<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>

Using Skills

The Rule

Check for skills BEFORE ANY RESPONSE. This includes clarifying questions. Use the Read tool to read relevant SKILL.md files from .cursor/skills/ based on task context.

How to Find Skills

All skills are in .cursor/skills/. Match your task to the appropriate skill directory and read its SKILL.md:

Task → Skill Mapping

Workflow

1. Identify task type from user message
2. Read relevant SKILL.md using the Read tool
3. Announce: "Using [skill name] for [purpose]"
4. If skill has checklist: Create TodoWrite todos for each item
5. Follow skill exactly

Red Flags

These thoughts mean STOP—you're rationalizing:

Skill Priority

When multiple skills could apply, use this order:

1. Process skills first (brainstorming, debugging) - these determine HOW to approach the task
2. Implementation skills second (frontend-design, database) - these guide execution

"Let's build X" → brainstorming first, then implementation skills. "Fix this bug" → when-stuck/debugging first, then domain-specific skills.

Skill Types

Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.

Flexible (patterns): Adapt principles to context.

The skill itself tells you which.

User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.