Art & Design

>- Operational framework for high-density, zero-waste modern web applications, tool dashboards, and productive workspaces. Use when designing, building, or refactoring web interfaces (React, TypeScript), two-pane master-detail layouts, unified compose hubs, keyboard-driven navigation, command palettes (cmdk), live telemetry indicators, and granular authentication ergonomics.

Reverse engineer shipped software with plain local CLI tools, no MCP needed. Covers Electron/JS bundles, native Mach-O/ELF/PE, Go/Rust/.NET/Flutter/WASM binaries, APKs, SQLite, pcaps, firmware and websites. Use to explain how a feature works, extract versions/deps, compare builds, or rebuild a feature.

Application structure and file-placement guide for NestJS GraphQL (code-first) applications. Use when deciding where a file belongs, designing or reviewing a feature-first directory layout, scaffolding a new feature module, or working out how modules connect to resolve GraphQL fields and relations. Covers the base structure map plus per-file rules for modules, services, resolvers (query, mutation, subscription, field), inputs and args, pagination, entities (Mongoose schema best practices for shared types), repository-only model injection, models/mappers, repositories, Mongoose discriminators, derived fields, providers, loaders, events, background jobs, auth, exceptions, custom scalars, config, common building blocks, infra setup, and the naming/testing/lint conventions — and module-resolution concerns such as circular dependencies. For behavioral rules (DI depth, security, performance, error handling) use the nestjs-best-practices skill instead.

>- Comprehensive guide and operational framework for native Android and mobile UI/UX engineering. Use when designing, auditing, building, or refactoring Android applications (Jetpack Compose, Material 3), mobile ergonomics, offline-first outbox patterns, stale-while-revalidate caching, smart one-tap intent actions, storage framework integrations, tactile haptics, shared element transitions, predictive back gestures, and seamless mobile authentication.

Create or edit interactive 1C form prototypes from text, screenshots, or form XML, and preview them in Codex's in-app browser. Use for GUI mockups, not 1C configuration changes or business operations.

Auditoria de segurança frontend (varredura FS01–FS11, dependências, cookies de sessão, plano priorizado). Um script determinístico implementa as regras 1–45 do README.md e escreve out/<caso>.json.

Generate perceptually uniform color ramps and compose accessible color palettes in OKLCH. Builds gamut-clamped 9-12 step scales from base colors, unifies multiple hues at each step, and validates WCAG contrast and colorblind safety with a bundled script. Use when the user asks to create a color ramp, generate a color palette or color scale, expand a brand color into tints/shades, build design-system color tokens, or check a palette for contrast/colorblind accessibility.

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

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.

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.

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.

Review a pull request or branch diff against main — read-only. Checks intent and simpler alternatives, traces real code paths beyond the diff, then runs the repo checklist (CI, tests, authz and user-supplied ids, dependencies and EOL, security, audit/session/health, UI/i18n, design, bug-fix evidence, core rule files) and reports must-fix items with evidence and a one-line verdict. Use before opening a PR, when asked to review, or when assigned a review card.

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.

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".

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).

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.

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".