메뉴
Route a request to the right Boring v2 workflow skill without doing the work.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Drive one ready artifact through implementation, proof, review, and owner handoff.
Review the named UI scenario or emit one bounded improvement packet.
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.
Create a GitHub issue from user feedback with safe context and simple labels. Never implement.
| name | ask-boring |
| description | Route a request to the right Boring v2 workflow skill without doing the work. |
Router only. Do not edit files, create issues, plan, implement, review, or merge.
feedback — user is reporting a bug, idea, UX issue, feature request, or rough observation that should become a GitHub issue.triage — an existing issue/PR needs classification, verification, or a next state.plan — the desired outcome needs a spec, implementation plan, slices, blockers, or proof path before coding.implement — one issue/slice is ready for an agent to build.diagnose later — hard bug without a tight repro loop.wayfinder later — huge/foggy effort where the destination or route is not knowable in one session.human — external access, product judgment, security/privacy, merge authority, or unavailable context is required.Return one routing card:
Recommended: <skill>
Why: <one sentence>
Input: <issue/PR/path/context to pass>
Next: /<skill> <args>
Caution: <optional blocker or human decision>