agentleFS
soumatheusgomessoumatheusgomes/agentville/.claude/skills/behavioral-modes/SKILL.md

behavioral-modes

Skill9 starsChanged 3 months agoApache-2.0View on GitHub

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type. When adapting AI behavior for specific task types: brainstorm, implement, debug, review, teach, ship, or orchestrate modes.

13 other projects use a version of this, 13 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use nextjs-react-expert, rust-pro and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SKB3002Skill

    nextjs-react-expert

    React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

    Also in 3 projects that use this

  • xfstudioSkill

    rust-pro

    Master Rust 1.75+ with modern async patterns, advanced type system

    Also in 5 projects that use this

  • jornalistainclusivoSkill

    design-spec

    How to author a DESIGN.md file — the machine-readable design-token + human-rationale format that must exist before any UI is built. YAML front-matter token schema (colors, typography, spacing, rounded, components), type system, token references, and canonical section order.

    Also in 3 projects that use this

  • zzfancitizenSkill

    verify-changes

    Verify code changes do not break the project by running tests, linter checks, and import validation. Use after making any code changes, editing Python files, modifying imports, updating dependencies, or refactoring.

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 8 are common, 0 are distinctive, and 0 are very specific to this project.

  • 8

    Common

    Most of the 13 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Ask clarifying questions before assumptions

    line 22
  2. Common:

    No code yet - focus on ideas and options

    line 25
  3. Common:

    Use visual diagrams (mermaid) to explain concepts

    line 26
  4. Common:

    Use established patterns and best practices

    line 52
  5. Common:

    Write complete, production-ready code

    line 53
  6. Common:

    Ask for error messages and reproduction steps

    line 87
  7. Common:

    Use analogies and examples

    line 138
  8. Common:

    Check for missing error handling

    line 168

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Vendored from ag-kit (github.com/vudovn/ag-kit) @ 20a13da6d4414c7c6ae33db050a9c606eaef9f40 :: .agents/skills/behavioral-modes/SKILL.md. MIT (c) vudovn. -->

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:

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

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

Modes are not exclusive — most real tasks chain several in sequence:

FlowMode Chain
New featureBRAINSTORM → PLAN-EXECUTE-CRITIC → IMPLEMENT → REVIEW → SHIP
Bug fixEXPLORE → DEBUG → IMPLEMENT → REVIEW
Unfamiliar codebaseEXPLORE → TEACH → BRAINSTORM
Risky refactorEXPLORE → PLAN-EXECUTE-CRITIC → IMPLEMENT → REVIEW

Switch modes when the work changes shape (e.g. drop from IMPLEMENT to DEBUG the moment a test fails), and carry context forward with MENTAL MODEL SYNC across long sessions.

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.