pwguler
11 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
pwgulercore-interview
Internal support skill that runs the interview loop for other skills, until every decision is settled. Use it only when another skill or the user starts it, never on your own.
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulerdebug
Find the root cause of a bug before you fix it. Read this skill before you fix any bug. Read it also when the fix looks obvious. Use it when the user says "fix", "broken", "not working", "error", "failing", or "bug". Use it also when a test fails unexpectedly during other work.
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulerdrill
Question a plan or design until every decision in it is settled and agreed. Read this skill first when the user asks for a new feature, or when a design is not settled. Use it when the user wants a plan stress-tested or a design settled before building. Use it also to settle the structure of a new codebase or area. Use it when the user says \"drill this\" or \"drill me\".
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulerimplement
Implement a settled plan test-first, smallest slice at a time. Use when starting implementation of a feature or fix after the plan is settled, or when user says \"implement this\" or \"build it\".
- installs
- 1
- GitHub stars
- 10
- Updated
- Sep 28
pwgulerparallel
Run independent tasks at once in subagents, race attempts at one task, or cover many parts of one job. Use it only when the user asks for parallel work. Use it when the user asks to run two or more independent tasks or failures in parallel. Use it also to race or compare several attempts at one task, or to cover many parts of one job.
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulerprototype
Build a throwaway UI prototype for the user to react to before any real code. Read this skill when the user asks for a mockup or a prototype of a UI. Use it when a design decision depends on look, feel, or flow that text cannot settle.
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulerrecall
Rebuild where recent work stands, from past sessions of the agent, the live repository, and the history of the project. Give back a short brief. Run it before you start or continue work, with or without a topic.
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulerresearch
Find out what is true about a library, service, or standard from the owner of the facts. Or find out from its history why code has its shape. Write the answer down with a citation for each claim. Read this skill when the user asks why code, a constant, or a setting has its current form. Use it when the user asks to look something up, or to check how an API or tool really behaves. Use it also to give reading to a subagent while other work continues.
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulerrubric
Find defects in a change with independent read-only reviewers. Judge quality that no command can settle, such as "this API design is good" or "this UI is not slop". Judge it against criteria written before anyone looks at the work. Use when the user asks for a defect review or a bug hunt on a change. Read this skill when the user asks whether a design, a UI, a name, or prose is good. Use it when a UI, public interface, name, or doc needs a quality judgment before it ships. Use it when a spec cri
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulertldr
Report a finished task as its result, not its transcript. Or tell the user what happened since their last message. Read this skill before your final report on a task that changed files, made an artifact, or ran a check. Examples are a build, a workflow, a background agent, an implement or verify run, or a release. Use it also when the user asks what happened since their last message. Use it when the user asks to catch up on this session.
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16
pwgulerverify
Prove a claim of done, fixed, or passing before you make it. Run the commands and read their output. Read this skill before you say that work is done, fixed, or tested. Read it also after a small change. Use it before a commit or a PR. Use it also when the user asks to write or update the verification recipe of the app.
- installs
- 1
- GitHub stars
- 10
- Updated
- Oct 16