buildlisted

# Feature Build Workflow Before starting work, create a marker: `mkdir -p ~/.claude/tmp && echo "build" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active` ## Phase 1: Research (GO/NO-GO Gate) Before any implementation, complete this research phase: 1. **Detect stack** — read `package.json`. `next` dep → satus / Next.js; `react-router` dep → novus / React Router. Note any starter signal (`name` field, `darkroom.starter` marker). 2. **Understand requirements** — parse what the user actually needs. 3. **Explore codebase** — find existing patterns, similar implementations. 4. **Fetch docs** — use Context7 MCP for any external library. Never code from memory. 5. **Check versions** — run `bun info <package>` for the latest version. 6. **Assess feasibility** — can this be done cleanly within existing architecture? **GO/NO-GO Verdict**: After research, state one of: - **GO** — requirements are clear, approach is viable, proceed to implementation. - **NO-GO** — requirements are ambiguous, approach has blockers, or scope is too large. Report findings and stop. Do not proceed past this gate without an explicit GO verdict. ## Phase 2: Plan Create a brief implementation plan: - Files to create/modify (with stack-correct paths — `lib/hooks/` for satus, `hooks/` for novus, etc.) - Key decisions and rationale - Dependency order ## Phase 3: Implement Follow standard Maestro workflow: scaffold → implement → test → review. Use the