plan
Use when you have a spec or requirements for a multi-step task, before touching code. Triggers - plan, design, architect, implementation plan, spec, requirements.
Découvrez les skills Données et IA, comparez leurs dépôts et consultez leurs instructions.
Use when you have a spec or requirements for a multi-step task, before touching code. Triggers - plan, design, architect, implementation plan, spec, requirements.
Process PR review feedback, categorize comments, create tracking issues for deferred items, and resolve conversations. Can be invoked standalone or during submit-pr Phase 6.
Use when working with git operations including commits, branches, worktrees, and PRs. Covers the full git workflow from feature isolation to PR submission.
Use when generating ideas, exploring options, defining requirements, or making decisions. Covers both discovery (what to build) and approach (how to build). Triggers - ideate, brainstorm, options, alternatives,...
Use when creating design documents, technical specs, architecture decisions, or system documentation. Covers structure, audience, and validation.
Use when about to claim work is complete, fixed, or passing. Invoke BEFORE committing, creating PRs, or making any success claims. The Iron Law - evidence before assertions, always.
Use when rapidly prototyping ideas into products. Covers MVP scoping, feature prioritization, tech stack selection, timeline estimation, and launch checklist.
Use when working with infrastructure, deployments, Docker, CI/CD, or server management. Covers containerization, deployment workflows, and DevOps patterns.
Use when working with CodeRabbit AI code review. Covers triggering reviews, interpreting feedback, addressing comments, and PR workflow integration.
Meta-skill for rapidly learning new domains. Covers domain research process, expert consultation simulation, knowledge validation, and documentation generation.
Use when implementing payment flows with Stripe or Polar. Covers checkout integration, webhooks, subscriptions, and error handling.
Plan issues for an upcoming Linear cycle/sprint. Review backlog, prioritize, assign to cycle, balance workload. Triggers - cycle planning, sprint planning, plan cycle.
Use when implementing analytics, event tracking, or setting up dashboards. Covers privacy-first tracking, event patterns, and common analytics tools.
Use when debugging frontend issues in the browser. Covers DevTools usage, network debugging, performance profiling, and console patterns.
Resolve Linear issues tagged with "tech-debt". Decide to address now, schedule, or close. Triggers - resolve tech debt, technical debt, debt triage, cleanup.
Use when multiple independent tasks can run simultaneously. Maximizes throughput through parallel Task tool invocations.
Create Linear Issues from requirements using the plan process. Same process as /plan but outputs to Linear Issues instead of file. Triggers - linear plan, plan to linear, create issues from plan.
Use when implementing any feature, bugfix, or code change. Invoke BEFORE writing implementation code. The Iron Law - no production code without a failing test first.
Use when identifying opportunities to improve the Jarvis system, adding patterns, creating skills, or updating rules based on repeated guidance.
Intelligent work tracking. Automatically classifies issues, gathers codebase context, and creates well-formed Linear tickets. Triggers - linear, issue, track, bug, todo, fix, question, debt.
Use when documenting reusable code patterns, architectural approaches, or established solutions with keyword triggers and anti-patterns.
Use before git write operations (commit, push, merge, rebase) to verify you are in a git worktree. Guides worktree setup if missing. Keywords: worktree, isolation, git commit, git push.
GitHub CLI patterns for PR reviews, comments, and API operations. Use when working with gh api commands, especially for review threads and comments.
TypeScript idioms, type guards, utility types, and type-safe patterns. Use when working with TypeScript types, generics, or type safety issues.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.