Project Context

Create durable context without making other skills depend on it.

PRODUCT.md records product truth. DESIGN.md records an observed or explicitly chosen visual system. Keep them separate because they change for different reasons.

Default workflow

1. Resolve the project root and read any existing PRODUCT.md, DESIGN.md, product documentation, package metadata, routes, representative UI, tokens, and shared components.
2. Identify the requested mode: product context, design documentation, or both. Decide independently whether each file should be created, refreshed, or left alone.
3. Infer only what the repository supports. Treat code as evidence, not user approval.
4. Ask only about material product facts or visual commitments that cannot be inferred.
5. Before changing an existing context file, explain whether the operation is a refresh, merge, or replacement. Never silently overwrite it.
6. Write the smallest accurate document. Mark unresolved decisions instead of inventing answers.
7. Report what was created or changed, what evidence supported it, and what remains unknown.

Read references/templates.md before writing either file. When writing DESIGN.md, also read references/design-format.md; it contains the portable token schema, extraction order, and canonical headings.

PRODUCT.md