Exporters#

TasteKernel exporters turn one contract into implementation guidance artifacts for tooling and design-to-code workflows.

Supported outputs#

tastekernel export v0 generates:

• tastekernel.v0.instructions.md
• tastekernel.v0.registry-alignment.json

tastekernel export figma generates:

• tastekernel.figma.rules.md
• tastekernel.cursor.rules.mdc
• tastekernel.claude.fragment.md

Backward-compatible aliases are also supported:

• tastekernel export-v0
• tastekernel export-figma

Commands#

From a repo with tastekernel.contract.yml:

tastekernel export v0
tastekernel export figma

Output files are written to the current working directory.

File intent#

tastekernel.v0.instructions.md#

• Human-readable instruction pack
• Captures token/component/motion/copy constraints
• Includes do/don’t behavior guidance

tastekernel.v0.registry-alignment.json#

• Machine-readable alignment payload
• Token mappings and component inventory
• Required import paths and naming conventions

tastekernel.figma.rules.md#

• Design-to-code guardrails for token/component fidelity
• Motion and copy constraints for implementation parity

tastekernel.cursor.rules.mdc#

• Compact editor-agent guidance
• Designed for repeated code generation sessions

tastekernel.claude.fragment.md#

• Small policy fragment for assistant prompts
• Focuses on non-negotiable implementation constraints

Operational guidance#

• Treat exporters as generated artifacts from the active contract.
• Regenerate on contract changes.
• Keep exporter files versioned in repos where downstream tooling consumes them.
• Do not hand-edit generated files unless you explicitly fork the generator.

Validation checks#

After export, verify file presence and non-empty content:

for f in \
  tastekernel.v0.instructions.md \
  tastekernel.v0.registry-alignment.json \
  tastekernel.figma.rules.md \
  tastekernel.cursor.rules.mdc \
  tastekernel.claude.fragment.md; do
  test -s "$f" && echo "OK $f" || echo "MISSING/EMPTY $f"
done

Dashboard downloads#

Dashboard exports page serves the same five artifacts from active contract state:

• /projects/[slug]/exports
• API: /api/projects/[slug]/exports?file=<filename>

Use this path for CI or remote retrieval where local generation is not preferred.