个人作者
Kuruto Denzeru
Senior Software Engineer | PH100 Under 30 | Tech Advocate | Student Ambassador of Microsoft
- Skills
- 43
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 33
Kuruto Denzeru 的 Skills 43
tersio
Show Tersio status, usage, help, update, upstream, or dashboard in Codex.
tersio-modes
Read or change Tersio's session-start modes and local usage stats in Codex. Use when the user asks for Caveman, Ponytail, pstack, Combo, token usage, session history, or Tersio status.
rtk
Set or show Tersio's stored RTK preference in Codex.
pstack
Set or show Tersio pstack in Codex. Use with `$pstack on`, `$pstack off`, or `$pstack status`.
ponytail
Set or show Tersio Ponytail in Codex. Use with a level such as `$ponytail full`.
headroom
Set or show Tersio's stored Headroom preference in Codex.
combo
Set or show Tersio Combo in Codex. Use with a level such as `$combo lite`.
caveman
Set or show Tersio Caveman in Codex. Use with a level such as `$caveman lite`.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
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.
teach
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'.
tdd
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.
swarm
Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
statechart
Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives the shortest path to each state that breaks a rule. Use for /statechart, or to show a bug as a path through states.
show-me-your-work
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
sharpen
Make a task deeper, not bigger, then rewrite the prompt. Use for /sharpen.