스킬 찾기

Apply when integrating a new requirement into an existing design.

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

Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

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

Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.

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

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions. Use for /figure-it-out or 'figure it out'.

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

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

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

Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

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

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

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

Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

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

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.

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

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

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

Catch the user up on what changed in this chat since their last message, in a few plain sentences and small visuals. Give each action item just enough context to make the call. Use for /ketchup.

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

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

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

Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

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

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

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

Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

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

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

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

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

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

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.

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

Configure which models pstack uses per role and at what reasoning budget. Detects your available models and writes an always-applied rule that overrides the skill defaults. Use for /setup-pstack, "configure pstack models", "pstack budget", or changing pstack's model choices.

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

Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.

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

Apply when tempted to ask 'should I do X?' on reversible work.

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

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

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

Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

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

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.

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