design-blueprint

Solid

Run a complete design workflow -- from establishing context through 5 progressive design levels to an approved blueprint. Composes context anchoring, design-first methodology, architecture, and DDD into a unified process. Handles both new features (create context doc) and resuming existing work (load context doc). Use when starting a design, planning architecture, or when the user says 'design a feature', 'blueprint', 'start designing', 'plan the architecture', or 'let's design before coding'.

AI & Automation 134 stars 8 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Design Blueprint ## Required Skills Read apply skills order: 1. `framework:knowledge-priming` -- Load project context (tech stack, architecture, conventions) ground decisions real project 2. `framework:context-anchoring` -- Create or load feature context anchor doc 3. `framework:learning-harvest` -- Load prior operational learnings inform design; harvest new patterns at session end (always) 4. `framework:collaborative-judgment` -- Surface real design judgment calls structured options instead silent assuming (always) 5. `framework:design-first` -- Walk through 5 progressive design levels 6. `framework:architecture` -- Apply structural rules Component and Interaction levels 7. `framework:domain-driven-design` -- Apply domain modeling Component, Interaction, Contract levels ## Workflow ### Step 1: Establish Context Use `framework:learning-harvest` Load behavior. Focus hint: "design session — focus: design patterns, reliability, structural health". Prior learnings about decomposition choices, failure-prone patterns, and structural debt inform design decisions from the start. Use `framework:context-anchoring` set up feature living doc. - **Document Discovery**: Check existing context anchor doc feature (scan context base directory, match by feature name or frontmatter). - **If exists** → Load (context-anchoring Load behavior). Present structured acknowledgment -- feature name, decision count, open questions, constraints. Resume last design checkpoint recorded doc. - **If...

Details

Author
techygarg
Repository
techygarg/lattice
Created
3 months ago
Last Updated
3 days ago
Language
Shell
License
MIT

Related Skills