This repository is equipped with AI agent instructions, slash commands, and migration guides that help you work faster with AI coding assistants. Whether you're migrating a component, creating tokens, or writing tests, there's likely an AI-assisted workflow ready to help.
Open the repo in any AI coding assistant (Claude Code, Cursor, Codex, etc.) and it automatically picks up all the agent configuration, with no setup required.
The repo ships with:
/command-nameSlash commands are ready-made workflows that handle common tasks end-to-end. Type the command in your AI coding tool and it takes it from there.
Creates a pull request following the repo's conventions. It handles branch naming, Conventional Commits title formatting, and description templates, including the "How did you test this?" checklist for feat and fix PRs.
The AI will:
feat-button-loading-prop)type(scope): subjectTurns a vague task request into a precise, self-contained goal document to paste into the goal command. It grounds the brief in the codebase first (relevant code, git history, conventions), asks you only the decisions that are genuinely yours, then writes a standalone goal under the runner's 4000-character limit.
The goal covers the whole lifecycle: change, tests, build/verify, and branch/commit/push/PR. It carries concrete anchors, such as commit SHAs, file paths, and component and token names, so it stands alone without the originating conversation.
Generates a Storybook playground code snippet for quick demos and testing. Just describe what you want to see and the AI produces a runnable snippet.
Snippets follow playground conventions: no imports needed, Box for layout, React. prefix for hooks.
Creates a design token across all five themes (default, odeditor, odeditor-dark, studio, studio2-light) with optional per-theme overrides. Supports foundation, semantic, and component levels.
The AI handles JSON structure, type inference, validation against existing tokens, and runs pnpm generate afterward.
Automates applying design tokens from a Figma spec to a component's CSS files. Give it a Figma link and the component name, and it will:
value() calls with var(--wds-...) using proper fallbacksGuides you through renaming visual tests and cleaning up generated screenshots across all themes. Handles the full lifecycle: renaming in source .visual.tsx files, deleting old screenshots, and regenerating new ones.
The repo includes detailed migration guides that the AI follows step-by-step. You don't need to memorize the rules. Just ask the AI to perform the migration on a component.
Converts JS components to TypeScript with zero breaking changes. The AI handles:
.js → .tsx, removing .d.ts files)ComponentName.types.tsComponentName.constants.tsComponentName.uni.driver.ts), keeping method descriptions but dropping the @param, @return and @returns tags the types now coverConverts class components to functional components using hooks. The AI maps:
| Class Pattern | Functional Pattern |
|---|---|
this.state | useState |
componentDidMount | useEffect(() => {}, []) |
componentWillUnmount | cleanup in useEffect |
componentDidUpdate | useEffect(() => {}, [deps]) |
| Public methods via ref | forwardRef + useImperativeHandle |
Both migrations preserve the public API. Props, ref methods, events, and display names remain identical.
The AI is pre-loaded with coding conventions specific to this repo. These are enforced automatically when it writes code, so you don't need to remember them all:
| Convention | What it does |
|---|---|
| Visual testing | Follows the visualize → story → snap pattern with storybook-snapper |
| E2E testing | Uses Playwright with Sled infrastructure, correct file naming, and data-hook patterns |
| No setTimeout | Avoids setTimeout for timing workarounds and uses proper async patterns instead |
| TypeScript types | Maintains TypeScript type definitions as the source of truth |
| Prop documentation | Writes the description of every prop it adds or changes in the same change, in the Wix writing style |
| Unused CSS vars | Removes unused CSS variables from Stylable files |
| Component token overrides | Overrides literal CSS properties on Stylable-extended selectors instead of reassigning global tokens |
| Design tokens | Follows the token hierarchy (foundation → semantic → component) |
| Illustration conventions | Follows the SVG build pipeline and naming patterns |
| Docs content | Writes guideline and introduction pages in the house voice, with real image alt text and the page conventions this site uses |
Here are some prompts you can use directly with the AI to accomplish common tasks:
Component work:
Testing:
Tokens and Figma:
Migrations:
Pull requests:
Last updated: 26 October 2026