← all publishers

pwguler

@pwguler source repo

Report this profile Claim this profile

• 14 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Deep · pwguler

   Full ceremony mode for the whole suite. Run /deep before risky or ambiguous work; /deep off returns to fast-first.
   0
   installs
2. ▌
   Land · pwguler

   Finish a development branch. Use when implementation is complete and the work needs to be merged, pushed as a PR, kept, or discarded.
   0
   installs
3. ▌
   Tldr · pwguler

   Report a finished task as its result, not its transcript. Use when a task that produced an artifact or a run (a build, a workflow, a background agent, an implement or verify run, a release) has just finished and you are about to report it, and when the user types /tldr.
   0
   installs
4. ▌
   Debug · pwguler

   Find the root cause of a bug before fixing it. Use whenever the user says "fix", "broken", "not working", "error", "failing", or "bug", and whenever a bug, test failure, or unexpected behavior appears, before proposing any fix.
   0
   installs
5. ▌
   Drill · pwguler bundle

   Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, drill into their design, or says "drill this" or "drill me".
   0
   installs
6. ▌
   Rubric · pwguler

   Gate a taste claim that no command can prove, such as "this API design is good" or "this UI is not slop", by judging the work against checkable criteria. Use when verify meets a claim its commands cannot settle, when a design or artifact needs a quality call before it ships, or when the user asks whether something is good.
   0
   installs
7. ▌
   Verify · pwguler

   Prove a claim of done, fixed, or passing by running the commands and reading the output before making it. Use before claiming work is complete, fixed, or tested, and before committing or opening a PR.
   0
   installs
8. ▌
   Parallel · pwguler

   Dispatch independent tasks to concurrent subagents. Use when two or more failures or tasks are independent, sharing no files or state, and can be worked simultaneously.
   0
   installs
9. ▌
   Research · pwguler

   Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
   0
   installs
10. ▌
    Implement · pwguler

    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".
    0
    installs
11. ▌
    Prototype · pwguler

    Build a throwaway UI prototype to react to before committing. Use when a design fork turns on look, feel, or flow that prose cannot settle, or when the user asks to prototype or mock something up. Prefers the /design canvas; falls back to a self-contained HTML artifact when /design is not available.
    0
    installs
12. ▌
    Write Skill · pwguler

    Create or edit a document an agent reads and prove it changes behavior. Use when writing or editing a skill, AGENTS.md, CLAUDE.md, a system prompt, or other agent-facing prose, or verifying one before it ships.
    0
    installs
13. ▌
    Architecture · pwguler bundle

    Shape a codebase's architecture, at the start or once it fights you. Use when setting up a new codebase or area, choosing structure and conventions, or when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
    0
    installs
14. ▌
    Core Interview · pwguler

    Internal support skill, the relentless interview loop other skills delegate to. Use only when another skill or the user explicitly triggers it, never on your own.
    0
    installs