스킬 찾기

Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.

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

Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.

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

Builds questions and assessments that measure what they claim — matching item type to the thing being assessed, writing distractors that diagnose, and telling a question that measures learning from one that measures reading speed or test-taking. Use this to write or review assessment items, design a unit check or diagnostic, work out why scores do not match classroom performance, or decide how much evidence a claim about mastery actually needs.

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

Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broad search or audit would be faster fanned out, or when deciding whether work can safely be split at all.

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

Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.

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

Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.

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

Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it across models. Use this when a prompt is not producing what was wanted, when output varies run to run, when writing a prompt for a repeated task, when moving a prompt between models, or when someone describes what they want an AI to do and needs it written properly.

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

Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.

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

Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting for review.

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

Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking, and patch policy. Use this to stand up or fix a vulnerability program, triage scanner output, decide what to fix first, set patch SLAs, handle a disclosure from an outside researcher, or report posture to leadership.

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

Runs the production schedule — sequencing and releasing work, managing work in process and changeovers, and holding the promised date when the floor and the order book disagree. Use this to build or fix a production schedule, decide what to run next, diagnose why lead times are growing while machines look busy, set up OEE or throughput measurement, or choose between make-to-stock and make-to-order for a product line.

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

Manages the relationship with a represented workforce — administering a collective agreement, handling grievances, understanding what supervisors may and may not say, and preparing for bargaining. Use this for a grievance or arbitration question, a work rule change in a represented unit, supervisor guidance during organizing, contract interpretation and past practice, or preparation for negotiations.

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

Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.

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

Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.

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

Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.

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

Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.

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

Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this when creating a new skill, editing an existing one, diagnosing a skill that fires too often or never fires, or reviewing a set of skills for overlap. Also use before adding to a skill library, to check the capability is not already covered.

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

Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it.

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

Judges whether material for children under six is developmentally plausible — what is typical at each age, why pre-K is not a thinner kindergarten, and which frameworks apply where Common Core does not. Use this to design or review pre-K material, decide whether a task is reasonable for an age, choose the right framework for a pre-K alignment claim, or push back on material that pushes school-age expectations downward.

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

Keeps production assets available — ranking equipment by consequence of failure, setting preventive and predictive intervals, sizing spares, and moving a plant off reactive maintenance. Use this to build or fix a maintenance program, decide what to put on a PM schedule, diagnose repeat failures on one asset, justify spares inventory, or work out why a plant that maintains everything still has unplanned downtime.

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

Aligns learning material to the standard it claims — choosing the right framework for the grade and subject, citing standards by code rather than reproducing their text, and telling a real alignment from a decorative one. Use this to align a worksheet, lesson or workbook to Common Core, NGSS or a state framework, to check an alignment claim before publishing, or to decide what may lawfully be printed on the cover.

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

Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a third-party integration, or decide whether a design is safe to build.

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

Runs environment, health and safety on an operating site — hazard controls in order of effectiveness, incident recording and reporting obligations, and safety measurement that does not reward silence. Use this to build or audit a safety program, decide what controls a hazard actually needs, work out whether an injury is recordable or reportable, investigate an incident, or fix safety metrics that have stopped producing reports.

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

Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.

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