Coding standards, frameworks, refactoring, and code review (16.9K skills)
Use this skill to structure Java Spring Boot backends, from REST controllers and service layers to Spring Data access. It offers examples for validation, error handling, caching, asynchronous work, logging, pagination, retries, rate limiting, and production configuration.
Run formatters and linters after each file edit, then delegate remaining violations to a Claude subprocess for repair and verification. The hooks also protect linter configuration files and support several languages and file formats.
Use this skill to write, review, or refactor modern C++ code with guidance based on the C++ Core Guidelines. It covers safer types, resource ownership, errors, concurrency, templates, and standard library choices, helping keep code consistent and clear.
Apply practical patterns for React and Next.js interfaces, covering component composition, state management, data fetching, forms, accessibility, and performance techniques such as memoization, lazy loading, and list virtualization.
Choose which Everything Claude Code skills and rules to install for a user or project. The guide copies the selected files, checks paths and cross references, reports problems, and can tailor installed content to the project.
Use this example as a template for a project-specific skill that helps an agent work within a particular application. It demonstrates how to document architecture, file layout, coding patterns, testing expectations, and deployment steps for consistent project work.
Apply JPA and Hibernate patterns in Spring Boot for entity mapping, relationships, repositories, transactions, auditing, pagination, indexing, and connection pools. The guidance also covers query tuning, including ways to prevent N+1 queries, and database migration practices.
Design a file cache that identifies inputs by SHA-256 content, so results from costly work such as PDF parsing or image analysis can be reused after files move or are renamed. Changed content gets a new cache key, while cache handling stays separate from processing functions.
Use this skill to design or review REST APIs, including resource URLs, HTTP methods and status codes, pagination, filtering, errors, versioning, and rate limits. It helps make endpoint behavior and response formats consistent for clients and developers.
Coordinate multiple AI agents working on a large software project in parallel. The skill uses Git tasks and worktrees to let agents claim work, share progress, and contribute changes, with scripts and a dashboard for monitoring and control.
Guides teams planning, building, testing, or reviewing Stripe integrations. It helps select suitable APIs and test environments for payments, subscriptions, marketplaces, and tax, while covering secure key handling, webhooks, and migration from deprecated patterns.
Build, modify, or review Stripe Apps and extensions for Dashboard interfaces, scripts, workflow actions, authentication, and event handling. The skill checks documented product capabilities and limitations, selects relevant implementation guidance, and helps determine whether an extension fits a billing or workflow need.
Plan a Stripe version upgrade across API pins, webhook destinations, server SDKs, Stripe.js, and mobile SDKs. The skill checks the target version, highlights relevant migration steps, and helps stage and test changes while distinguishing versioned snapshot events from unversioned thin events.
Search and retrieve Stripe documentation and API references from the terminal. Use it to check how a product or endpoint works, find guidance by keyword, and access gated documentation after signing in with the Stripe CLI.
Plan, implement, review, and evaluate MCP servers that let AI agents work with external APIs and services. The guide covers Python with FastMCP and Node or TypeScript with the MCP SDK, including tool schemas, errors, and realistic evaluations.
Turn performance investigation data, experiment results, profiling evidence, and tested hypotheses into concise recommendations and next steps. The skill cites only evidence found in logs or code, and flags insufficient data when another run is needed.
Review skill-bus session telemetry at work transitions to see which skills were intercepted, which subscriptions may be missing, and which conditions caused skips. Receive a brief interpretation and possible subscription improvements based on the available data.
Build and review React or Next.js interfaces with TypeScript and Tailwind CSS. Get help creating components, checking accessibility, examining bundle size, and applying performance patterns such as choosing server or client components appropriately.
Investigate a specific performance scenario by checking relevant Git history and code paths, then produce up to five evidence-backed hypotheses with confidence levels. It helps focus investigation without proposing optimizations or fixes.
Review active skill-bus subscriptions from global and project configuration together. See merge status, conditions set at both insertion and subscription levels, how those conditions combine, and optionally simulate which subscriptions would match a scenario.
Reviews recent Claude Code chats to summarize work patterns, highlight recurring challenges and strengths, and suggest areas to study. It gathers relevant articles and discussions from HackerNews and sends a personalized development report to Slack DMs.
Appends structured notes for each performance investigation phase, preserving exact user quotes alongside summaries, decisions, and evidence pointers such as files, metrics, and commands. It stores notes under the configured state directory for later reference.
Map the code paths related to a performance scenario before profiling. The skill identifies entry points, handlers, and likely hot files, then lists relevant files and symbols with brief evidence and call-chain context where useful.
Store performance metrics and environment details in one JSON baseline per version, then use those baselines to organize results and compare versions. The skill specifies where each file belongs and how same-version updates are handled.