← all publishers

gusgad

@gusgad source repo

Report this profile Claim this profile

• 9 skills
• 0 followers
• 1 repo stars
• last month last updated

1. ▌
   Playwright · gusgad

   Use when testing or validating the client UI end-to-end - verifying a page renders, a form submits, navigation works, or checking visual/responsive behavior in a real browser. Use when the user asks to "test", "check", or "verify" something in the app that requires clicking through the UI, not just unit tests.
   1 repo stars
2. ▌
   Code Review · gusgad

   Use when finishing a task, before merging, or when giving or receiving code review feedback on this repo - covers when to request a review, how to scope it, and how to respond to feedback with technical rigor instead of reflexive agreement.
   1 repo stars
3. ▌
   Agent Skills · gusgad

   Use when creating a new skill under .agents/skills/, editing an existing one, or deciding whether a technique deserves to become a skill at all - covers SKILL.md structure, the description field, and how to keep a skill discoverable and token-efficient.
   1 repo stars
4. ▌
   Ralph Wiggum · gusgad

   Use when a task is well-defined, has an automatic way to verify success (tests, linter, build), and is tedious or large enough to benefit from unattended iteration - e.g. "get all tests passing", "implement this spec end to end", "fix every lint error". Not for one-shot changes or work that needs human judgment mid-stream.
   1 repo stars
5. ▌
   Compound Engineering · gusgad

   Use after solving a non-trivial bug or making a non-obvious decision, to capture it as durable, searchable documentation so the next session doesn't re-derive it from scratch - and use at the start of related work to check whether that documentation already exists.
   1 repo stars
6. ▌
   Brainstorming · gusgad

   Use before any creative or ambiguous work - new features, new components, or behavior changes - to explore intent, requirements, and design before implementation starts.
   1 repo stars
7. ▌
   Systematic Debugging · gusgad

   Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
   1 repo stars
8. ▌
   Test Driven Development · gusgad

   Use when implementing any feature or bugfix, before writing implementation code.
   1 repo stars
9. ▌
   Verification Before Completion · gusgad

   Use before claiming work is complete, fixed, or passing, and before committing or opening a PR - run the actual verification command and read its output before making any success claim.
   1 repo stars