← all publishers

blueclover22

@blueclover22 source repo

Report this profile Claim this profile

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

1. ▌
   Setup · blueclover22 bundle

   Use when asked to install or update the mak common rules in ~/.claude/CLAUDE.md, optionally in Korean (ko) or English (en).
   0
   installs
2. ▌
   Commit · blueclover22

   Use when the user explicitly asks to commit the current changes. Push, amend, and rebase require separate explicit requests.
   0
   installs
3. ▌
   Teardown · blueclover22

   Use when asked to remove the mak-managed rules block from ~/.claude/CLAUDE.md, especially before uninstalling the plugin.
   0
   installs
4. ▌
   Doc Audit · blueclover22

   Use after a slice/phase completes, at a phase transition, or before handing off unfinished work. Not for single-design implementation review (mak:review-report), verification (mak:verify-checklist), code-vs-doc behavior analysis (mak:analyzer), or choosing the next task (mak:dev-resume).
   0
   installs
5. ▌
   Dev Resume · blueclover22

   Use only on explicit request to resume or take over work when the next task is undecided. Use mak:dev-kickoff for a decided task, mak:reverse-engineering when project docs are absent, and mak:doc-audit for document-consistency audits.
   0
   installs
6. ▌
   Dev Kickoff · blueclover22

   Use for feature/component additions, cross-file behavior changes, refactors, migrations, or changes to data models, dependencies, security, or deployment, and when task size is unclear. Skip Trivial/Small work (typos, formatting, one-line or single-file fixes). If direction is vague, use mak:brainstorming first.
   0
   installs
7. ▌
   Brainstorming · blueclover22

   Use when the user lacks a settled direction and asks what to build or how to approach it ("what are the options", "any ideas", "how should we approach this"). If direction is settled, use mak:dev-kickoff.
   0
   installs
8. ▌
   Review Report · blueclover22 bundle

   Use when asked to review or critique finished implementation work ("review this", "code review", "look at the PR"), or when a completed stage needs checking against its design doc.
   0
   installs
9. ▌
   Roadmap Planning · blueclover22 bundle

   Use to create or update a project-wide, multi-phase roadmap, including priorities and status. For a single feature or phase, use mak:dev-kickoff.
   0
   installs
10. ▌
    Verify Checklist · blueclover22

    Use after any implementation or change, before reporting it done, even without an explicit verification request.
    0
    installs
11. ▌
    Design Doc Template · blueclover22 bundle

    Use when asked to record an approved or sufficiently converged design in the standard design-doc format. Use mak:dev-kickoff first if requirements or approval remain unresolved.
    0
    installs
12. ▌
    Reverse Engineering · blueclover22 bundle

    Use when asked to bootstrap a project's docs/ set or reverse-engineer an existing codebase into that set; also supports brand-new projects.
    0
    installs