Menu
Review the named UI scenario or emit one bounded improvement packet.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Drive one ready artifact through implementation, proof, review, and owner handoff.
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.
Ask which Boring skill or workflow fits your situation. A router over the local Boring skills.
Run an extremely strict maintainability review for abstraction quality, giant files, spaghetti-condition growth, and code-judo simplification opportunities.
Route a request to the right Boring v2 workflow skill without doing the work.
Create a GitHub issue from user feedback with safe context and simple labels. Never implement.
| name | ui |
| description | Review the named UI scenario or emit one bounded improvement packet. |
| disable-model-invocation | true |
Read docs/kanzen/procedures/visual-review.md before acting; it owns commands,
hard-gate authority, critic bounds, packet rules, providers, and owner handoff.
Also follow docs/kanzen/MODEL-CARD.md.
Accept only explicit review <registered-spec> or
improve <registered-spec>. Resolve the exact name through the repository
registry; reject URLs, paths, configs, commands, and unknown names.
review is read-only and reusable by reviewer agents for changed frontend
components or behavior; it leaves a bounded spec-defined report.improve creates one checkout-bound execution packet; validate it, then invoke
/skill:exec <run>/execution-packet.json exactly once.Never apply packet fixes here, recurse into improve, auto-run provider hooks,
or treat advisory critic scores as hard gates.