A design and engineering arsenal for Claude Code.

01 Plan

It asks before it draws.

An interview, one question at a time, until every decision is made. Then the project files: SOUL.md for who it is for, MASK.md for how it looks, ARMOURY.md for type, tools and five dials that decide what the project may do.

## Type
website

## Dials
auftreten: werkstatt
bewegung:  1
dichte:    luftig
technik:   statisch
tonfall:   nüchtern

02 Design

Taste, written as numbers.

Grid, type, colour and perception as measurable rules, plus layout patterns beyond the card grid and a slop test: if it could be captioned “AI made that”, it failed.

• Body text16–18 px, line height 1.5–1.6
• Measure45–75 characters
• Contrast4.5:1 text, 3:1 large text and controls
• NeutralsOKLCH-tinted, never pure black or white
• Typefacestwo families at most, of different kinds
• Techniquesone or two per page, not five

03 Build

A fixed order, because the order is the point.

The build runs as a workflow you see as a flowchart first. Content comes before layout, references before generation, variants before choice. 48 ready building blocks wait in the library before anything is drawn from scratch.

1. Content before layoutreal copy for every section and state
2. Reference pullconfirmed references loaded first
3. Variants and selectionnever the first draft
4. Assemblyeach agent owns its own files
5. Critique loopindependent reviewers, three fix rounds at most
6. Release gatefresh reviewers, another model than the builder
7. Performance and reduced motionmeasured on the rendered page

04 Animate

Motion with a reason to exist.

A motion doctrine with sourced tokens instead of hand-picked milliseconds. Transform and opacity only, bounce almost never, and a complete reduced-motion version at every setting. WebGL, 3D and scroll choreography come with their budgets.

05 Engineer

The parts nobody sees, held to the same standard.

Architecture, data, APIs, security, optimisation and conventions, each a reference the agent opens before it decides. A tech database of 359 entries proposes the stack. Fourteen standard checks prove a build meets its requirements.

• PLNRequirements quality
• REQTraceability
• FUNFunction and edge cases
• TSTTests
• SECSecurity
• PRFPerformance
• A11YAccessibility
• CODCode and conventions
• DATData and backups
• APIAPI contract
• ERRErrors and logging
• OPSDeploy and rollback
• DOCDocumentation
• LICLicences

06 Review

Six critics who never see each other’s notes.

Each reviewer starts fresh and checks the same page alone. A finding without severity, location, finding and fix is dropped. The rest is merged into Necessary, Recommended and Taste, and fixed on your word.