Stats
Actions
Tags
From stv
Distills real-world experiences into minimal methodologies, skills, and processes via bottom-up inductive design, stripping unnecessary elements.
How this skill is triggered — by the user, by Claude, or both
Slash command
/stv:thinkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A methodology design process that starts from experience and extracts minimal structure.
A methodology design process that starts from experience and extracts minimal structure. Core principle: Strip away the unnecessary from what worked. Do not fill in from theory.
First, secure experiences where the user actually succeeded (even 2-3 lines). The raw material is "I did this and it worked", not "theoretically it should be this way." If there are multiple experiences, lay them side by side and extract the common structure.
Extract common principles across experiences. Is only the direction different? Only the scale? Only the domain? — Find the invariant, not the differences.
The most important thing in the first structuring pass is not overdoing it. If the experience succeeded in 2-3 lines, creating a 200-line process document is over-engineering. Distinguish between what a sufficiently smart executor (human or AI) needs as just a direction hint versus what requires enforced procedure.
Simulate each sentence of the draft as "If I give this to an executor, how will they actually behave?"
If an ambiguous instruction causes wrong behavior, add a constraint. If a constraint is excessive, remove it.
Fill in with "when we actually tried it, omitting this caused failure." Add inductively ("this failed without it in practice"), not deductively ("logically this should also be needed").
A good name makes what the methodology actually does sharp and clear in one word. Metaphors (Blackbox, Dead Reckoning) have stronger identity than functional descriptions (A* Debug). If the name doesn't match the content, the name isn't wrong — the content definition is still fuzzy.
After structuring, verify the following:
If any of these apply, cut it down. Minimal structure is optimal.
npx claudepluginhub 2lab-ai/oh-my-claude --plugin stvGuides designing tightly focused, composable skills as mental models, principles, techniques, and processes at various abstraction levels for dynamic integration like a knowledge graph.
Surfaces expert frameworks and methodologies from domain masters for instruction design, code review, debugging, testing, knowledge management, and decision making. Use when creating or evaluating skills, hooks, or agents.
Guides developers in formalizing repeated manual processes into reusable Skills (SKILL.md files) with appropriate complexity handling, including decision trees for simple/complex paths.