Art & Design

Use this skill when designing or reviewing APIs — REST, GraphQL, tRPC, or gRPC. Trigger on keywords: API design, REST, GraphQL, tRPC, gRPC, endpoint, schema, route, OpenAPI, Swagger, API versioning, pagination, API contract, HTTP methods.

Use this skill when designing how an AI agent should communicate with developers — intent clarification, progress reporting, ambiguity handling, confirmation before irreversible actions, error communication, self-correction, task tracking, and plan mode. Also use when building agent UX or defining agent behavior rules. Trigger on keywords: agent communication, intent clarification, plan mode, agent behavior, task tracking, confirmation, agent UX, agentic workflow, agent protocol.

Find and run a project's test, lint, type-check, build and dev-server commands, read the results correctly, and seed a throwaway database when UI work needs realistic data. Never seeds the project's real or default database. Use before 'run the tests', 'lint this', 'does it build', 'start the app so I can see it', 'seed some demo data', and before you claim that a change works. Not for deployment or CI pipeline design; use the project's own deploy tooling for those.

Review Go (Golang) code changes like a careful senior engineer, following Google's code review practices and Google's Go Style Guide best practices (design, functionality, complexity, tests, naming, errors, comments, style, docs) plus Go-specific checks for errors, concurrency, context and resource handling. Use this whenever the user asks to review Go code, a diff, a PR/MR, a branch or a .go file, or asks things like "check my changes", "is this Go code okay", "LGTM?", even if they don't say "code review".

Applies an agreed visual direction to a page or component by reusing existing components first, then verifies every width and dark mode with the headless-Chrome audit plus a before/after pixel diff, and reviews against Refactoring UI, Nielsen and WCAG 2.2. Use when asked to redesign, restyle, polish or "make it look like the reference", after design-ref or when the direction is already clear.

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

>- Use when designing or changing Croct content models: regular vs union components, what becomes a component, slot, structure, or primitive attribute; writing component schema JSON (`structure`, `union`, `reference`, `text`, `number`, `boolean`, `list`, `@croct/file`, `@croct/richText` rich text, `format`, `choices`, `optional`, `private`, `position`); writing content definition JSON (`static`/`dynamic` values, `nullable`, `default`, `{{placeholder}}` paths); slot default, localized, experience, experiment, or content group content; schema limit errors (30 attributes, 6 nesting levels, 10 union members, complexity score 50); component versioning and breaking changes (`home-hero@2`); refactoring (duplicate and modify, duplicate and replace, flatten and merge); Markdown in text attributes with `@croct/md-lite`. Phrasings: "model content for a hero", "add an attribute to the banner component", "support variations", "component is too complex", "localize the hero", "translations", `preferredLocale`.

Use when starting a feature, refactor or bug fix; when asked to plan, spec, design or debug something; when writing a plan or handoff document; when choosing, adopting or upgrading a dependency, framework or external API; or when starting work that will become its own branch. Covers propose-before-building, scoping work to the PR size budget, debugging discipline, reading current docs instead of trusting memory, and when and how to use a git worktree.

Use when a change touches anything a user sees, such as components, pages, views, screens, styles, templates, dialogs, forms or copy, and before opening a PR for it. Covers driving the change in a real browser through every state, running a review sweep against the repo's design and framework guidelines, and capturing screenshots for the PR, including what to do when no browser is available.

Founden MCP server. Build your company over chat with one API key, no browser required. Works with Claude Desktop, Cursor, VS Code.

Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for \"computer use\". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before computer use is turned on for a conversation there may be no such tools, only an enable__mcp__remote-devices__computer tool, which turns it on. It covers turning it on, picking the right tool, the access flow, and the safety rules for tiered apps, links and financial actions. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.

Function-first design guidance for UI, UX, product, information, and visual design. Use when designing, critiquing, or reviewing interfaces, screens, components, layouts, flows, charts, copy structure, APIs/CLIs as user surfaces, or any object meant to be used; when choosing between aesthetic options; when asked to "make it look better/cleaner/simpler/modern"; or when deciding whether to add, keep, or remove an element, animation, or feature.

Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files

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.

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

Designs deep modules with small interfaces, real seams, and interface-level tests. Use when shaping a module's API, restructuring code, or choosing test seams. Not for quick fixes.

Review an engineering design, code change or result against requirements and raw evidence. Use for independent correctness, security, reliability, performance and evidence review before integration or consequential claims.

Use when designing, writing, reviewing, packaging or releasing audio plugins (synths, effects, MIDI controller plugins) in C++/JUCE for VST3 on Linux, macOS and Windows. Covers realtime safety, parameters, CPU/RAM/GPU/latency, sound quality, instrument, filter, FX and preset design, UI standards, offline installers and manuals, signing, testing and security.

Execute a bounded engineering job with explicit commands, resources and output evidence. Use for builds, tests, data jobs, simulations and benchmarks; return design or algorithm changes to their owner unless implementation is assigned.

>- DESIGN.md 设计契约工作流——为任意项目生成 / 提炼 / 验收前端设计系统。 按 Google Stitch 规范的 DESIGN.md（YAML 令牌 + 11 节正文）沉淀设计决策， 产出机器可读 tokens、tokens.css（双形式令牌）、Tailwind 映射与可视化预览页， 并用 WCAG 2.1 对比度门禁做回归验收（可在 CI 中阻断构建）。 集成 awesome-design-md（84 个真实品牌 DESIGN.md 参考库）与 DeepSeek Search/Fetch 实时网页研究（付费直连、**默认关闭**——需用户显式同意并带 --yes-billing；无 key / 未同意时 优雅降级为内置抓取）。 TRIGGER when: 用户要给项目立设计规范/统一样式（"设计系统"、"DESIGN.md"、"design tokens"、 "配色规范"、"前端风格不一致"）；要从参考网站提炼配色/字体/圆角；要审计 UI 对比度 / 可访问性（WCAG、contrast）；要引用 awesome-design-md 里的现成 DESIGN.md； 为 UI 工作做 design research（竞品视觉分析、品牌参考）。 DO NOT TRIGGER when: 纯后端 / CLI / 数据管道任务；只需要生成一张图片（用 qianwen-image-generation）；只是普通代码功能开发且不涉及视觉一致性。

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

Design before building. Use for anything significant - a big feature, a refactor, a new project, multi-repo work, or changes to core logic, state, data, money, security or public APIs. Walks through product, architecture, program design and vertical slices, stopping for the user's approval at each stage, and records the design in docs/designs/.

Delegate authorized work to Claude Code or Codex agents (native subagents or separate CLI workers), consult ChatGPT Pro through native app messaging when available, or create detailed technical infographics through ChatGPT web with Extra High, never Pro. Use for substantial implementation, UI checks, audits, documentation, refactoring, annotation batches, independent review, difficult research, complex module design, and infographic images. Claude receives bounded assignments; Pro receives questions with approval before each submission and user-triggered retrieval; infographic briefs put content before aesthetics. Includes context sharing, progress reporting, Claude allowances and reset times, scheduled continuation, and parent verification.

PostgreSQL naming and schema conventions (tables, columns, keys, constraints, indexes, relations, types) for .NET/EF Core, Node.js (Drizzle, Prisma, TypeORM, Knex) and Go (sqlc). Use when designing or reviewing schemas, writing migrations, entity configurations, sqlc queries or SQL, or when asked how to name database objects. Reports deviations to the user instead of silently changing them.