πŸ“ Design Guide

Compose a blueprint from feature blocks β€” each block becomes a requirement card that already meets the house standards β€” then launch it. The standards themselves (design, code, infrastructure, pipeline) are the reference section below; the factory injects the same records into its prompts and the judge grades against them.
2/7checks
Core data 0Workflow & control 0Visibility & collaboration 0Time & scheduling 0Compliance & privacy 0ACs 0failure-path coverage β€”
target: …
PROFILEedit β†’
ON LAUNCH1Spec intake2PRD3Define4Contract5ADP6Design7Build8Scores9Provision10Deploy11Verifyhow each step works β†’
FEATURE BLOCKS β€” click or drag to add
CORE DATA0/5β–Ύ
πŸ—‚οΈRecord tracking
πŸͺœDrill-down lists
πŸ”ŽSearch & filter
🎯Assignment
πŸ“€CSV export
WORKFLOW & CONTROL0/3β–Ύ
βœ…Approval workflow
πŸ‘₯Roles / permissions
πŸ“œAudit trail
VISIBILITY & COLLABORATION0/3β–Ύ
πŸ“ŠSummary dashboard
πŸ””Alerts / reminders
πŸ’¬Comments / notes
TIME & SCHEDULING0/3β–Ύ
πŸ“…Due dates & overdue
πŸ“ˆTimeline view
πŸ”Recurring items
COMPLIANCE & PRIVACY0/3β–Ύ
πŸ—‘οΈRetention & purge
πŸšͺAccess log
πŸ“¦Export-on-request
QUICK START
REQUIREMENTS CANVASΒ β€” drop blocks, drag cards to reorder, click to edit
🧩
Drag a feature block here
each block becomes a standards-compliant requirement card
STANDARDS CHECK
2/7 green β€” resolve the amber items
⚠
DS-01 Every feature is a requirement
drag features onto the canvas
⚠
DS-02 β‰₯2 acceptance criteria each
all requirements covered
⚠
DS-02b Negative-path AC present
every requirement tests a failure path
βœ“
DS-04 Decisions imply an audit trail
satisfied
⚠
DS-08 Right-sized (3–7 for standard scope)
add more β€” a real app needs at least 3
βœ“
CS-02 Login gate
always enforced by the factory β€” anonymous users land on /login
⚠
APP Name + summary
give the app a name and a one-line summary
β–Ύ Standards
the same records are injected into the factory prompts and graded by the page judge