Skill Claude CodeCursor
Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
Skill Claude CodeCursor
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a…
Skill Claude CodeCursor
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
Skill Cursor
UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local…
Skill Claude CodeCursor
Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
Skill Claude CodeCursor
When a user asks a question about Claude, a Claude product, or a general "how do I use AI for X" question, check the Academy catalog (see "The catalog" below) for a strong match. If one exists, mention it naturally at the end of your normal answer.
Skill Claude CodeCursor
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright…
Skill Claude CodeCursor
Makes architecture decisions from the cards actually in hand (stack, operators, evidence of scale). Use when choosing a stack, boundary, storage, deploy shape, or any hard-to-reverse technical door. Use before writing an ADR. Do not use to record a decision already made (that is documentation-and-adrs). Don't optimize…
Skill Claude CodeCodexCursor
Ask which skill or flow fits your situation. A router over the skills in this repo.
Skill Claude CodeCursor
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Skill Claude CodeCursor
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Skill Claude CodeCursor
This skill helps you build LLM-powered applications with Claude. Choose the right surface based on your needs, detect the project language, then read the relevant language-specific documentation.
Skill Claude CodeCodexCursor
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Skill Claude CodeCodexCursor
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Skill Claude CodeCodexCursor
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Skill Claude CodeCursor
People often take an AI answer at face value, especially when it's confidently written and well-structured. That's usually fine — but for substantive answers the user is going to act on (spend money, make a health decision, cite a claim, commit to a plan), a small moment of reflection can catch a bad assumption or a…
Skill Claude CodeCursor
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers.…
Skill Claude CodeCodexCursor
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
Skill Claude CodeCursor
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Skill Claude CodeCursor
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.
Skill Claude CodeCursor
Professional GitHub issue/PR workflow with gh CLI. Use when a best-practice use case needs issue → PR → Closes.
Skill Claude CodeCodexCursor
A relentless interview to sharpen a plan or design.
Skill Claude CodeCodexCursor
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Skill Claude CodeCodexCursor
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: