React-specific rules for writing components — component tiers (UI kit / business blocks / pages), folder structure, props conventions, and Storybook stories. Builds on top of the framework-agnostic ui-component skill. Apply when creating, editing, or reviewing React components.
Pattern for SVG icons via a symbol sprite — individual SVG files are compiled into a single sprite.svg by the svg-sprite package, and an Icon component renders them with <use href="sprite.svg#name">. Apply when setting up an icon system, adding icons to a project that uses this pattern, or reviewing icon-related code.
Conventions for writing unit tests in Trigen-style repositories — Vitest, colocated *.spec.ts files, describe groups that mirror the unit's address (package → folders → module → unit in monorepos, folders → module → unit in single-package projects), and "it should" test titles. Apply when writing, editing, or reviewing unit tests.
Migrate Trigen-style repositories from @trigen/eslint-config to @trigen/oxlint-config, including package scripts, Node runtime setup, oxlint.config.ts files, nested monorepo configs, and cleanup of old ESLint config usage.
Scaffold the base of a new Trigen-style project (Node.js/frontend, TypeScript/JavaScript, single package or pnpm monorepo) by copying and adapting config files from reference repositories — toolchain, linting, git hooks, GitHub workflows, and simple-release publishing. Apply when creating a new project or bringing an existing one up to the Trigen project baseline.
Pattern for mixins in native CSS (no preprocessor) — a mixin is a class in a shared CSS Module, its parameters are CSS Custom Properties, applied by adding the class to an element. Apply when creating or using reusable style mixins in a CSS Modules codebase.
Framework-agnostic rules for writing UI components — semantic HTML, CSS Modules conventions (root class, camelCase, CSS Custom Properties), and UX/accessibility requirements. Apply when creating, editing, or reviewing UI components, their markup, or styles.