# using-framework > Use when starting any conversation - establishes mandatory workflows for finding and using skills, checking for relevant skills before any task, and following systematic approaches - Author: Conny Wallstrom - Repository: walcon/ai-framework - Version: 20251126195105 - Stars: 0 - Forks: 0 - Last Updated: 2026-02-08 - Source: https://github.com/walcon/ai-framework - Web: https://mule.run/skillshub/@@walcon/ai-framework~using-framework:20251126195105 --- --- name: using-framework description: Use when starting any conversation - establishes mandatory workflows for finding and using skills, checking for relevant skills before any task, and following systematic approaches --- # 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 follow the skill exactly 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. **If a skill exists for your task, you must use it.** ## 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. Check for skills first. - "Let me gather information first" → WRONG. Skills tell you HOW to gather information. - "This doesn't need a formal skill" → WRONG. If a skill exists for it, use it. - "This doesn't count as a task" → WRONG. If you're taking action, it's a task. - "The skill is overkill for this" → WRONG. Skills exist because simple things become complex. - "I'll just do this one thing first" → WRONG. Check for skills BEFORE doing anything. ## Skills with Checklists If a skill has a checklist, create todos for EACH item. Don't work through checklist mentally. ## Announcing Skill Usage Before using a skill, announce it: "I'm using [Skill Name] to [what you're doing]." ## Summary **Starting any task:** 1. If relevant skill exists → Use the skill 2. Announce you're using it 3. Follow what it says **Finding a relevant skill = mandatory to read and use it. Not optional.**