Add InDesign-to-React conversion pipeline

[PAMulligan]

Summary

Add an end-to-end pipeline that turns Adobe InDesign designs into finished React products — typed React components, design tokens, asset imports, and (in v2.0.0) optional Next.js / Vite / Astro scaffolding — as a sibling to the existing Figma/Canva-to-React pipeline.

This is the epic tracking issue. Implementation is broken into sub-issues below.

Motivation

Design and marketing teams that produce brochures, pitch decks, and editorial layouts in InDesign currently have no direct path to React. Aurelius already has a strong Figma/Canva-to-React pipeline; adding InDesign extends Aurelius's design-to-code coverage to print-first sources and unlocks a new class of users.

Scope

Input formats (both supported)

• IDML (.idml) — primary path. XML-based, well-documented, gives access to stories, frames, styles, swatches, and master pages.
• PDF (exported from InDesign) — fallback path. Extracts text runs, images, and approximate layout via positional analysis.

Output

• Typed React components (one per InDesign spread or logical section), generated as .tsx files with explicit prop types for any extracted content.
• Design tokens (tokens.ts / tokens.css) covering typography scale, color palette, and spacing scale derived from InDesign paragraph/character styles and swatches.
• Tailwind preset (when Tailwind is selected in the Aurelius config) that exposes those tokens.
• Asset pipeline: linked/embedded images written to public/ (or framework-appropriate location) with correct relative imports.
• Optional multi-framework scaffolds (Next.js, Vite, Astro) per the v2.0.0 milestone direction.
• Storybook stories auto-generated for each component (aligns with v2.0.0 Storybook auto-generation goal).

Sub-issues

• IDML parser and intermediate representation
• PDF fallback parser and layout reconstruction
• Style and design-token mapper (paragraph/character styles + swatches → tokens + Tailwind preset)
• React component generator (TSX output, optional Tailwind/CSS Modules, Storybook stories)
• Claude Code agent + skill + documentation for the InDesign pipeline

Acceptance Criteria

• Running the pipeline against a representative .idml produces a directory of typed React components plus a tokens.ts, importable from any of the supported v2.0.0 framework scaffolds.
• Running against a representative exported PDF produces equivalent output with documented fidelity caveats.
• Generated components render in Storybook without runtime errors on the happy-path fixture.
• A dedicated indesign-to-react Claude Code agent is available and documented.
• End-to-end CLI command (e.g. aurelius pipeline indesign <input>) is documented with examples.
• Sample fixtures (.idml and exported PDF) are committed under tests/fixtures/indesign/ and exercised in CI.

Out of scope

• Round-tripping (React → InDesign)
• Editing .indd proprietary files directly (we rely on the user exporting to IDML or PDF)
• Interactive PDF features (forms, embedded video)

Related

• Parallels the existing Figma/Canva-to-React pipeline (pipeline label)
• Targets the v2.0.0 milestone alongside multi-framework output and Storybook auto-generation