Guide for creating optimized Claude Code agents. Use to design a new specialized agent, a swarm sub-agent, or a multi-agent workflow. Follows the Skill → Agent (preloaded skills) → Skill orchestration pattern.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
43건(DGouron의 저장소) · 인기순
Guide for creating optimized Claude Code agents. Use to design a new specialized agent, a swarm sub-agent, or a multi-agent workflow. Follows the Skill → Agent (preloaded skills) → Skill orchestration pattern.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Anti-overengineering guide based on YAGNI. Use before adding an architectural pattern, during code review, or to challenge an overly complex implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit documentation for duplication, staleness, language issues, and verbosity. Read-only — produces an actionable report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Local auto-review of modified code (no GitLab/GitHub). Runs 5 sequential audits and generates a local report. Ideal for validating code before creating a MR/PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clean Architecture (Uncle Bob) guide for this project. Use when creating modules, entities, use cases, presenters, controllers, gateways, guards, services. Contains tactical patterns and structure conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clean Code (Robert C. Martin) guide to produce and challenge code that is readable, durable, simple, and consistent. Covers naming, functions, comments, smells, and refactor heuristics. Complements `/solid` (SOLID principles) and `/anti-overengineering` (YAGNI/KISS). Activate during the REFACTOR phase of the TDD cycle and during implementation self-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safe commit and push workflow. Creates a commit following conventions and pushes. Husky handles verifications (TypeScript, Biome, tests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a new documentation file following project standards. Detects overlap with existing docs before creating.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strategic DDD guide for this project. Use to split the domain into bounded contexts, define ubiquitous language, create new business modules, or analyze context boundaries. Tactical patterns follow Clean Architecture (see architecture skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Business discovery before technical specs. Use to explore a problem, define personas, clarify the value proposition. Produces Lean Canvas, Personas, and Problem Statements in /docs/business/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate or update the centralized documentation index (docs/INDEX.md) with navigation map and cross-references.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for Playwright end-to-end tests. Use to create a new e2e test, debug a flaky test, or test API endpoints. Covers patterns, workarounds, and project conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Event Storming Big Picture on a bounded context or the whole project. Explores code to discover domain events, commands, entities, context boundaries, and produces structured markdown following Vaughn Vernon's strategic patterns. Usage: /event-storming <bc-name> or /event-storming global
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomous feature implementation via spec-driven development. Orchestrates a planner and a TDD implementer with preloaded skills. Consumes Gherkin specs produced by /product-manager.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Challenge and specification of tickets/user stories. Use to define a feature, write acceptance criteria, scope a ticket, score with RICE. Produces INVEST specs with DSL in /docs/specs/. Subcommands: rice, ticket.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomous refactoring via spec-driven development. Orchestrates contract tests, batch planning, and incremental implementation with regression checks. Reuses feature-planner and feature-implementer agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for large-scale refactorings with Mikado and Strangler Fig. Use for architecture migration, library replacement, module splitting, or pattern changes. Maintains a Mikado graph to track dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete code review of a backend MR/PR with 8 sequential audits (Clean Architecture, DDD, TypeScript Best Practices, SOLID, Testing, Code Quality, Security, Performance). An orchestrator runs each audit one by one to avoid memory spikes. Generates an .md report and posts it directly on the MR/PR. Direct mode with sourced lessons.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete review of a documentation-focused MR/PR with 5 sequential audits oriented for documentation projects (markdown-quality, link-validity, terminology, freshness, examples-validity). No code-architecture audits, no React patterns, no SOLID. An orchestrator runs each audit one by one. Generates an .md report and posts it directly on the MR/PR. Direct mode with sourced lessons.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Follow-up review to verify corrections on a MR. Sequential execution to avoid memory spikes. Checks blocking issues, detects new problems, and posts a concise report on GitLab.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete code review of a MR/PR with 7 sequential audits (Clean Architecture, DDD, TypeScript Best Practices, SOLID, Clean Code, Testing, Code Quality). An orchestrator runs each audit one by one to avoid memory spikes. Generates an .md report and posts it directly on the MR/PR. Direct mode with sourced lessons.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete code review of a fullstack MR/PR with 8 sequential audits (Clean Architecture, DDD, React Best Practices, SOLID, Testing, Code Quality, Security, Performance). The audit set is the deduplicated union of review-front and review-back — no audit runs twice. An orchestrator runs each audit one by one to avoid memory spikes. Generates an .md report and posts it directly on the MR/PR. Direct mode with sourced lessons.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code scan to detect secrets before commit. Use before git add/commit/push or on demand. Checks for tokens, API keys, credentials, and other sensitive data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ship — commit and push in one command. Chains quality gates, conventional commit, push, and optional PR creation + merge. Use when the user says "ship", "commit and push", "/ship", or wants to finalize a branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.