Tooling integration

This guide offers non-normative expectations for exporters, build tooling, and linting workflows.

Design tools

Exporters SHOULD generate deterministic identifiers, timestamps, and names. Token names SHOULD use slash‑separated paths.

Build tools

Transformers MAY map tokens to CSS variables, platform constants, or other configuration files. When converting units, tools SHOULD honour platform conventions such as px to dp on Android and pt on iOS. Install @lapidist/dtif-schema to validate inputs and consume the bundled TypeScript declarations, and use @lapidist/dtif-validator when you need a preconfigured Ajv instance inside CI or build steps.

Linting

Linting tools SHOULD warn on unknown $type values, unsupported units, and deprecated tokens. Warnings SHOULD NOT fail builds by default.

Design Lint ships as an npm package (@lapidist/design-lint). It parses DTIF payloads with the canonical schema, enforces rule sets tailored to component libraries and CSS authoring, and emits deterministic diagnostics and formatter output for both local development and CI pipelines.