Artifacts

Specra generates two public artifacts from each successful revision.

Artifacts are not the main product surface, but they are the clearest way to inspect exactly what Specra inferred.

The artifacts are portable. You can download DESIGN.md and theme.css and apply them manually in any stack. The stricter TailwindCSS and shadcn/ui expectations belong to Specra's MCP and skills workflows, where the agent needs a predictable implementation path.

DESIGN.md

This is the agent-facing entrypoint.

Read it first when you want the compact, convention-friendly guide with:

• visual atmosphere
• token and type rules
• component recipes
• do and don't guidance
• prompt-ready implementation notes

theme.css

This is the implementation-ready theme contract.

Use it for semantic styling such as:

• bg-background
• text-foreground
• bg-card
• border-border
• text-muted-foreground

Recommended order

If you are working directly from artifacts:

1. read DESIGN.md
2. apply theme.css