All Skills

Symbol (adah-symbol)

Action (adaz-action)

Memory (aeaf-memory)

Symbol (afah-symbol)

Action (afaz-action)

时间符号 (agah-symbol)

Action (aiaz-action)

Action (ajaz-action)

Action (akaz-action)

通用粒子抽象接口。当定义物质维度、物理实体或物质系统时调用此技能。

Action (amaz-action)

通用规划抽象接口。当定义规划过程、策略制定、目标分解时调用此技能。

Action (apaz-action)

Action (aqaz-action)

Action (araz-action)

Action (ataz-action)

Action (auaz-action)

Action (avaz-action)

Action (ayaz-action)

融合分类系统与潜能蒸馏能力，从复杂现象中提取本质并进行结构化分类，促进跨领域知识整合与创新。

融合分类系统与范式锻造能力，将不同领域的分类体系融合成新的分类范式。

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use `review-animations`; for auditing a whole codebase use `improve-animations`. Source: github.com/emilkowalski/skills.

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

Write, read, and apply DESIGN.md files — Google Stitch's open AI-readable design-system format (YAML design tokens + Markdown rationale). Use when asked to "create a design.md", "extract a design system from [brand/PDF/site/screenshots]", "document this brand for AI tools", or when reverse-engineering a brand's visual identity into reusable tokens for an AI coding agent to apply consistently.

Conduct a design interview, generate 5 distinct UI variations in a temporary route, collect real click-to-comment feedback on the live rendered variants via human-review, and produce an implementation plan. Use when the user wants to explore UI design options, redesign an existing component/page, or create new UI with multiple genuinely different approaches to compare — before writing production code or committing to a direction. For a lighter, single-component variant picker with no interview, use `prototype` instead. For reviewing a UI that's already real (not exploring new directions), use `visual-review`. Source: adapted from github.com/0xdesign/design-plugin's design-lab skill (interview + 5-variant structure), with feedback collection replaced by this repo's own `visual-review` skill (human-review) instead of a bespoke overlay component.

Creates decision-focused PRDs and product specs — the kind that make explicit decisions, not document hopes. Make sure to use this skill whenever someone asks to write, review, draft, or improve any product document, including PRDs, feature specs, requirements docs, or product specifications. Trigger even when the user doesn't say "PRD" explicitly — phrases like "write a spec for X", "define requirements for Y", "what should my PRD include", "help me document this feature", or "my spec feels too vague" all apply. Do not attempt to write the PRD directly without consulting this skill. Produces 5-stage PRDs with behavior contracts (15-25 labeled examples for AI features), measurable success metrics with specific thresholds, precise rollout plans with percentages and ramp gates, and antipattern detection. Works for AI features, SaaS, mobile apps, and traditional software.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.

Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.

Identifies and designs growth loops (flywheels) for sustainable traction — evaluating 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral. Use when designing growth mechanisms or reducing reliance on paid acquisition. Triggers on: growth loop, flywheel, viral loop, referral program, product-led growth, PLG, user acquisition, growth strategy, retention loop, compounding growth.

Expert Socratic discovery skill for exploring ideas, architecture decisions, and technical design before writing any code. Use this skill — proactively and always first — when requirements are vague, when the user is debating between technical approaches, when the problem is unclear, or when a design decision could have significant architectural consequences. Triggers on: "should we use X or Y", "help me think through", "I'm not sure how to approach this", "what's the best architecture for", "trade-offs between", "design before I code", "let's think through this", "I have an idea", "how should I structure", "help me design", "I want to build X but not sure how", "what approach would you recommend", "is this the right way to". Produces a validated design doc with 2-3 implementation options, trade-offs, and a recommendation. Always use before planning when the approach is not yet locked.

Agent Workflow Designer

Generates a bespoke brand identity for a new project through a short interview, then writes it as a DESIGN.md file (Google Stitch format) in that project's own repo. Use when starting a new project and its visual identity isn't defined yet, when asked "what's the brand for X", "define the brand for this project", "new project design system", or before the first UI work on a fresh project. Do NOT use this to restyle or elevate a project that already has an identity — that's `taste-redesign`.

Planning Product Launch

Shared vocabulary for designing deep modules — a small interface hiding a lot of behavior. Use when designing or improving a module's interface, deciding where a seam belongs, deciding whether to extract or merge modules, or making code more testable.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Maintains a project's domain vocabulary and records architecturally-significant decisions as they're made — a CONTEXT.md glossary and gated ADRs, not passive documentation read once. Use when terminology conflicts or turns fuzzy, when making a decision that's hard to reverse/surprising/a real trade-off, or when a stated domain rule doesn't match what the code actually does.