← ClaudeAtlas

bld-sprint-refinelisted

sr: Polish a working app base screen by screen. Design craft, motion, optional 3D and premade components. Use for "polish this app", "make it feel great", "bring it to life", once a screen is basically done.
mnguyenht/bld-package · ★ 1 · Web & Frontend · score 64
Install: claude install-skill mnguyenht/bld-package
# bld-sprint-refine — working base → feels alive Takes a base (from `/bld-sprint-init` or existing) and layers on craft. This skill **orchestrates other skills** — you must actually INVOKE each one (via the Skill tool / its script), not just read about it. The last time this was skipped, the app stayed plain. Don't repeat that. ## ⛔ MANDATORY PROTOCOL — read before doing anything 1. **Every sub-skill below must be actually invoked**, in order, for the screen you're refining. "Invoke" = call the Skill tool for that skill (or run its script), load its guidance, and **apply the changes it produces**. Mentioning it is not invoking it. 2. **Vibe first.** If there's no agreed design direction / design guide for this app yet, STOP and pin it down with the user before any polish (ask: mood, references, what "great" looks like). Craft passes on an undefined vibe just thrash. 3. **One screen at a time, fully.** Take a single screen all the way through Phases 1→4 before starting the next. Don't half-apply across many screens. 4. **You are NOT done until the Completion Checklist at the bottom is filled with real evidence** (which skill ran + what it changed) for this screen. If you skipped one, say so explicitly — an incomplete refine must be reported as incomplete, never as done. Announce the screen you're refining, then work the phases. ## Phase 1 — ui-ux-pro-max (the deeper steps bld-init skipped) **Invoke `ui-ux-pro-max`** against `design-system/MASTER.md`