Die Kette provides
- Design system and rulebook
- Components, domain components and page templates
- Agent roles, skills and review flows
Spec-driven Development
Spec-driven development. On a ready foundation.
Die Kette extends spec-driven development with an existing design system, concrete UX/UI rules, reusable components and specialised agents for building and reviewing.
The contribution in every step
SDD sets the process. Die Kette brings the content.
SDD structures development from the requirement to the reviewed implementation. Die Kette brings content, components and workflows that are already worked out.
The comparison follows the Spec Kit process, see Spec Kit Documentation. Review and release form the project process that follows. Step 0 happens once. Every new feature starts at step 1.
-
Once
Prepare the project
SDD Set ground rules and the working environment.
Die Kette Plug in the design system, rulebook, agents, skills and checks. Define ownership and sources of truth.
Benefit Less setup work. A shared working framework is already in place.
-
Describe the user task
SDD Clarify who wants to achieve what and how success shows.
Die Kette Requirements and UX roles support the description. Existing prototypes and usage patterns serve as concrete references.
Benefit Clear requirements sooner. People and agents can talk about concrete flows.
-
Clarify requirements
SDD Resolve missing details and contradictions.
Die Kette UX/UI rules and do/don't examples steer the review towards interaction, feedback, errors and missing states.
Benefit Fewer missed details. Empty views, loading states and focus behaviour are covered too.
-
Plan the solution
SDD Design architecture, interfaces, data and implementation.
Die Kette Pick matching tokens, components and page templates. Connect project specific domain logic and technology to them.
Benefit Less repeated design work. Existing solutions can be adopted and extended where needed.
-
Derive tasks
SDD Break the implementation into ordered work steps.
Die Kette Assign tasks to the affected stations and agents, such as tokens, Figma, library, domain components or app. Plan review tasks in.
Benefit Clear ownership. Changes are made at the right source and in the right order.
-
Implement
SDD Agents work on the agreed tasks.
Die Kette Build agents use existing components, page templates and tokens according to the shared rulebook.
Benefit Less custom UI code. Interfaces are assembled from components that fit together.
-
Review and correct
SDD Check the implementation against spec and plan, close gaps.
Die Kette Separate review roles for QA, design and accessibility add to automated tests. Findings go back to the owner.
Benefit Broader quality review. Function, design and interaction are checked. Fixes address the root cause.
-
Accept and ship
SDD Assess the user task, approve the result and release it.
Die Kette Existing review and release flows plus versioned component packages support delivery. Improvements flow back into shared components.
Benefit Reusable improvements. Further features and applications benefit with the next update.
The key differences
What Die Kette adds on top.
- Design foundation
- Connected prototypes, Figma files, tokens and design guidelines.
- Build foundation
- React components, domain components and page templates as existing code.
- Quality bar
- Concrete UX/UI rules and examples that carry into requirements and reviews.
- Way of working
- Specialised agent roles and a loop of building, separate review and returning findings.
- Evolution
- Connected sources and versioned packages that pass corrections on.
Where the offer ends
Framework and interface from us. Domain logic from you.
Domain logic, backend, APIs and databases are still worked out for each project. Die Kette provides the shared design and working framework plus the interface components to connect.
Stays with the project
- Domain logic
- Backend and APIs
- Databases
The added value is the foundation that is already built and connected: a project does not have to develop its design system, components, rules and review roles entirely on its own.
Spec first. Foundation ready.
Join the waitlist, or write to us if you already have a design system.