app-development-blueprint-protocol-v2-0

# App Development Blueprint Protocol v2.0 Skill ## Core Mission When a user requests development of an App or any programming project, **strictly enforce the "plan-first, function-as-unit" workflow** — never skip steps and jump straight to writing large blocks of code. ## Execution Phases (Strictly sequential — no phase may be skipped) ### Phase 1: Requirements Analysis & Blueprint Planning (Blueprint Phase) 1. Deeply parse the user's requirements and produce a **Functional Specification Document**. 2. Generate a **Complete Function Inventory** where each entry includes: - Function name (verb-first, following language conventions) - Single-responsibility description - Input parameters (type, validation, default values) - Output type and description - Edge cases and exceptions - Dependencies on existing functions / classes 3. Draw an overall architecture blueprint (plain-text flowchart or Mermaid syntax). 4. Clearly label each item as **"new function"** or **"references existing content"**. ### Phase 2: Expand All Existing Functions / Classes (Reference Expansion Phase) - For any **already-existing** function, class, or module referenced in the blueprint, **output it in full first**: - Complete code block - Detailed docstring - Type hints - Usage example and recommended unit tests - Ensure all referenced content is directly copy-pasteable within this conversation. ### Phase 3: Per-Function Spec Definition (Spec Definition Phase) Produce a formal spec for each function. Example format: ```markdown ### function_name **Purpose**: ... **Inputs**: ... **Outputs**: ... **Exceptions**: ... **Dependencies**: ... **Test Cases**: (at least 3) ``` ### Phase 4: Implementation (Implementation Phase) - Implement **one function at a time**, strictly following its spec. - After each function is complete, immediately provide: - Full code block (with language tag) - Usage example - Recommended unit-test code - After all functions are done, produce the **Entry Point / Main Program** and the project structure. ## Rules - At the start of every task, output: "**App_Development_Blueprint_Protocol_v2.0 activated**". - Never generate multi-function code blocks without prior blueprint approval. - Blueprint must be user-confirmed before moving to Phase 2. ## Trigger Phrases "Use the blueprint protocol to develop XXX App", "Activate v2.0 Blueprint", or any app-development request.