메뉴
Run a structured UI/UX polish pass on implemented code. Spawns a scrutiny agent to generate 15-30 improvement suggestions, presents them numbered for user selection, converts selected ones to beads, and triggers implementation. Use after initial implementation is complete.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Relentless goal/design interview that sharpens framing and writes durable docs (brainstorm artifact, ADRs, glossary) as decisions crystallize. Use when refining a flywheel goal, pressure-testing scope, or "grill with docs".
Start or resume the full agentic coding flywheel. Drives the complete workflow: scan → discover → plan → implement → review.
Set up flywheel prerequisites for this project.
One-shot diagnostic of every flywheel dependency — MCP connectivity, Agent Mail liveness, br/bv/ntm/cm binaries, node version, git status, dist-drift, orphaned worktrees, and checkpoint validity. Use when debugging toolchain issues, before starting a new session, after /flywheel-cleanup, or as a CI gate.
Strategic gap analysis between vision (AGENTS.md / README.md / plan docs) and what's actually implemented. Converts gaps into beads, optionally launches a swarm. Use when "reality check", "where are we really", "gap analysis", "did we drift", or before declaring a long-running project done.
Launch a parallel swarm of agents to implement multiple beads simultaneously.
| name | ui-ux-polish |
| description | Run a structured UI/UX polish pass on implemented code. Spawns a scrutiny agent to generate 15-30 improvement suggestions, presents them numbered for user selection, converts selected ones to beads, and triggers implementation. Use after initial implementation is complete. |
A structured polish phase for UI/UX quality: scrutiny → selection → bead conversion → implementation.
Spawn a scrutiny sub-agent with this exact task prompt:
"Great, now I want you to super carefully scrutinize every aspect of the application workflow and implementation and look for things that just seem sub-optimal or even wrong/mistaken to you, things that could very obviously be improved from a user-friendliness and intuitiveness standpoint, places where our UI/UX could be improved and polished to be slicker, more visually appealing, and more premium feeling and just ultra high quality, like Stripe-level apps."
If the user wants a second round of deeper suggestions after reviewing Phase 1 results, use this follow-up:
"I still think there are strong opportunities to enhance the UI/UX look and feel and to make everything work better and be more intuitive, user-friendly, visually appealing, polished, slick, and world-class in terms of following UI/UX best practices like those used by Stripe, don't you agree? And I want you to carefully consider desktop UI/UX and mobile UI/UX separately while doing this and hyper-optimize for both separately to play to the specifics of each modality. I'm looking for true world-class visual appeal, polish, slickness, etc. that makes people gasp at how stunning and perfect it is in every way. Think carefully and step-by-step; this is harder than it looks."
The scrutiny agent should produce exactly 15–30 numbered improvement suggestions. Format:
N. [Component/File] — specific change and why it improves UX
Present the numbered suggestions to the user. Ask which to implement:
For each selected suggestion, call br create with:
### Files: listing the relevant file(s)After bead creation, call flywheel_approve_beads to review the new beads and launch implementation via swarm.
After implementation, run a de-slopify pass on any documentation or UI copy files that were modified to remove AI writing patterns and improve documentation tone.