exporters-builder

Build deterministic CSS and JSON exporters from v0.3 planning specs.

3|Updated Jan 11, 2026

Search Tags:#planning #css #tooling #json #codegen #deterministic #exporters

Ready to run

npx skills add https://github.com/claushaas/palette-kit --skill exporters-builder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: exporters-builder
Source: https://github.com/claushaas/palette-kit/tree/main/.codex/skills/exporters-builder
Command: npx skills add https://github.com/claushaas/palette-kit --skill exporters-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to implementing CSS and JSON exporters that align with v0.3 planning specs, ensuring consistent output across environments.

Core Features & Use Cases

Read planning docs to align exporters with spec-v0.3 and roadmap-v0.3.
Implement exporters in src/export with OutputOptions and deterministic formatting.
Ensure optional meta data is included only when requested and verify compatibility with downstream tooling.

Quick Start

Create or update the exporters in src/export following the v0.3 spec and run tests to verify deterministic CSS and JSON output.

Frequently Asked Questions about exporters-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build deterministic CSS and JSON exporters from planning docs?▼

To build deterministic CSS and JSON exporters from planning docs, implement your export logic in a src/export directory using OutputOptions, aligning with spec-v0.3 and roadmap-v0.3 to ensure stable output across environments.

Why does my CSS and JSON codegen output vary across different environments?▼

CSS and JSON codegen output varies across environments when deterministic formatting is not enforced. Implementing exporters with structured OutputOptions ensures consistent token export and stable formatting across all downstream tooling.

What's the best way to enforce stable token export for theme codegen?▼

The best way to enforce stable token export for theme codegen is to structure exporters with OutputOptions, including optional metadata only when requested, and verify compatibility with downstream tooling through dedicated tests.

Do I need planning specs to implement deterministic JSON exporters?▼

Yes, you need planning specs to implement deterministic JSON exporters. The implementation requires access to src/planning/spec-v0.3.md and src/planning/roadmap-v0.3.md to align export logic with the expected v0.3 formatting and feature requirements.

How do I test deterministic CSS and JSON output for correctness?▼

You test deterministic CSS and JSON output for correctness by running tests against your src/export implementation, verifying that OutputOptions produce stable formatting and that optional metadata is included only when explicitly requested.

Can I include optional metadata in my JSON token exporters without breaking determinism?▼

Yes, you can include optional metadata in your JSON token exporters without breaking determinism by configuring OutputOptions to include metadata only when requested, then verifying the output compatibility with downstream tooling through tests.