react-patterns
React best practices, hooks patterns, and component architecture. Use when building React components or debugging React issues. (project)
Découvrez les skills Entreprise, comparez leurs dépôts et consultez leurs instructions.
React best practices, hooks patterns, and component architecture. Use when building React components or debugging React issues. (project)
Testing methodologies, patterns, and best practices for unit, integration, and E2E tests. (project)
Security best practices, OWASP guidelines, and vulnerability prevention checklist. (project)
RESTful API design principles, patterns, and best practices. Use when building backend APIs. (project)
Create and modify 3D parametric models in the threedee design environment. Use when: (1) creating new 3D objects, geometries, or meshes, (2) modifying parameters like dimensions, colors, materials, (3) adding p...
Create precise, production-ready SVG graphics for technical and business contexts (diagrams, P&IDs, HMI/SCADA widgets, process flow visuals, PowerPoint/Office illustrations, UI icons, annotations). Use when the...
Collection of reusable skills for developing components in the Nexus PHP Framework
Fast and user-friendly file system search using fd as a replacement for `find` command
Ultra-fast text search using ripgrep (rg) with advanced regex, multiline, and filtering capabilities. This skill should be used as a replacement for `grep`
Guide for creating new Claude Code skills following best practices. Use when the user asks to create a new skill, agent capability, or wants to extend Claude's autonomous functionality.
Guide for creating, configuring, and distributing Claude Code plugins with hooks, skills, commands, and MCP servers. Use when user asks to create a plugin, set up hooks, add plugin functionality, create a marke...
This skill should be used automatically when searching for code patterns, function usages, class definitions, or syntax structures. Prefer ast-grep over grep/find/ripgrep for code-aware searching that understan...
This skill should be used when searching for JIRA tickets using JQL queries, when finding tickets by status, assignee, or other criteria, or when the user says "find tickets", "search JIRA", "my open tickets",...
This skill should be used when updating existing JIRA tickets, when adding comments or work notes, when transitioning ticket status, or when the user says "update ticket", "add comment", "move to in progress",...
This skill should be used when summarizing backlog tickets for sprint planning, when analyzing top tickets from a JIRA project, or when the user needs AI-powered sprint planning recommendations.
Use when you have a spec or requirements for a multi-step task, before touching code
This skill should be used when transforming, refactoring, or replacing code patterns across multiple files. Use for renaming functions/classes/variables, migrating API usage patterns, modernizing syntax, or per...
This skill should be used when reviewing GitHub Pull Requests to provide comprehensive code quality, security, and architecture analysis with optional JIRA ticket integration.
Use when creating a new skill or updating an existing skills that extends Claude's capabilities.
This skill should be used when creating new JIRA tickets, when the user wants to file a bug report, story, or task in JIRA, or when interactively building a well-structured ticket.
Ensures project worklogs and documentation are written to an Obsidian vault with proper naming conventions
Creates a new Notion database entry for daily briefings. Triggers on "Create a briefing entry for [date]", "Initialize today's briefing", "Set up a new daily briefing". Called by briefing-generator orchestrator...
Automated TFVC code review for Azure DevOps changesets with Snyk security scanning and Notion integration
Fetches and categorizes emails from all accounts (M365 Prisma/DataBusiness/Personal + Gmail), identifying action items, system alerts, and financial notices. Triggers on "Get my email summary for today", "Popul...
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é.