94.8K skills · sorted by popularity
Carry out an existing implementation plan in one session, task by task. Verify each step with tests, record progress and decisions in a file, and finish with a review of all changes on the branch.
Carry out an implementation plan by assigning each task to a separate agent, then reviewing specification compliance and code quality. Keep progress in files and review the complete set of changes after all tasks are finished.
Create, revise, and validate agent skills through tests that compare behavior with and without the instructions. It helps identify unclear guidance, choose an appropriate document structure, and refine wording before deployment.
Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.
Refine a plan or design through a persistent interview that asks probing questions. This skill starts the conversation by invoking the related grilling skill, providing an entry point for examining and sharpening what you have in mind.
Explore a writing topic through probing questions and collect promising sentences, anecdotes, metaphors, and unfinished thoughts. It saves these fragments in a single Markdown file, giving you raw material to develop before deciding on an outline.
Turn a decision that needs someone else’s knowledge into a Markdown questionnaire. Clarify who will answer and what information is needed, then create prioritized questions with answer spaces for asynchronous replies or a meeting.
Turn plans, specifications, or conversations into small development tickets that each deliver verifiable behavior. Identify which tickets must finish first, review the breakdown together, and publish approved tickets to local files or the configured issue tracker.
Set up Claude Code hooks that block Git commands such as push, hard reset, and forced deletion before execution. Choose project-wide or global settings, customize the blocked commands, and verify that the hook rejects a test command.
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.
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.
Coordinate subagents, separate agents assigned tasks, to pursue a long-running goal in one session. Maintain dialogue with the user while improving working conditions, shared rules, and access to information needed for future tasks.
Learn a new skill or concept through short, interactive lessons tailored to your goals and previous learning. The skill creates HTML lessons, reference sheets, and learning records to support practice and review across multiple sessions.
Examine a plan, decision, or idea through structured rounds of questions with recommended answers. Organize dependent decisions into a branching map, resolve assumptions, and build a shared understanding before taking action.
Investigate a question using official documentation, source code, specifications, and first-party APIs. A background agent records the findings in one Markdown file with sources for each claim, following the repository’s existing conventions for research notes.
Ask the agent to explain its last message again with some context. The revised explanation uses ASD-STE100, a simplified technical English standard, and the vocabulary defined in the project's glossary.
Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.
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.
Summarize an ongoing conversation and launch a fresh background agent to continue the work. The handoff includes the next focus, references to existing documents, and suggested skills, with sensitive information removed.
Turn an existing discussion and codebase knowledge into a specification, then publish it to the project's issue tracker. Organize the problem, user needs, implementation decisions, testing approach, and work excluded from scope.
Turn notes, fragments, or transcripts into an article through a paragraph-by-paragraph discussion. Compare opening options, establish what readers need to know, and save agreed sections in a separate document while preserving the original material.
Prepare a repository for engineering skills by documenting where issues are tracked, which triage labels organize incoming work, and where glossaries and architecture decision records belong. Review the existing setup and confirm drafts before writing configuration files.
Summarize the current conversation into a handoff document so another agent can continue the work. Reference existing project materials, suggest skills for the next session, and redact sensitive information.
Turn recurring work or life activities into workflow specifications through focused questions with recommended answers. Clarify triggers, human review, and decision summaries so an implementation agent can build the workflow without further questions.