Art & Design

Create or update a project's documentation set — README.md, AGENTS.md, MEMORY.md, CHANGELOG.md, DESIGN.md, docs/architecture.md, docs/plans/, and API docs (OpenAPI + Scalar). Use this whenever the user asks to "document my project", "documenta mi proyecto", "crea/actualiza el AGENTS.md o MEMORY.md", "genera el README", "actualiza el CHANGELOG", "crea/actualiza el DESIGN.md", "documenta el diseño visual", "escribe el architecture.md", or mentions keeping agent instructions/memory/plans in sync after finishing work — even if they only name one file, since these docs are interdependent and should be checked together.

Activate a session-wide policy that permits architecturally justified breaking changes and removes compatibility with project-owned historical interfaces from design constraints. Use only when the user explicitly invokes `$allow-breaking-change`; never trigger implicitly from generic refactoring, simplification, architecture, compatibility, or breaking-change discussion. Keep the policy active across projects and tasks for the rest of the current conversation unless the user overrides it for a task or disables it.

Design a new system or a large feature before any code — interview in rounds, write docs/design/<slug>.md from the template, ADRs and glossary, run make docs-check, and open a docs-only PR for approval. Use when asked to design something, or when /new-feature finds the feature is large.

按阮一峰《中文技术文档的写作规范》与微软中英文风格指南撰写、审校简体中文技术文档与本地化文案，并可按 ASD-STE100 简明技术英语约束英文技术写作。凡是要写或改 README、教程、API 文档、发布说明、博客、产品/UI 文案、错误提示，或是把英文技术内容翻译成中文，以及讨论中文标点、中英文混排空格、数字用法、标题层级、文档结构、语气风格，或要求简化英语（STE/Simplified Technical English/受控语言）、安全关键文档、航空与维修手册风格时都应使用——即使对方没有明说"写作规范"。

Analyse a Figma .fig file kept in a project's spcfctn/ui/draft. Unpacks and decodes it offline (kiwi), breaks it into sections, screens, text rows and rasters, writes the analysis to spcfctn/ui/*.md, then fetches the author's comments through the figma MCP by link, binds them to screens by geometry, checks that the comments agree with the content of the file and asks the user to clarify what does not. Use when the user asks to analyse, decode or re-read a .fig file or Figma wireframes, or to refresh spcfctn/ui after a new export.

Keeps a living PREFERENCES.md in the project that records every decision and preference the user states while working (product, design, technical, workflow, writing), with dates, so later sessions follow them instead of asking again. Use at the start of work in a project that has a PREFERENCES.md (read it first), and whenever the user makes, changes or reverses a decision, picks one of several options, corrects how something was done, or says things like "I prefer", "from now on", "always", "never", "let's go with", "no, do it like this", "remember that".

Create, verify, maintain, continue, and close subsystem documentation, change designs, and plans; verify how human-readable designs relate to engineering materials. Use when the user asks to organize these materials, work requires preserving design and execution context over time, or changes make existing documentation, plans, status, or navigation inaccurate. Check source code, tests, and relevant decisions as needed; distinguish current state, goals, unresolved questions, and actual verification; maintain a single source of truth. This is not a mandatory phase for every development task.

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Use when writing or revising replies, documents, UI copy, comments, or other prose. Make the next action clear.

Where frontend files belong in this repo. Fire when creating a new file or moving one.

Find and delete dead frontend code safely - prove unused, delete whole units, verify.

UI styling rules - one font, spacing over borders, 80-20-10 color. Fire when writing UI.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Use for new frontend applications, dashboards, games, creative websites, hero sections, and visually driven UI from scratch, or when the user explicitly asks for a redesign/restyle/modernization. Builds from clean, airy, high-taste, readable image-generated concept design with section-specific references, faithful implementation, and browser testing.

Executes the 4-Phase Agentic SDLC (Spec -> Red Test -> Green Implementation -> Quality Gate) for AI Motion Design Studio.

Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says "openspec propose" or "opsx propose".

Design and build polished, non-generic UI for this TanStack Start + React + Tailwind v4 + shadcn/Radix app. Use whenever you create or restyle any interface surface — pages, landing pages, dashboards, forms, modals, nav, and game overlays (start screens, HUD, menus). Covers design tokens, layout, typography, color, spacing, motion, and the anti-"AI-slop" rules that keep output from looking generic. Triggers on "design", "UI", "make it look good", "polish", "landing page", "theme", "style", "redesign", "ugly", "clean up".

>- Extract self-contained static HTML from a built web application or React components by inlining CSS and images. Use this skill whenever you need to capture a specific UI state, share a static version of a page, or prepare assets for Stitch upload, even if the user just asks to 'save the HTML' or 'mock the view'.

>- Extract a comprehensive design system (DESIGN.md) directly from frontend source code — React, Vue, Svelte, Angular, plain HTML/CSS, or any web framework. Analyzes component files, stylesheets, Tailwind configs, theme definitions, and design tokens to produce a rich, Stitch-compatible design system document. Use this skill whenever the user wants to reverse-engineer a design system from an existing codebase, audit the visual language of a project, extract design tokens from source files, or understand the styling patterns in a frontend repo — even if they just say "what does this app look like?" or "pull out the design from this code.

>- Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI/UX terminology, design tokens and theme system capabilities.

>- Convert frontend code (Vite, React, Angular, Vue, etc.) to a Stitch Design by chaining static HTML extraction, design system extraction, and file upload. **ALWAYS** use this skill when the user's intent is to move existing web apps or React/Angular/Vue components into Stitch (e.g., requests to "save", "migrate", or "upload"). You must use this skill even for simple "save" operations, as it is the only way to ensure the design system is extracted and assets are properly linked.

Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.

Make Roblox game UI end to end. read the developer's style reference (stud style by default), source textures from ui-resources.com, take icons ONLY from one licensed vector icon pack the developer owns, build every screen in HTML/CSS with all states, let the developer check and approve it, then export to JSON, upload images, generate and build a real ScreenGui in Studio, wire the runtime UI module, and verify. Use for ANY Roblox UI, GUI, HUD, menu, shop, popup, screen, panel, frame, button, toast, billboard, tutorial card, crate/RNG reel or icon request; when the user mentions "ui resources", "ui-resources", "stud style", "html ui", importing a UI into Studio, or gives feedback on a UI's look.

Candidate nurturing — design cadenced care plans for long-cycle candidates, showing up at the right time with the right content so great people never drift away in silence.