Blueprint generation
Describe a feature and generate implementation-ready Blueprint Bundles for AI coding assistants
Blueprint Bundles are implementation-ready context packages generated from your Functional-Domain Wiki. Describe a feature, and Stractal identifies affected domains and produces a technical design tailored to your AI assistant.
Creating designs
Designs are feature specifications that drive blueprint generation. You can create them in two ways:
- From the Design tab — click New design, write a title and summary, then refine scope and link affected Wiki domains.
- From AI chat (Build mode) — describe what you want to build in natural language. The assistant proposes a design that you can accept, edit, or reject.
Design lifecycle
| Status | Meaning |
|---|---|
| Draft | Initial description, still being refined |
| Proposed | Ready for review, not yet scoped |
| Confirmed | Scope defined (in-scope items, out-of-scope items, technical approach) |
| In blueprint | Included in a generated blueprint |
| Implemented | Feature has been built |
| Archived | No longer active |
Only confirmed designs can be included in blueprint generation.
Impact analysis
When you link a design to Wiki domains, the impact analysis panel shows which domains, files, types, and database tables are affected. Each linked domain has an impact type: modify (change existing behavior), add (new functionality), or remove (deprecate or delete).
Generating blueprints
Select designs
From the Blueprints tab, choose one or more confirmed designs to include. You can filter designs by status to find the ones ready for generation.
Add context
Optionally add additional notes to guide the blueprint — for example, constraints the AI assistant should respect or implementation preferences.
Generate and export
Click Generate to produce the bundle. Once ready, export in your preferred format.
Export formats
| Assistant | Directory | Context file |
|---|---|---|
| Claude Code | .claude/ | CLAUDE.md |
| Cursor | .cursor/ | .cursorrules |
| Gemini | .gemini/ | GEMINI.md |
| GitHub Copilot | .github/copilot/ | agent.md |
| Windsurf | .windsurf/ | cascade.md |
| Generic | docs/ | AI_CONTEXT.md |
Knowledge Base
The Knowledge tab in your project lets you add supplementary context that gets incorporated into blueprints. Use it for information that can't be derived from code:
- Team coding conventions and style guides
- Deployment and infrastructure notes
- Business rules and domain context
- Temporary instructions or constraints for current work
The Knowledge Base accepts up to 50,000 characters and supports file uploads for importing existing documentation.
Replacing manual context files
If you maintain hand-written .cursorrules, CLAUDE.md, or similar files, Stractal can replace that manual work. The Wiki captures domain structure, database schema, API surface, type system, and dependencies directly from code — context that manual files miss or let go stale.
You may still want manual files for team conventions, deployment instructions, or business context not derivable from code. The Knowledge Base is designed for exactly that — it merges your supplementary context with Wiki-derived architecture to produce comprehensive blueprints.