Art & Design

Reconsiders a project or shelved idea against current capabilities, proposes three ambitious outcomes, and designs an experiment for the hardest uncertainty. Use when asked "what more is now feasible", "is this worth attempting now", "revisit this shelved idea", or "think bigger about this project".

How SwiftUI decides what to re-render — identity, lifetime, dependencies — and how to write views that update efficiently, especially SwiftUI hosted in UIKit cells (UIHostingConfiguration) and views rebuilt from streaming or generated content. Use when writing or reviewing SwiftUI views for performance, fixing views that lose state, flash, re-render too often or reload images, choosing ForEach identifiers, hosting SwiftUI in collection/table view cells, or debugging layout that changes when views are wrapped. Based on WWDC21 "Demystify SwiftUI" and WWDC23 "Demystify SwiftUI performance", plus lessons verified in practice.

Generate a comprehensive Product and Technical Requirements Document (PRD-Project) with visual Mermaid diagrams through an interactive two-step workflow. Use when the user asks to create a PRD, plan any software/web/mobile/AI/game project, write specifications, or design system architecture.

>- Write the plan for a Clanker Ship ticket, following the team's plan instructions. Use when the person asks to plan, design or write up how to do a ticket such as WEB-31. Fetches the team's live instructions with get_agent_instructions, saves the plan with update_ticket, and waits for approval before implementing.

>- Orchestrates the full feature lifecycle: Refine → Design system → Architecture → Build → Verify production readiness. Use when starting a story, implementing a feature end-to-end, or closing out work before PR. The parent coordinates child skills — it does not duplicate their rules.

>- Design-system guidance in three modes: PLAN (prospective reuse and abstractions before build), BUILD (apply those standards while implementing), REVIEW (audit branch diff against them). Use in feature-development phases 2, 4, and 5; or standalone for inline styles, sx, custom CSS, one-off cards, or pattern-library scope. Formerly pattern-library-refactor.

Production data-access playbook for the N+1 query problem. Use when code queries a database inside a loop, an ORM lazy-loads a relation per row, or a list endpoint is fast at 5 rows and slow at 50. Worked cases are in references/bad-vs-good.md. Do not use for HTTP contract design or for Go/JavaScript language style.

Guides systematic refactoring to align features with established patterns, remove duplication, and improve code reuse. Includes DataGrid/pattern-library, typing, fetch pagination, view-model vs override-prop guidance, and MUI sx-first layout (avoid deprecated Box style shorthand props). Use when refactoring features, consolidating duplicate code, extracting shared utilities, or aligning patterns across similar features.

Production Go playbook. Use when writing or reviewing Go: errors, goroutines, byte payloads, parsers, and switches on external input. Worked cases are in references/bad-vs-good.md. Do not use for JavaScript, TypeScript, or API-contract design.

Spec-driven feature work that freezes obligations instead of the plan: one human-reviewed plan with EARS criteria, path, entities, interface and one-way doors, then proof-backed checks, then build, then an independent Verifier. Use when the user says "tlc-spec-lean", "plan feature", "specify feature", "write the checks", "build this plan", or "verify work". Do NOT use for standalone design documents unattached to a feature, architecture decomposition analysis, or work that already has a task list or checklist to execute.

>- Comprehensive operational framework and design intelligence for modern UI/UX design, design systems, visual hierarchy, design tokens, component architecture, high-density financial terminal aesthetics, accessibility (WCAG 2.2 AAA/AA), mobile ergonomics, data visualization, and complete interface revamps. Use this skill whenever auditing, designing, refactoring, building, or restyling user interfaces, dashboards, design systems, layouts, forms, data tables, animations, and micro-interactions.

Design secure Supabase and PostgreSQL architectures including schema, RLS, authentication, migrations, and query performance. Use when planning or reviewing a Supabase-backed application.

Design or review REST/RPC API contracts that are consistent, evolvable, and hard to misuse. Use when defining new endpoints, reviewing an API surface, or resolving naming/versioning/error-shape questions.

Design or review polished, accessible interfaces inspired by Apple Human Interface Guidelines. Use for web, native, and responsive product UI; do not copy Apple proprietary interfaces or assets.

Rigorous, severity-ranked review of a diff, PR, or file. Use when you want a thorough check of correctness, security, performance, design, readability, and test coverage with actionable feedback.

>- Comprehensive guide and operational framework for software engineering standards, clean code, low-level design (LLD), high-level architecture (HLD), distributed systems, API contracts, database indexing, capacity planning, and architecture decision records (ADRs). Use this skill whenever designing, evaluating, refactoring, reviewing, or scaling software architectures, backend services, database schemas, APIs, or performance-critical systems.

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

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.

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.

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