스킬 찾기

Set up dependency-cruiser in a TypeScript repository to enforce package boundaries: outside code uses public entry files while implementation stays in subfolders. Add checks, a starter package, and documentation, then verify that forbidden imports fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preventing imports into package internals
• Adding boundary checks to existing validation commands
• Creating a starter package with public entry files

Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a branch or pull request
• Check changes since a specific commit
• Find missing requirements or unintended scope

Set up Claude Code hooks that block specified Git commands before they run, including push and destructive cleanup operations. Choose project or global installation, adjust the blocked commands, and test that the hook rejects a sample command.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Blocking git push from Claude Code
• Preventing commands that discard local changes
• Installing Git guardrails across projects

Write and revise documents that guide AI agents, including skills and AGENTS.md files. Organize steps, define checkable completion criteria, and clarify when to load references so agents can follow a consistent process across different tasks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write or revise instructions for a skill
• Review AGENTS.md or CLAUDE.md guidance
• Move detailed references out of an overloaded main document

Ask an agent to restate an unclear message with more background, using the conversation's language and the project's glossary. It applies simplified technical writing guidance to help explain how the discussion reached its current point.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Asking for a clearer explanation of the previous message
• Adding background to understand the reasoning
• Aligning explanations with project glossary terms

Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Simplify a module interface
• Review module structure during refactoring
• Decide where behavior should be swappable

Shape Markdown notes, fragments, or transcripts into a separate article through a collaborative drafting session. Choose an opening, establish what readers already know, and develop each paragraph or block in an order that introduces concepts before relying on them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning scattered notes into an article
• Developing an article from a transcript
• Comparing openings to choose an angle

Set up checks that run before each commit using Husky, lint-staged, and Prettier. Format staged files, run existing type-check and test scripts, then verify and commit the configuration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding automated checks before commits
• Formatting staged files with Prettier
• Running type checks and tests before committing

Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose a workflow for turning an idea into working software
• Find the starting point for a difficult bug investigation
• Plan specifications and tickets for work across multiple sessions

Diagnose difficult bugs and performance regressions by first building a repeatable check for the exact symptom. Minimize the reproduction, test ranked hypotheses, apply a fix, and verify the original scenario with regression tests where suitable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating persistent errors or incorrect output
• Increasing reproduction rates for intermittent bugs
• Measuring and diagnosing performance regressions

Turn a specification and its linked tickets into code. Multiple agents work on available tasks in separate worktrees, combine changes on one integration branch, and complete a code review before preparing the result for review or closing tickets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a specification and its linked tickets
• Working through tasks with blocking dependencies
• Coordinating parallel implementation in separate worktrees

Implement work described in a specification or set of tickets, using test-first development where agreed. Run type checks and tests throughout, review the completed changes, and commit the work to the current branch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing work from a specification
• Completing a set of development tickets
• Checking changes with types and tests

Review a codebase for design friction and compare refactoring candidates in an HTML report with before-and-after diagrams. Then explore a chosen candidate through questions about constraints, module design, and testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find design problems in frequently changed code
• Compare refactoring candidates with diagrams
• Explore constraints and tests for a chosen improvement

Draft or revise pull request descriptions that show the change, evidence of its behavior, and merge risks. Use concise diagrams, trees, or diffs alongside before-and-after results to help reviewers assess impact and how easily changes can be reversed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a description for a pull request
• Explain a refactor with a tree or diff
• Present before-and-after evidence for a fix

Build a disposable prototype to answer a specific design question. Use a shareable HTML demo to explore logic and state changes, or compare distinct UI variations on one route, then record the decision and retain the prototype separately.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trying state transitions through an interactive demo
• Sharing a logic prototype with non-developers
• Comparing distinct UI designs on one route

Research a question using original sources such as official documentation, source code, and specifications. A background agent records findings with sources for each claim and saves a Markdown note following the repository’s existing conventions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Researching a topic using official sources
• Checking documented API behavior
• Saving research notes with sources

Set up the repository settings that engineering skills read: where work is tracked, which triage labels to use, and where domain documents belong. Review existing files and confirm drafts before writing configuration documents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a repository before using engineering skills
• Configure GitHub, GitLab, or local Markdown issue tracking
• Match triage labels to an existing workflow

Build features or fix bugs by writing one failing test, then the minimum code needed to pass it. Test agreed public interfaces, the boundaries callers use, to check behavior without depending on internal implementation details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a feature through test-first development
• Fixing a bug with a failing test first
• Writing behavior-focused integration tests

Turn an existing conversation and codebase context into a feature specification. Organize user needs, implementation decisions, testing plans, and scope, then publish the specification to the project’s issue tracker with a label marking it ready for agent work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a feature discussion into a specification
• Recording implementation and testing decisions
• Publishing an issue ready for agent work

Turn plans, specifications, or conversations into small implementation tickets that each deliver verifiable behavior. Define acceptance criteria and dependencies, review the breakdown together, then publish approved tickets to the configured tracker or local Markdown files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Break a specification into independently verifiable tickets
• Clarify ticket dependencies and starting order
• Publish approved tickets to a tracker or local files

Review issues and external pull requests, classify them, verify their claims, and assign a handling state. The skill checks existing implementations and past rejections, requests missing details, and prepares briefs that agents or human maintainers can act on.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find issues and external PRs needing attention
• Reproduce reported bugs and verify PR changes
• Prepare work briefs for agents

Turn a large, unclear idea into a shared map of decisions in an issue tracker. Record answers, dependencies, and unresolved questions across sessions until the route to a defined goal is clear enough to hand off.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarify decisions before starting a large project
• Map unresolved questions and their dependencies
• Carry planning decisions across agent sessions

Create an interactive bash script that guides people through manual setup or migration tasks. It opens relevant pages, explains each action, collects values, and saves settings to .env files or GitHub secrets with confirmation steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Guide someone through an unfamiliar service dashboard
• Collect credentials and configure CI secrets
• Walk through a one-time migration or cutover

Summarize the current conversation and launch a fresh background agent to continue the work. The handoff includes references to existing artifacts and suggested skills, removes sensitive information, and can emphasize the next session’s intended focus.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Continue ongoing work with a fresh agent
• Focus the next session on a specific task
• Hand off work using references to existing documents