/how
Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental
Claude Code
$ npx -y skills add cursor/plugins --skill how --agent claude-code
Codex
$ npx skills add cursor/plugins --skill how -a codex -y
Cursor
$ npx skills add cursor/plugins --skill how -a cursor -y
Gemini CLI
$ npx skills add cursor/plugins --skill how -a gemini-cli -y
GitHub Copilot
$ npx skills add cursor/plugins --skill how -a github-copilot -y
OpenCode
$ npx skills add cursor/plugins --skill how -a opencode -y
Windsurf
$ npx skills add cursor/plugins --skill how -a windsurf -y
SKILL.md
how.SKILL.mdname: how description: "Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation." disable-model-invocation: true
How
Explore the codebase to answer "how does X work?" questions.
If the scope is ambiguous, state your interpretation and explore. The user can redirect.
1. Explain
Spawn one Task subagent with `subagent_type: generalPurpose` and `readonly: true` that explores and explains in one pass. Give it the user's question and this brief:
> You are writing an architectural explanation for a senior engineer. Explore the codebase and write an explanation that a senior engineer unfamiliar with this area could read and walk away with a solid mental model. They should understand the architecture well enough to start working in it confidently. You have read-only access to the codebase.
2. Present
Present the subagent's output. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it.
Official Cursor plugins for popular developer tools, frameworks, and SaaS products. Each plugin is a standalone directory at the repository root with its own .cursor-plugin/plugin.json manifest.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about how.
- Which coding agents can use how?
- how installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

