project-builderlisted

End-to-end project engineering — from understanding user intent to architecture design, incremental build with verification, and systematic debugging. Covers scheduled tasks (cron jobs), dashboards, web apps, APIs, scripts, and any software the user wants built. Replaces coder + preview-dev with a unified methodology.
Starchild-ai-agent/official-skills · ★ 13 · Web & Frontend · score 73

Install: claude install-skill Starchild-ai-agent/official-skills

# Project Build Three phases, always in order: **DESIGN → BUILD → DEBUG**. **Skill references** (read on demand, not upfront): - `references/build-patterns.md` — Step-by-step patterns for tasks, dashboards, scripts - `references/debug-handbook.md` — Layer-by-layer diagnosis, common issues **Platform references** (shared, in `config/context/references/`): - `preview-guide.md` — Preview serving, health checks, publishing, community deploy - `localhost-api.md` — Scripts can call the agent via /chat/stream (decide when to think, what context to pass, which model) and push messages via /push - `sc-proxy.md` — Transparent proxy, API pricing & rate limits **Skill references** (in `references/`): - `build-patterns.md` — Detailed build recipes per project type - `debug-handbook.md` — Systematic diagnosis protocol - `dashboard-examples.md` — Code templates for Chart.js, ApexCharts, D3.js, SSE, responsive layouts, dark mode, accessibility (read when building dashboards) --- ## Phase 1: DESIGN **Translate vague requests into concrete specs.** If intent is ambiguous, ask ONE question. Architecture decision tree: ``` Periodic alerts/reports? → Scheduled Task Live visual interface? → Preview Server (dashboard) One-time analysis? → Inline (no build needed) Reusable tool? → Script in workspace ``` For medium+ projects, present to user BEFORE writing code: 1. Data flow — sources → processing → output 2. Architecture choice and why 3. Cost estimate — (cost/run) ×