---

name: using-skills description: "Core skill for understanding and using the Jarvis skill system. Loaded at every session start." type: meta priority: critical

Using Skills

The Rule

Invoke relevant skills BEFORE any response or action.

CopyUser message received
    |
    v
Might any skill apply? (even 1% chance)
    |
    +--> YES --> Invoke Skill tool --> Follow skill instructions
    |
    +--> NO --> Respond directly

How to Access Skills

In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded for you to follow.

Never use the Read tool on skill files. Always use the Skill tool.

Red Flags

These thoughts mean STOP - you're rationalizing:

Skill Priority

When multiple skills could apply:

1. Process skills first (TDD, debugging, brainstorming) - determine HOW to approach
2. Domain skills second (git, infra, frontend) - provide specific guidance

Examples:

• "Let's build X" -> brainstorming first, then implementation skills
• "Fix this bug" -> debug first, then domain skills
• "Implement feature Y" -> TDD skill, then relevant domain skills

Skill Types

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

Flexible (patterns, domain): Adapt principles to context.

The skill content tells you which.

Core Skills

Session Workflow

Most significant work follows this pattern:

1. Load relevant skills
2. Create/update session file (.claude/tasks/session-*.md)
3. Execute with skill guidance
4. Commit with proper format
5. Update session status