design-dna

Design DNA

Build a machine-readable design profile without presenting guesses as measured facts. Treat existing project tokens, Figma variables, approved specs, and vault decisions as sources of truth.

Source priority

Use the strongest available evidence in this order:

1. Existing approved project tokens, Figma variables, and implementation constants.
2. Inspected source code and computed styles.
3. Pixel measurements or color sampling from supplied assets.
4. Visual inference from screenshots or video.
5. Qualitative interpretation.

Never overwrite a stronger source with a weaker inference. When sources conflict, report the conflict and ask which source governs.

Evidence contract

Read references/schema.md before extraction. Preserve its three dimensions: design_system, design_style, and visual_effects.

For every populated leaf, add an entry to a top-level evidence map keyed by JSON path:

{
  "evidence": {
    "design_system.color.primary.hex": {
      "status": "measured",
      "confidence": 0.96,
      "source": "Figma variable Brand/Primary"
    }
  }
}

Allowed status values:

• authoritative: approved token, Figma variable, spec, or implementation constant.
• measured: directly sampled or inspected.
• observed: clearly visible behavior or property without an exact value.
• inferred: reasoned estimate from incomplete evidence.
• unknown: not supported by the available references.

Use null for unknown values. Do not fabricate a complete-looking profile. Keep confidence between 0 and 1 and explain low-confidence fields briefly.

Workflows

Structure

When asked for the schema, read references/schema.md, present only the relevant sections unless the user requests the complete schema, and explain the evidence contract.

Analyze references

1. Identify reference type and available evidence.
2. Inspect the strongest sources first.
3. Extract only supported fields.
4. Record evidence status, confidence, and source for every populated field.
5. Separate shared patterns from reference-specific variants.
6. Report unknowns and contradictions instead of silently resolving them.
7. Return the JSON plus a concise findings summary.