ryanditjia · Agent Skills
出典を確認した実質的な文書を持つ Skill が 14 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。
create-verification-skill
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
figure-it-out
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 via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
how
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.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
interrogate
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.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
principle-migrate-callers-then-delete-legacy-apis
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
principle-outcome-oriented-execution
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.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
principle-prove-it-works
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.'
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
principle-type-system-discipline
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.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
reflect
Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
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'.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
unslop
Cut AI tells from any writing. Must always apply.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月2日
