/using-superjawn

name: using-superjawn
description: Establishes how to find and use skills before any response or action. Use when starting any conversation.

<!-- Adapted from obra/superpowers using-superpowers skill (v5.0.7), MIT-licensed, copyright 2025 Jesse Vincent. Modifications copyright 2026 Joe Amditis. v0.6.0 ports as a renamed consumer skill: directory + frontmatter `name:` field move from `using-superpowers` to `using-superjawn` so the bootstrap skill matches the local plugin's identity. Two body references to the system name ("Superpowers skills") are rebranded to "superjawn skills" to match. The rename makes byte-parity with upstream impossible by definition; `skill_md_parity` is false in the manifest and `upstream_name` is set to `using-superpowers` so the validator's parity + supporting-file checks resolve against the right upstream directory. See CREDITS.md. -->

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill. </SUBAGENT-STOP>

<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke 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>

Instruction Priority

superjawn skills override default system prompt behavior, but **user instructions always take precedence**:

1. **User's explicit instructions** (`AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, and direct requests), highest priority 2. **superjawn skills**, override default system behavior where they conflict 3. **Default system prompt**, lowest priority

If the project instruction file (`AGENTS.md` for Codex, `CLAUDE.md` for Claude Code, or `GEMINI.md` for Gemini CLI) says "skip the research phase" and a skill says "always research first," follow the user's instructions. The user is in control.

How to Access Skills

**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you; follow it directly. Do not use the Read tool on skill files.

**In Codex:** Skills load natively from the skill catalog. Open the listed `SKILL.md` and follow it directly.

**In Copilot CLI:** Use the `skill` tool. Skills are auto-discovered from installed plugins.

**In Gemini CLI:** Skills activate through the `activate_skill` tool. Gemini loads skill metadata at session start and the full content on demand.

**In other environments:** Check the client's documentation for skill discovery and loading.

Platform Adaptation

Skills describe capabilities instead of vendor tool names. Use the client's file, shell, plan, and worker features that match the requested action. For concrete tool names, see `references/codex-tools.md` (Codex), `references/copilot-tools.md` (Copilot CLI), or `references/gemini-tools.md` (Gemini CLI). Gemini CLI users get the tool mapping loaded automatically through `GEMINI.md`.

Using Skills

The Rule

**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.

digraph skill_flow {
    "User message received" [shape=doublecircle];
    "About to EnterPlanMode?" [shape=doublecircle];
    "Already brainstormed?" [shape=diamond];
    "Invoke brainstorming skill" [shape=box];
    "Might any skill apply?" [shape=diamond];
    "Load relevant skill" [shape=box];
    "Announce: 'Using [skill] to [purpose]'" [shape=box];
    "Has checklist?" [shape=diamond];
    "Create one task-list item per checklist item" [shape=box];
    "Follow skill exactly" [shape=box];
    "Respond (including clarifications)" [shape=doublecircle];

    "About to EnterPlanMode?" -> "Already brainstormed?";
    "Already brainstormed?" -> "Invoke brainstorming skill" [label="no"];
    "Already brainstormed?" -> "Might any skill apply?" [label="yes"];
    "Invoke brainstorming skill" -> "Might any skill apply?";

    "User message received" -> "Might any skill apply?";
    "Might any skill apply?" -> "Load relevant skill" [label="yes, even 1%"];
    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
    "Load relevant skill" -> "Announce: 'Using [skill] to [purpose]'";
    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
    "Has checklist?" -> "Create one task-list item per checklist item" [label="yes"];
    "Has checklist?" -> "Follow skill exactly" [label="no"];
    "Create one task-list item per checklist item" -> "Follow skill exactly";
}

Red Flags

These thoughts mean STOP, you're rationalizing:

| Thought | Reality | |---------|---------| | "This is just a simple question" | Questions are tasks. Check for skills. | | "I need more context first" | Skill check comes BEFORE clarifying questions. | | "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. | | "I can check git/files quickly" | Files lack conversation context. Check for skills. | | "Let me gather information first" | Skills tell you HOW to gather information. | | "This doesn't need a formal skill" | If a skill exists, use it. | | "I remember this skill" | Skills evolve. Read current version. | | "This doesn't count as a task" | Action = task. Check for skills. | | "The skill is overkill" | Simple things become complex. Use it. | | "I'll just do this one thing first" | Check BEFORE doing anything. | | "This feels productive" | Undisciplined action wastes time. Skills prevent this. | | "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |

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, mcp-builder) - these gui