1.6천건 · 관련도순
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find and fix WCAG 2.2 accessibility issues. Two modes — report (sweep a codebase or page, produce a prioritized written report, no edits) and fix (audit→edit→verify loop on a target). Prefers direct-CDP live-DOM auditing; falls back to a browser-MCP composition or HTML-string audits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure every factual claim in a response is backed by verifiable evidence from the codebase, documentation, or external sources. Use when preparing technical documentation, code reviews, or any output where accuracy is non-negotiable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Harvests a DESIGN.md from an existing codebase, critiques it against the actual code, and applies safe quick-win fixes. Three modes harvest / critique / fix. Shells out to `npx @google/design.md lint` for structural validation; never reimplements Google's linter. The on-ramp that makes DESIGN.md adoptable for every existing repo, not just greenfield projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
detailed information about kitten space agency (KSA) game code, decompiled sources, modding patterns, architecture and best practices for working with mods and the game codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); other stacks allowed by user decision. Do NOT use to implement code or when approved SPECs already cover the migration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research the codebase to answer a question without making any changes. Use when exploring code, understanding architecture, or investigating how something works.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design conventions for this codebase. Use whenever writing or reviewing API endpoints, route handlers, or HTTP clients.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan the codebase for common security issues: hardcoded secrets, SQL injection vectors, XSS, unvalidated inputs, and insecure defaults. Use before deploying, as part of code quality review, or when asked to check for security issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate two separate areas of the codebase simultaneously and combine findings into a comparison report. Use when you need research on two independent topics at once, want to compare two subsystems, or need to understand how two components relate to each other.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a README.md for the current project by analyzing the codebase structure, package files, and existing documentation. Use when asked to write a README, create documentation, or document the project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Product Owner - scans codebase and creates or amends GitHub issues with PRD. Use when: PRD, feature, issue, create issue, amend issue, what should we build, plan feature, design feature, scope, requirements, user story.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate beautiful, on-brand HTML artifacts — reports, diagrams, diff reviews, slide decks, plans, recaps, dashboards. Loads on creation intents ("create a plan", "make me an implementation plan", "generate a diagram", "build a slide deck", "draft a recap", "visualize this", "render this as HTML", "make me a status update") and exploration intents ("show me three layouts", "explore document shapes", "compare visual treatments", "explore a new design system", "compare replacement brand directions") and iteration intents ("make this beautiful", "polish this report", "make this less generic", "design this", "theme this", "use my brand", "iterate on this design", "review this artifact", "make this bolder", "make this quieter", "simplify this design", "animate this", "improve the look of", "give this a refresh"). Captures brand from the user's codebase, asking, or live site, then applies it to every artifact.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep multi-pass codebase audit — orchestrates project-analysis-core plus the framework-specific project-analysis-*; explicit request only. Single-pass scan → project-analyzer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate whether a feature request fits the existing codebase — check for duplicates, contradictions, scope creep, and architectural misfit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when surfacing tech debt as trackable items — interest-vs-principal framing, prioritisation by carrying cost, repayment plan — even if the user just says 'this codebase is a mess'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.