humanize-as-kevin-xiao
|
git-worktree
Create isolated git worktrees in ~/.claude-worktrees/. Use when user says "create an isolated copy", "worktree", "create worktree", "isolated workspace", or needs to work on a branch without affecting the main working directory.
completion-check
Run a completion checklist over the current change set when work is considered done and ready to commit. Checks for correctness, simplification candidates, comment and prose audits, and repository-specific checks. Use before marking a task complete, e.g. before committing or pushing to open a PR, or when the user says "commit for me", "open a PR", "are we done".
linear-uploads
Download attachments and images from Linear issues. Use when fetching screenshots, images, videos, or file attachments from Linear comments or descriptions. Also use when user says "get the image from the ticket", "download the video", or "download the attachment".
SEO Optimizer
Search Engine Optimization specialist for content strategy, technical SEO, keyword research, and ranking improvements. Use when optimizing website content, improving search rankings, conducting keyword analysis, or implementing SEO best practices. Expert in on-page SEO, meta tags, schema markup, and Core Web Vitals.
skill-writer
Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
ui-skills
Opinionated constraints for building better interfaces with agents.
api-design
REST API design patterns for endpoints, responses, errors, and conventions
python
Python coding conventions, type hints, and FastAPI patterns
security-check
Security audit patterns for identifying vulnerabilities and security issues
testing
Testing strategy, patterns, and best practices for unit, integration, and e2e tests
typescript
TypeScript and React/TSX coding conventions and patterns
code-review
Systematic code review checklist for quality, correctness, and maintainability
go
Go idioms, error handling, and API patterns
project-structure
Project organization conventions for files, modules, and directory structure
typescript-refactor
Safely refactor TypeScript code while maintaining type safety and test coverage. Includes verification steps.
react-component-create
Create new React components following project patterns and best practices. Includes proper typing, testing, and documentation.
resilience-check
Checklist for reliability engineering
security-audit
Procedure for analyzing code or dependencies for vulnerabilities
test-suite-create
Creates a comprehensive test suite for a feature
professor-for-testing-agentic-qe-skill-builder
Build comprehensive testing skills with TDD, quality engineering, and automated test generation. Use when creating test suites or improving testing practices.
git-commit-message
Auto-generates conventional commit messages from git diffs with tiered format enforcement. Analyzes staged changes to produce meaningful commit messages following Conventional Commits specification.
obra-superpowers-test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
obra-superpowers-systematic-debugging
Systematic debugging approach with 4-phase root cause analysis. Use when troubleshooting complex bugs, identifying root causes, or following structured debugging methodology.
obra-superpowers-brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
muratcankoylan-agent-skills-for-context-engineering-memory-systems
Context management and persistent memory systems for AI agents. Use when optimizing context windows or building agent memory systems.
modu-ai-moai-adk-moai-tool-opencode
Multi-agent orchestration using MoAI framework for complex task coordination. Use when orchestrating multiple agents or building multi-agent workflows.
maxritter-claude-codepro-backend-models-standards
Backend development standards and best practices for API design, database, security, and performance. Use when designing or reviewing backend systems.
obra-superpowers-writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
pattern-extraction
Extracts reusable patterns from code changes
obra-superpowers-using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
database-migration-create
Safely creates database migrations
docs-update
Standard procedure for updating documentation
git-commit-standard
Generates conventional commits based on file changes. Analyzes diffs and creates properly formatted commit messages.
dependency-audit
Audit npm dependencies for security vulnerabilities, outdated packages, and license compliance.
code-review-checklist
Generates a code review checklist for the Code Reviewer agent
madappgang-claude-code-debugging-strategies
Universal debugging strategies and techniques applicable across all technology stacks. Use when approaching unknown bugs or need language-agnostic debugging methodology.
api-endpoint-create
Standard procedure for creating robust API endpoints
ci-pipeline-update
Updates CI/CD pipelines for DevOps Engineer
decision-log
Persist a decision that has just been settled — the alternatives rejected, the reasoning, the consequences accepted, and the condition for revisiting it — into one database shared by every repository, and retrieve past ones from any of them. Use at the moment a design, architecture, or tooling choice stops being weighed and becomes what will be done, and whenever the alternatives or rationale behind an earlier choice are asked for, including a choice settled while working somewhere else. Not for choices without meaningful trade-offs.
japanese-writing
Revise Japanese developer-facing technical writing — planning/design docs, meeting materials, issue/PR text, team chat posts — to read plain and accurate: cut overstatement, coined jargon, filler, and blame aimed at people; fix loose paragraphs and notation (spacing around half-width alphanumerics). Use when writing or editing such Japanese prose, including small edits to already-drafted or posted text. Not for English, reference docs, or CLI text.
external-repo
Use whenever you decide you need to inspect a third-party repo's source on disk — explicit (user pastes a repo URL asking about its contents, "how is X implemented in library Y") or implicit (you yourself proposing mid-conversation to fetch an OSS project to investigate). Managed via ghq for direct Read/Grep. DO NOT USE for one-off doc/raw-file lookups (WebFetch) or work inside the user's own repo.
devils-advocate
Examine a direction the user has already settled on from both sides at once, each side argued by an independent agent that sees neither the other nor the assessment forming in this conversation. Use before answering someone who presents a course as decided and asks whether to proceed — whether the answer taking shape is agreement or rejection, and above all when the course is the user's own and agreeing would cost nothing — to surface what it rests on and what would settle it. Not for an option still being floated, where no course has been chosen yet. Reports whichever side holds, including when only one does.
test-perspectives
Use when writing or expanding tests for code with branching conditions, state transitions, input boundaries, or operational failure modes.
bonsai
Maintain and groom config files in the current repository. Use when reviewing config health, pruning unused entries, fixing cross-file inconsistencies, applying format changes after tool upgrades, or doing periodic config tidy-up. Not for code quality review of application source.
tdd-first
Pin the expected outcome down as a failing test before writing production code. Use when a change alters observable behavior — new logic, a bug fix, a modified rule. Not for config, docs, or refactors that keep behavior identical.
socratic
Interview the user one question at a time to turn a half-formed idea into a plan they own. Use when the user muses a tentative idea of their own ("maybe I should X", "I'm thinking of X") rather than asking for a verdict — develop it by questioning, not by recommending; also for pressure-testing a plan decision-by-decision. Not for explicit requests for a recommendation, plain build requests, or rubber-stamping a finished plan.
skill-eval
Evaluate and tune an LLM-facing instruction doc — a skill, subagent prompt, or CLAUDE.md/rule addition — by having a fresh subagent execute it blind against frozen scenarios and iterating fixes until improvements plateau. Use right after authoring or substantially revising such a doc, or when a skill misbehaved and instruction-side ambiguity is suspected rather than model failure. Not for typo-level wording changes or personal-taste polish.
Page 1550 of 1700 · 84990 results
