typix

Cross-cutting expert for the shadcn-style "vendor source into user project" distribution model. Use when designing or debugging anything that touches the pipeline from packages/design-system/src/* → CLI templates → user's components/typix/ folder. Spans CLI (packages/cli) and design-system (packages/design-system). Use ALONGSIDE typix-cli or design-system, not instead of them.

Cross-cutting CSS rules for Typix consumers. Use when working on a consumer app's globals.css, debugging Tailwind v4 + Turbopack issues, deciding which @typix-editor/ui styles to import, handling dark mode wiring, or diagnosing "unknown utility class" / "unstyled component" / "CssSyntaxError" build failures.

Expert for @typix-editor/ui. Use when working on UI primitives, main editor components (CodeBlockUI, FloatingLinkUI, MentionUI, etc.), design tokens, the new src/styles/ structure, or any visual layer work. Attaches frontend-design, polish, and animate skills for quality UI work.

Expert for @typix-editor/react. Use when working on React hooks, components, context, or anything in packages/react. Knows the hook API, component patterns, and how to bridge TypixEventEmitter to React state correctly.

Expert for the Typix CLI tool. Use when building or working on the CLI — scaffolding commands, extension generators, project init, config management, vendoring design-system components, or any Node.js CLI tooling for Typix.

Lexical engine expert and cross-agent reviewer. Use when working on anything that touches Lexical internals — nodes, commands, editor state, plugins, reconciliation — or when reviewing work done by other Typix agents for correctness against Lexical constraints.

Expert for @typix-editor/svelte. Use when building or planning the Svelte adapter for Typix. Knows Svelte 5 runes, stores, actions, and how to bridge TypixEventEmitter to Svelte's reactive system correctly.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Strict guardian of @typix-editor/core. Use when working on the core package — createTypix, TypixEditor, extension system, event emitter, chain builder, commands, or server utilities. This agent prevents breaking the public API and enforces zero-React, zero-framework rules.

Expert for building and maintaining Typix extensions. Use when creating a new extension, modifying an existing one, or reviewing extension code for correctness. Knows all Lexical extension APIs and enforces Typix extension conventions.

Expert for @typix-editor/vue. Use when building or planning the Vue adapter for Typix. Knows Vue 3 reactivity, composables, and how to bridge TypixEventEmitter to Vue's reactive system correctly.