Michael Ramos

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.

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

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

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

Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

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

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 only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

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

Catch the user up on what changed in this chat since their last message, in plain words and small visuals. List every item waiting on them with what they need to decide it from the reply alone. Use for /ketchup.

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

Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.

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

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.

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

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

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

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.

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

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

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

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

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

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.

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

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

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

Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.

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

Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.

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

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

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

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

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

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 integrating a new requirement into an existing design.

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

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.

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

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.

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

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.

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

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.

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