/**
 * `@urbicon-ui/design-engine` — the deterministic core of the Urbicon UI design loop.
 *
 * Zero runtime dependencies. Five independent modules, each also available as a
 * subpath export (`@urbicon-ui/design-engine/{linter,manifest,reference,rubric,search}`):
 *
 * - **linter**    — the engine behind `validate_design`: deterministic rules + the
 *                   token whitelist + distribution heuristics ("is it correct?").
 * - **manifest**  — the persistent design-intent layer: parse/edit `design.manifest.md`
 *                   and scan `data-design-pattern` markers ("what has this project decided?").
 * - **reference** — the CSS design-token reference text + design-system file parsers
 *                   (principles topics, pattern entries) behind the CLI's
 *                   `css-reference`/`principles`/`pattern` and the MCP server's
 *                   `get_css_reference`/`get_design_principles`/`get_pattern`.
 * - **rubric**    — the eight-criterion design-quality rubric ("is it good?", judged).
 * - **search**    — the component-catalog + icon schemas, discovery rankers, and
 *                   `llm.txt` section parser shared by the CLI's
 *                   `find`/`get-component`/`icons` and the MCP server's
 *                   `find_components`/`get_component`/`find_icons`.
 *
 * Extracted from `@urbicon-ui/mcp-server` so the same engine can back the MCP server,
 * a CLI, and editor hooks. See docs/internal/DESIGN-MCP-V2.md.
 */

export * from './linter/index.js';
export * from './manifest/index.js';
export * from './reference/index.js';
export * from './rubric/index.js';
export * from './search/index.js';