using-superpowerslisted

<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST read the skill. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT> # Getting Started with Skills ## MANDATORY FIRST RESPONSE PROTOCOL Before responding to ANY user message, you MUST complete this checklist: 1. ☐ List available skills in your mind 2. ☐ Ask yourself: "Does ANY skill match this request?" 3. ☐ If yes → Read and run the skill file 4. ☐ Announce which skill you're using 5. ☐ Follow the skill exactly **Responding WITHOUT completing this checklist = automatic failure.** ## Critical Rules 1. **Follow mandatory workflows.** Brainstorming before coding. Check for relevant skills before ANY task. 2. Execute skills as written ## Common Rationalizations That Mean You're About To Fail If you catch yourself thinking ANY of these thoughts, STOP. You are rationalizing. Check for and use the skill. - "This is just a simple question" → WRONG. Questions are tasks. Check for skills. - "I can check git/files quickly" → WRONG. Files don't have conversation context. Check for skills. - "Let me gather information first" → WRONG. Skills tell you HOW to gather information. Check for skills. - "This doesn't need a formal skill" → WRONG. If a skill exists for it, use it. - "I remember this skill" → WRONG. Skills evolv