Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

Gusen1453

@gusen1453 source repo

11 published skills

  1. ▌
    Tdd · gusen1453
    Use when implementing any feature, bug fix, refactor, or behavior change, before writing production code.
    0
    installs
  2. ▌
    Debug · gusen1453
    Use when hitting a bug, a test or CI failure, unexpected behavior, or when about to claim something is fixed and the root cause is not yet proven with evidence.
    0
    installs
  3. ▌
    Grill · gusen1453
    Use when starting any creative work — a new feature, behavior change, architecture decision, or non-trivial plan — or when the user says grill / grill-me / brainstorm / pressure-test a design, and no code should be written until the design is agreed.
    0
    installs
  4. ▌
    Solid · gusen1453
    Use when locking module boundaries, class/API shape, or dependency direction after a design/spec is clear; when new packages, ports, or IO edges are about to be planned; when unit tests need many mocks; or when a review/refactor shows coupling or God-class smell. Do not use as the main skill while product decisions are still open (that is grill).
    0
    installs
  5. ▌
    Review · gusen1453 bundle
    Use when finishing a task or task slice, before a merge or PR, or after a major change — and when reviewing a spec, plan, or structure/boundary decision as its own object. Routes each review object to a dedicated rubric reference.
    0
    installs
  6. ▌
    Explore · gusen1453
    Use when a task modifies or references existing code — refactors, legacy rework, reusing a pattern, or when the prompt names specific methods/classes/tables. Harvests repo facts and verifies the user's technical claims before any design or code, so grill only asks judgment calls.
    0
    installs
  7. ▌
    Write Plan · gusen1453
    Use when you have an approved design or spec, or clear requirements for multi-step work, before touching production code, or when the user asks for an implementation plan or task breakdown.
    0
    installs
  8. ▌
    Write Spec · gusen1453
    Use after design alignment (grill), or when the user asks for a design/spec/PRD doc, or when locking scope before an implementation plan, or when handing work off to someone who was not in the design discussion.
    0
    installs
  9. ▌
    Test Design · gusen1453
    Use when writing, reviewing, or modifying unit/integration tests, adding test cases, assertions, or mocks, or deciding whether a piece of code is worth testing — especially when tempted to add tests for coverage, over-mock dependencies, or write formalistic tests that just restate the implementation.
    0
    installs
  10. ▌
    Using Creed · gusen1453
    Use when starting any conversation in a Creed-enabled workspace, or when unsure which Creed skill applies, before any creative, test, debug, or ship work.
    0
    installs
  11. ▌
    Commit And Push · gusen1453
    Use when the user asks to commit, push, commit-and-push, open/draft a PR/MR, or write a PR description with a Test plan — especially when changes should be split into logical commits, or when tempted to dump everything into one commit or push to a protected branch.
    0
    installs