14.9K skills · sorted by popularity
Set up dependency-cruiser in a TypeScript project to enforce package boundaries, keep internal files private, and detect circular dependencies. Includes an example package, verification of the rules, and documentation for future development.
Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.
Clarify a project's business concepts and terminology through concrete scenarios and comparisons with code. Record agreed definitions in a glossary and document significant design trade-offs in ADRs, records explaining why a decision was made.
Sharpen a plan or design through persistent questioning while creating documentation along the way. The resulting documents include architecture decision records, which capture design choices, and a glossary of terms used in the discussion.
Turn a specification and its tickets into code by coordinating multiple agents around task dependencies. Combine their work on one integration branch, use test-driven development, review the result, and close tickets through the issue tracker’s workflow.
Review a codebase for structural problems that make understanding and testing difficult. Compare refactoring candidates in an HTML report with before-and-after diagrams, then explore the chosen option through questions about constraints, design, and tests.
Implement work described in a specification or tickets, checking types and running tests along the way. Review the completed changes with the code-review skill, then commit the implementation to the current branch.
Sort issues and external pull requests, which are proposed code changes, by category and readiness. Verify reports, identify missing information, and record clear briefs so an agent or a person can take the next step.
Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.
Write a pull request description that helps reviewers understand a code change. Use a compact diagram or diff, show before-and-after evidence, and explain how reversible the change is and what areas it may affect.
Check skills before distributing them to Codex or Cursor. Identify unsupported metadata fields, Claude-specific variables in shell examples, and inconsistencies between source skills and their installation copies using the project's compatibility checker.
Set up Everything Claude Code skills and hooks in DeepSeek Harness. Covers linking skill folders, generating hook settings, checking that hooks run, updating the setup, and investigating missing skills or inactive hooks.
Audit a focused part of an existing codebase, reconstruct its behavior and past decisions, and record gaps in reasoning, coding practices, features, and technology choices. Use the findings to plan, test, implement, and verify improvements.
Map the impact of a proposed change using real dependencies and project documentation. Identify affected code, data, interfaces, tests, and release steps, then compare the implemented changes with the plan to expose gaps and unverified risks.
Design and review Java database code using MyBatis and MyBatis-Spring. Covers mapping query results to objects, safe SQL parameters, transactions, pagination, batch writes, and investigating slow or unnecessarily repeated queries.
Turn Git changes into a clear commit message using Conventional Commits, a format that labels the change type and optional scope. Review repository history to match its conventions, and flag unrelated changes that should be split.
Apply shared coding conventions to new modules, reviews, and refactoring. Guides descriptive naming, readable structure, updates that preserve existing data, and error handling, giving teams a consistent basis for checking code quality.
Plan database structure changes and existing data updates for production systems. Provides migration patterns for adding columns and indexes, switching applications in stages, and documenting recovery steps while accounting for downtime and database locks.
Turn Claude Code sessions into reusable working rules with evidence and confidence scores. Keep project-specific habits separate, share general patterns across projects, and group learned rules into skills, commands, or agents for repeated tasks.
Structure server-side applications with practical patterns for Node.js, Express, and Next.js API routes. Covers API design, database queries, caching, authentication, error handling, and background jobs, with examples that separate business rules from data access.
Design and review REST APIs, interfaces that exchange resources over HTTP, with consistent URLs, responses, and error handling. Covers pagination, authentication, request limits, and versioning to clarify how clients interact with an API.
Run repository commands, inspect Git state, investigate CI or build failures, and verify focused fixes. Report the commands and results as evidence, clearly distinguishing local changes, local verification, commits, and pushes.
Build Java applications with tinystruct, including actions usable from both a terminal and the web. Get guidance on launcher generation, routing, JSON responses, database storage, tests, and MCP tools that agents can call.
Coordinate multiple AI agents with assigned owners, clear work boundaries, and a Kanban board that tracks progress. Organize separate branches or worktrees, collect test and handoff evidence, and define checks that must pass before combining their work.