Skill Claude CodeCodex
Teach a boring-ui child app how to enable Google signup with @hachej/boring-core. Use when the user asks for Google auth, Google OAuth, social signup, or how to turn on Google sign-in/sign-up in a child app.
Skill Claude CodeCodex
Ask which Boring skill or workflow fits your situation. A router over the local Boring skills.
Skill Claude CodeCodex
Run an extremely strict maintainability review for abstraction quality, giant files, spaghetti-condition growth, and code-judo simplification opportunities.
Skill Claude CodeCodex
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Skill Claude CodeCodex
Implement a piece of work based on a spec or set of tickets.
Skill Claude CodeCodex
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Skill Claude CodeCodex
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Skill Claude CodeCodex
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in a local file, or native blocking links on a real tracker.
Skill Claude CodeCodex
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Skill Claude CodeCodex
Create a GitHub issue from user feedback with safe context and simple labels. Never implement.
Skill Claude CodeCodex
Turn an issue or conversation into a spec and, when needed, tracer-bullet implementation slices with blockers and proof.
Skill Claude CodeCodex
Cut a boring-ui-v2 npm release from main and update the local/global boring-ui CLI install. Use when Julien says cut a release, new release, publish boring-ui, update global boring-ui CLI, or install latest boring-ui CLI.
Skill Claude CodeCodex
Generate a polished Nextra documentation site from any source repo. Use when building a docs site, "docs site for this repo", MDX docs, or deploying docs to Vercel.
Skill Claude CodeCodex
Use for /feedback: create one enriched GitHub issue with safe context, lean labels, first plan, and queued or grill-blocked state.
Skill Claude CodeCodex
Use for /loop-grill: clarify one Kanzen issue with grill-me and ask-user, then return it to triage or keep it blocked.
Skill Claude CodeCodex
Use for /loop-implement: implement one Kanzen issue or approved plan, open/update the PR, run review/fix/re-review, gather proof, and prepare owner or fast-track merge handoff.
Skill Claude CodeCodex
Use for /loop-plan: turn a Kanzen issue or PR that is too risky, unclear, large, or multi-slice for direct implementation into an issue-linked plan with acceptance, flag path, proof, review budget, and next slice.
Skill Claude CodeCodex
Use for scheduled /triage: refresh GitHub, run the first unmet gate, collect proof, and merge only fast-track-safe PRs.
Skill Claude CodeCodex
Use for /triage in boring-ui: refresh GitHub state, classify issues/PRs, choose the first unmet gate, route grill/plan/implement/proof/merge, and decide fast-track versus owner-review routing.
Skill Claude CodeCodex
Compatibility command for /loop-grill. Use boring-loop-grill for the actual Kanzen grill workflow.
Skill Claude CodeCodex
Compatibility command for /loop-implement. Use boring-loop-implement for the actual Kanzen implementation workflow.
Skill Claude CodeCodex
Compatibility command for /loop-plan. Use boring-loop-plan for the actual Kanzen planning workflow.
Skill Claude CodeCodex
Ask which skill or flow fits your situation. A router over the skills in this repo.
Skill Claude CodeCodex
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.