writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Follows TDD methodology.
Découvrez les skills Documentation, comparez leurs dépôts et consultez leurs instructions.
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Follows TDD methodology.
Use when creating new agents, defining agent roles, or configuring agent handoff protocols and model selection.
Vitest, Playwright, and testing strategies. Use when writing tests, setting up test infrastructure, or debugging test failures.
Use when creating hooks for prompt interception, permission handling, or event-triggered automation with timeout and bypass handling.
Schema design, migrations, queries, and indexing strategies. Use when designing database schemas, writing migrations, or optimizing queries.
Use when designing UI components, implementing accessibility, responsive layouts, or integrating with design systems.
Use when sharing development progress publicly. Covers progress sharing, changelog writing, social media updates, community engagement, and milestone announcements.
Core skill for understanding and using the Jarvis skill system. Loaded at every session start.
Refine Linear tickets tagged "refine" or in triage. Pull GitHub context, clarify scope, add acceptance criteria, improve descriptions. Triggers - refine ticket, ticket refinement, triage, improve ticket.
Use when following a written plan or task list. Checkpoint verification at each step. Triggers - execute plan, follow plan, implement plan, next step, continue, proceed.
REST/GraphQL API design patterns, error handling, and versioning. Use when designing APIs, handling errors, or making API architecture decisions.
Use when optimizing for search engines, creating content, or implementing structured data. Covers meta tags, schema markup, and content structure.
Use for parallel branch development with workspace isolation.
Use when work spans multiple phases, requires context handoff, or exceeds single conversation scope. Triggers - session, multi-phase, handoff, continue, resume, checkpoint, long-running.
Use when implementing web scraping, data extraction, or automated browser interactions. Covers Puppeteer, Playwright, rate limiting, and ethical scraping.
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.
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é.