project-builder

Three phases, always in order: DESIGN → BUILD → DEBUG . Skill references (read on demand, not upfront): Platform references (shared, in config/context/references/ ): Skill references (in references/ ): Translate vague requests into concrete specs. If intent is ambiguous, ask ONE question. Architecture decision tree: For medium+ projects, present to user BEFORE writing code: Design Gate (required, blocking): After Phase 1, STOP and present a short phase plan (milestones for DESIGN/BUILD/DEBUG). Ask explicitly: "是否按这个方案进入 Phase 2 BUILD？" API cost & rate limits: All external API calls go through sc-proxy, which bills per request and enforces rate limits. Before designing, read config/context/references/sc-proxy.md for pricing table and limits. Data reliability: Native tools > proxied APIs > direct requests > web scraping > LLM numbers (never). Iron rule: Scripts fetch data.