Existing local artifacts
Use existing DESIGN.md and theme.css files as optional context alongside your codebase's current design system.
Existing DESIGN.md and theme.css files can remain useful local context for an agent. Specra's current desktop workflow starts with the real codebase, its indexed Design System, live Pages, and supplied references.
The former hosted extraction service no longer creates public artifact revisions. You do not need an artifact export to open a codebase or work on a desktop draft.
DESIGN.md
A local design guide can describe visual principles, typography, component conventions, layout patterns, and implementation notes.
Compare it with the current source before relying on it. If an older guide conflicts with the codebase's components or the requested task, resolve that difference explicitly instead of copying stale rules into a draft.
theme.css
An existing theme file can document semantic tokens such as background, foreground, border, and spacing values. Use it only where it matches the repository's styling conventions.
An agent should reuse the active theme and shared primitives in your codebase. The presence of an old exported stylesheet does not require a framework migration or replacement of the current design system.
Local screenshot evaluation
The companion plugin retains an optional artifact-based evaluation workflow. Its local-evaluate-loop.ts script reads local artifact paths from the target repository's .specra.json, accepts screenshots and evaluation JSON, and records results under .specra/local-eval.
That configuration belongs to the optional local evaluator. It does not link your repository to a hosted project, and it is not required for ordinary desktop use.
Review the exact source, route, theme, and state captured in the screenshot. A targeted check establishes only the reported fix, not complete visual alignment.