using-skilletlisted

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill and do the task. </SUBAGENT-STOP> <EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you MUST invoke the skill. If a skill applies, using it is not optional. You cannot rationalize your way out of it. </EXTREMELY-IMPORTANT> # using-skillet A kitchen runs on mise en place: everything in its place before service, every cook reaching for the same prepped components instead of improvising. skillet is that prep for an AI coding session. The skills are the prepped stations; this skill is the line check that runs before you touch anything, deciding which station the current task belongs to and sending you there before you start cooking. ## The rule **Invoke the relevant or requested skill BEFORE any response or action,** including before clarifying questions and before "just looking." Even a 1% chance a skill applies means you invoke it to check. If it turns out wrong for the situation, you drop it; checking costs nothing, skipping costs a botched dish. ``` user message or task -> about to design/build something new? -> mise (then recipe) BEFORE anything else -> might any other skill apply? (yes, even 1%) -> invoke it -> announce: "Using skillet's <skill> to <purpose>" -> follow it exactly; if it has a checklist, make a todo per item -> definitely nothing applies -> respond ``` ## Instruction priority skillet sk