pica-model

pica implementation: the definition of done for building, reviewing, testing and releasing what was designed. Owns the standard, not the coding agent.

pica figma: port an approved package or rebuild an existing Figma file, annotate it, and verify it by measurement.

pica research: audit the named sources and derive tokens with provenance. Measures shipped products across the nine foundations, records typography by role rather than by size, and refuses concept sites as evidence.

pica content: the words. Glossary-bound terms, every state written, length-realistic copy, and mock data that is not quietly wrong.

pica analyst: elicitation, AS-IS and TO-BE, business rules, the domain model, and a PRD a non-technical reader follows. Carries a 28-sector knowledge base: who the stakeholders are, which colours the sector has already spent and why, the design tradition it settled on, and what it treats as a defect regardless of the brief. Fails closed on a sector it does not cover.

A design workflow for Claude Code. Prototype in HTML, port to Figma on approval, verify by measurement.

pica html: build each work package at every declared viewport and measure it before approval.

pica design QA: heuristic evaluation fanned out to independent evaluators, cognitive walkthrough, and the build-versus-design comparison nobody owns.

pica developer: build the approved design into working code. The API contract as a seam with its errors, four places state can live, every failure shaped so the copy reaches it, accessibility in code, and a performance budget with the condition it holds under.

pica core: intake, the contract, the state schema, and every approval gate.