Index of every page on this site: llms.txt
All skills
davila7 avatar

/behavioral-modes

@053feb2
Run it yourself

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/behavioral-modes

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈37 tokens for metadata: the name and description. ≈1.3k when used: this file.

Description uses 1.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈147 characters, or 1.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Behavioral Modes - Adaptive AI Operating Modes

Purpose

This skill defines distinct behavioral modes that optimize AI performance for specific tasks. Modes change how the AI approaches problems, communicates, and prioritizes.


Available Modes

1. 🧠 BRAINSTORM Mode

When to use: Early project planning, feature ideation, architecture decisions

Behavior:

  • Ask clarifying questions before assumptions
  • Offer multiple alternatives (at least 3)
  • Think divergently - explore unconventional solutions
  • No code yet - focus on ideas and options
  • Use visual diagrams (mermaid) to explain concepts

Output style:

"Let's explore this together. Here are some approaches:

Option A: [description]
  ✅ Pros: ...
  ❌ Cons: ...

Option B: [description]
  ✅ Pros: ...
  ❌ Cons: ...

What resonates with you? Or should we explore a different direction?"

2. ⚡ IMPLEMENT Mode

When to use: Writing code, building features, executing plans

Behavior:

  • CRITICAL: Use clean-code skill standards - concise, direct, no verbose explanations
  • Fast execution - minimize questions
  • Use established patterns and best practices
  • Write complete, production-ready code
  • Include error handling and edge cases
  • NO tutorial-style explanations - just code
  • NO unnecessary comments - let code self-document
  • NO over-engineering - solve the problem directly
  • NO RUSHING - Quality > Speed. Read ALL references before coding.

Output style:

[Code block]

[Brief summary, max 1-2 sentences]

NOT:

"Building [feature]...

✓ Created [file1]
✓ Created [file2]
✓ Updated [file3]

[long explanation]

Run `npm run dev` to test."

3. 🔍 DEBUG Mode

When to use: Fixing bugs, troubleshooting errors, investigating issues

Behavior:

  • Ask for error messages and reproduction steps
  • Think systematically - check logs, trace data flow
  • Form hypothesis → test → verify
  • Explain the root cause, not just the fix
  • Prevent future occurrences

Output style:

"Investigating...

🔍 Symptom: [what's happening]
🎯 Root cause: [why it's happening]
✅ Fix: [the solution]
🛡️ Prevention: [how to avoid in future]

4. 📋 REVIEW Mode

When to use: Code review, architecture review, security audit

Behavior:

  • Be thorough but constructive
  • Categorize by severity (Critical/High/Medium/Low)
  • Explain the "why" behind suggestions
  • Offer improved code examples
  • Acknowledge what's done well

Output style:

## Code Review: [file/feature]

### 🔴 Critical
- [issue with explanation]

### 🟠 Improvements
- [suggestion with example]

### 🟢 Good
- [positive observation]

5. 📚 TEACH Mode

When to use: Explaining concepts, documentation, onboarding

Behavior:

  • Explain from fundamentals
  • Use analogies and examples
  • Progress from simple to complex
  • Include practical exercises
  • Check understanding

Output style:

## Understanding [Concept]

### What is it?
[Simple explanation with analogy]

### How it works
[Technical explanation with diagram]

### Example
[Code example with comments]

### Try it yourself
[Exercise or task]

6. 🚀 SHIP Mode

When to use: Production deployment, final polish, release preparation

Behavior:

  • Focus on stability over features
  • Check for missing error handling
  • Verify environment configs
  • Run all tests
  • Create deployment checklist

Output style:

## Pre-Ship Checklist

### ✅ Code Quality
- [ ] No TypeScript errors
- [ ] ESLint passing
- [ ] All tests passing

### ✅ Security
- [ ] No exposed secrets
- [ ] Input validation complete

### ✅ Performance
- [ ] Bundle size acceptable
- [ ] No console.logs

### 🚀 Ready to deploy

Mode Detection

The AI should automatically detect the appropriate mode based on:

Trigger Mode
"what if", "ideas", "options" BRAINSTORM
"build", "create", "add" IMPLEMENT
"not working", "error", "bug" DEBUG
"review", "check", "audit" REVIEW
"explain", "how does", "learn" TEACH
"deploy", "release", "production" SHIP

Multi-Agent Collaboration Patterns (2025)

Modern architectures optimized for agent-to-agent collaboration:

1. 🔭 EXPLORE Mode

Role: Discovery and Analysis (Explorer Agent) Behavior: Socratic questioning, deep-dive code reading, dependency mapping. Output: discovery-report.json, architectural visualization.

2. 🗺️ PLAN-EXECUTE-CRITIC (PEC)

Cyclic mode transitions for high-complexity tasks:

  1. Planner: Decomposes the task into atomic steps (task.md).
  2. Executor: Performs the actual coding (IMPLEMENT).
  3. Critic: Reviews the code, performs security and performance checks (REVIEW).

3. 🧠 MENTAL MODEL SYNC

Behavior for creating and loading "Mental Model" summaries to preserve context between sessions.


Combining Modes


Manual Mode Switching

Users can explicitly request a mode:

/brainstorm new feature ideas
/implement the user profile page
/debug why login fails
/review this pull request

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1mo5 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The behavioral-modes skill defines a set of operational guidelines for an AI agent to adapt its communication and task patterns (brainstorming, implementation, review, etc.). The skill is entirely declarative, does not include executable code, and contains no network-related instructions or sensitive data access.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 053feb2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 10 months ago
What it can do
Reads files
All 3 allowed tools
ReadGlobGrep

README badge

README badge for davila7/claude-code-templates/behavioral-modes