Firebender

https://docs.firebender.com
Admin
Firebender is a powerful AI coding agent deeply integrated into Android Studio and JetBrains IDEs,...
Tokens:41,821
Snippets:593
Trust Score:7.7
Update:3 months ago
Show doc for...
Tokens:
Raw
### Windows setup script example

Source: https://docs.firebender.com/multi-agent/worktrees

A PowerShell script for setting up dependencies and migrations on Windows systems.

```powershell
$ErrorActionPreference = 'Stop'
# Install dependencies
npm ci
# Copy environment file
Copy-Item "$env:ROOT_WORKTREE_PATH\.env" .env
# Run database migrations
npm run db:migrate
Write-Host "Worktree setup complete!"
```

--------------------------------

### Debug worktree setup

Source: https://docs.firebender.com/multi-agent/worktrees

Example of redirecting command output to a log file for troubleshooting.

```json
{
  "worktrees": {
    "setup-worktree": [
      "npm ci 2>&1 | tee /tmp/worktree-setup.log",
      "cp $ROOT_WORKTREE_PATH/.env .env 2>&1 | tee -a /tmp/worktree-setup.log"
    ]
  }
}
```

--------------------------------

### Unix setup script example

Source: https://docs.firebender.com/multi-agent/worktrees

A bash script for setting up dependencies and migrations on Unix systems.

```bash
#!/bin/bash
set -e
# Install dependencies
npm ci
# Copy environment file
cp "$ROOT_WORKTREE_PATH/.env" .env
# Run database migrations
npm run db:migrate
echo "Worktree setup complete!"
```

--------------------------------

### Configure Python project worktree

Source: https://docs.firebender.com/multi-agent/worktrees

Example of setting up a virtual environment and installing dependencies via a command array.

```json
{
  "worktrees": {
    "setup-worktree": [
      "python -m venv venv",
      "source venv/bin/activate && pip install -r requirements.txt",
      "cp $ROOT_WORKTREE_PATH/.env .env"
    ]
  }
}
```

--------------------------------

### Configure database migrations in worktree

Source: https://docs.firebender.com/multi-agent/worktrees

Example of including a database migration command in the setup sequence.

```json
{
  "worktrees": {
    "setup-worktree": [
      "npm ci",
      "cp $ROOT_WORKTREE_PATH/.env .env",
      "npm run db:migrate"
    ]
  }
}
```

--------------------------------

### Configure build and link dependencies

Source: https://docs.firebender.com/multi-agent/worktrees

Example of using pnpm to install and build dependencies within the worktree.

```json
{
  "worktrees": {
    "setup-worktree": [
      "pnpm install",
      "pnpm run build",
      "cp $ROOT_WORKTREE_PATH/.env.local .env.local"
    ]
  }
}
```

--------------------------------

### Provide concrete usage examples

Source: https://docs.firebender.com/multi-agent/skills

Include clear, actionable examples within the skill documentation to demonstrate expected usage.

```markdown
## Example usage

```bash
# Search for issues
gh search issues "bug" --repo=owner/repo

# Clone for analysis
cd /tmp && git clone https://github.com/owner/repo.git
```
```

--------------------------------

### Quick Question Command Example

Source: https://docs.firebender.com/api-reference/commands

A read-only command configuration for explaining selected code snippets.

```markdown
---
name: explain
description: Quick explanation of selected code
model: quick
mode: read
---

Explain the selected code concisely:
- What it does
- Why it's implemented this way
- Any potential issues or improvements
```

--------------------------------

### Reference external script files

Source: https://docs.firebender.com/multi-agent/worktrees

Example of referencing shell or PowerShell scripts for complex setup logic.

```json
{
  "worktrees": {
    "setup-worktree-unix": "setup-worktree-unix.sh",
    "setup-worktree-windows": "setup-worktree-windows.ps1",
    "setup-worktree": [
      "echo 'Using generic fallback. For better support, define OS-specific scripts.'"
    ]
  }
}
```

--------------------------------

### Concrete Kotlin Example

Source: https://docs.firebender.com/api-reference/skills

Provide real-world code snippets to demonstrate skill functionality.

```kotlin
// Create Room database
@Database(entities = [User::class], version = 1)
abstract class AppDatabase : RoomDatabase() {
    abstract fun userDao(): UserDao
}
```

--------------------------------

### Configure OS-specific worktree setups

Source: https://docs.firebender.com/api-reference/syntax

Provides distinct command arrays for Unix and Windows environments to handle platform-specific setup requirements.

```json
{
  "worktrees": {
    "setup-worktree-unix": [
      "npm ci",
      "cp $ROOT_WORKTREE_PATH/.env .env",
      "chmod +x scripts/*.sh"
    ],
    "setup-worktree-windows": [
      "npm ci",
      "copy %ROOT_WORKTREE_PATH%\.env .env"
    ]
  }
}
```

--------------------------------

### Configure Full Hooks File

Source: https://docs.firebender.com/multi-agent/hooks

Example of a complete hooks configuration file defining various lifecycle and execution hooks.

```json
{
  "version": 1,
  "hooks": {
    "sessionStart": [{ "command": "./hooks/session-start.sh" }],
    "sessionEnd": [{ "command": "./hooks/session-end.sh" }],
    "subagentStart": [{ "command": "./hooks/subagent-start.sh" }],
    "subagentStop": [{ "command": "./hooks/subagent-stop.sh" }],
    "preToolUse": [
      {
        "command": "./hooks/validate-tool.sh",
        "matcher": "Shell|Read|Write"
      }
    ],
    "postToolUse": [{ "command": "./hooks/audit-tool.sh" }],
    "beforeShellExecution": [{ "command": "./scripts/approve-network.sh" }],
    "afterShellExecution": [{ "command": "./hooks/audit.sh" }],
    "beforeMCPExecution": [{ "command": "./hooks/audit.sh" }],
    "afterMCPExecution": [{ "command": "./hooks/audit.sh" }],
    "beforeReadFile": [{ "command": "./hooks/redact-secrets.sh" }],
    "afterFileEdit": [{ "command": "./format.sh" }],
    "preCompact": [{ "command": "./hooks/audit.sh" }],
    "stop": [{ "command": "./hooks/audit.sh" }]
  }
}
```

--------------------------------

### Install Skill Requirements

Source: https://docs.firebender.com/multi-agent/skills

Command to install necessary Python dependencies for the PDF processing skill.

```bash
pip install pypdf pdfplumber
```

--------------------------------

### Configure worktrees with command arrays

Source: https://docs.firebender.com/api-reference/syntax

Uses an array of shell commands to perform setup tasks sequentially within the worktree.

```json
{
  "worktrees": {
    "setup-worktree": [
      "npm ci",
      "cp $ROOT_WORKTREE_PATH/.env .env"
    ]
  }
}
```

--------------------------------

### Define AGENTS.md instructions

Source: https://docs.firebender.com/api-reference/agents-md

Example of a plain markdown file structure for defining project instructions, architecture, and testing guidelines.

```markdown
# Project Instructions

## Code Style
- Use Kotlin for all new files
- Follow Material Design 3 guidelines
- Prefer Jetpack Compose for UI components

## Architecture
- Use MVVM pattern with ViewModels
- Keep business logic in use cases
- Use Room for local data persistence
- Use Retrofit for network calls

## Testing
- Write unit tests for ViewModels and use cases
- Use MockK for mocking
- Prefer property-based testing where applicable
```

--------------------------------

### Code Review Command Example

Source: https://docs.firebender.com/api-reference/commands

A read-only command configuration for reviewing git diffs.

```markdown
---
name: review diff
description: Review staged changes before commit
mode: read
---

Review the current git diff for:

1. **Bugs**: Logic errors, null pointer issues, race conditions
2. **Security**: Input validation, SQL injection, XSS vulnerabilities
3. **Performance**: N+1 queries, unnecessary allocations, blocking calls
4. **Style**: Naming conventions, code organization, documentation

Provide actionable feedback with specific line references.
```

--------------------------------

### Configure worktrees with script files

Source: https://docs.firebender.com/api-reference/syntax

References external script files relative to firebender.json for environment setup.

```json
{
  "worktrees": {
    "setup-worktree-unix": "setup-worktree-unix.sh",
    "setup-worktree-windows": "setup-worktree-windows.ps1"
  }
}
```

--------------------------------

### Define Skill File Structure

Source: https://docs.firebender.com/api-reference/skills

Example directory structure for a skill, showing how to organize supporting documentation and assets.

```text
pdf-processing/
├── SKILL.md          # Overview and quick start
├── FORMS.md          # Form field mappings
├── REFERENCE.md      # Detailed API docs
├── examples.md       # Usage examples
└── icon.svg          # Custom icon
```

--------------------------------

### Git Worktree List Output

Source: https://docs.firebender.com/multi-agent/worktrees

Example output showing the directory paths and associated branches for active worktrees.

```text
/path/to/project                             15ae12e [main]
/Users/you/.firebender/worktrees/proj/a1b2c  15ae12e [feat-1-a1b2c]
/Users/you/.firebender/worktrees/proj/d3e4f  15ae12e [feat-2-d3e4f]
```

--------------------------------

### Skill Description Examples

Source: https://docs.firebender.com/api-reference/skills

Compare poor and effective skill descriptions to improve user understanding and trigger accuracy.

```yaml
description: Helps with testing
```

```yaml
description: Writes comprehensive unit and UI tests for Android apps using JUnit 5, MockK, and Compose Testing. Use when creating tests, improving test coverage, or debugging test failures.
```

--------------------------------

### Agent Configuration for Delegation

Source: https://docs.firebender.com/api-reference/agents

Example of an agent configuration file using frontmatter to define its role, tools, and callable status for delegation.

```markdown
---
name: Test Writer
description: Generates comprehensive test cases for code. Use when user asks to write tests, create test suites, or add test coverage.
tools: read, edit
model: inherit
callable: true
---

You are a test writing specialist...
```

--------------------------------

### Changelog Generator Command Example

Source: https://docs.firebender.com/api-reference/commands

A write-mode command configuration for generating changelogs from commit history.

```markdown
---
name: write changelog
description: Generate changelog entry from recent commits
model: default
mode: write
---

Analyze recent commits and generate a changelog entry.

1. Run `git log --oneline -20` to see recent commits
2. Group changes by type (features, fixes, improvements)
3. Write user-friendly descriptions
4. Update CHANGELOG.md with the new entry
```

--------------------------------

### Personal skills directory structure

Source: https://docs.firebender.com/api-reference/skills

Example layout for personal skill files stored in the user's home directory.

```bash
~/.firebender/skills/
├── my-preferences/
│   └── SKILL.md
└── personal-scripts/
    └── SKILL.md
```

--------------------------------

### Configure .gitignore for AGENTS.md

Source: https://docs.firebender.com/api-reference/agents-md

Example configuration to exclude project-specific personal instructions while maintaining team-shared instructions.

```gitignore
# Project-specific personal AI instructions
AGENTS.md

# But allow team instructions
!.firebender/AGENTS.md
```

--------------------------------

### sessionStart Hook Input

Source: https://docs.firebender.com/multi-agent/hooks

Example input payload for the sessionStart hook, triggered when a chat session becomes active.

```json
// Input
{
  "conversation_id": "abc123",
  "session_id": "abc123",
  "model": "gpt-5.4-mini",
  "hook_event_name": "sessionStart",
  "workspace_roots": ["/project"],
  "user_email": "user@example.com",
  "firebender_version": "0.15.20",
  "is_background_agent": false,
  "composer_mode": "write"
}
```

--------------------------------

### Define Kotlin Style Rules with Frontmatter

Source: https://docs.firebender.com/api-reference/rules

Example of a rule file using YAML frontmatter to specify a description, file globs, and application behavior.

```markdown
---
description: Kotlin coding standards for this project
globs: "*.kt, *.kts"
alwaysApply: false
---

# Kotlin Style Guidelines

- Use Kotlin coroutines for async operations, never `runBlocking`
- Prefer data classes for simple data holders
- Use `@SerializedName` for Retrofit/Gson classes (code gets obfuscated)
- Follow Material Design 3 guidelines for UI components
```

--------------------------------

### Create a Skill via Firebender

Source: https://docs.firebender.com/multi-agent/skills

Use the built-in command to initiate the guided skill creation process.

```text
/help me create a skill
```

--------------------------------

### Ask Mode for Code Explanation

Source: https://docs.firebender.com/integrations/deep-links

Launch in Ask mode to explain code.

```text
jetbrains://idea/firebender/chat?prompt=Explain+code&mode=ask
```

--------------------------------

### Create Skill Directories

Source: https://docs.firebender.com/multi-agent/skills

Set up the required directory structure for user-specific or team-shared skills.

```bash
mkdir -p ~/.firebender/skills/my-skill
```

```bash
mkdir -p .firebender/skills/my-skill
```

--------------------------------

### sessionEnd Hook Input

Source: https://docs.firebender.com/multi-agent/hooks

Example input payload for the sessionEnd hook, triggered when a chat session concludes.

```json
// Input
{
  "conversation_id": "abc123",
  "session_id": "abc123",
  "model": "gpt-5.4-mini",
  "hook_event_name": "sessionEnd",
  "workspace_roots": ["/project"],
  "user_email": "user@example.com",
  "firebender_version": "0.15.20",
  "reason": "user_close",
  "duration_ms": 5432,
  "is_background_agent": false,
  "final_status": "completed"
}
```

--------------------------------

### Basic Query Deep Link

Source: https://docs.firebender.com/integrations/deep-links

Launch the IDE with a simple prompt.

```text
jetbrains://idea/firebender/chat?prompt=Hello
```

--------------------------------

### Source Terminal Hooks

Source: https://docs.firebender.com/multi-agent/terminal

Automatically load specific scripts or aliases when an agent terminal session starts.

```bash
if [[ -n "$FIREBENDER_TERMINAL" ]]; then
source ~/.firebender-hooks.sh
fi
```

--------------------------------

### Define Project Context Rules

Source: https://docs.firebender.com/multi-agent/global-rules

Create a project-context.mdc file to set global coding guidelines for the AI. The alwaysApply flag ensures these rules are active across the project.

```markdown
---
alwaysApply: true
---

# Project Context

This is a food delivery app (similar to DoorDash).

Guidelines:
- Never use runBlocking
- Don't hardcode dpi
- Use `@SerializedName` for data/retrofit classes because code gets obfuscated
- Follow Material Design 3 guidelines and components
- Use Kotlin coroutines and Flow for asynchronous operations
```

--------------------------------

### Query with Specific Model

Source: https://docs.firebender.com/integrations/deep-links

Launch the IDE with a specific model ID.

```text
jetbrains://studio/firebender/chat?prompt=Debug+issue&model=claude-sonnet-4-20250514
```

--------------------------------

### Create UI component rules

Source: https://docs.firebender.com/api-reference/rules

Defines best practices for Jetpack Compose files.

```markdown
---
description: Jetpack Compose best practices
globs: "*.kt"
---

# Compose Guidelines

When writing Compose UI:
- Use Material 3 components and theming
- Implement proper state hoisting
- Use `remember` and `derivedStateOf` appropriately
- Preview components with `@Preview` annotation
```

--------------------------------

### Auto-trigger invocation example

Source: https://docs.firebender.com/api-reference/skills

Shows how Firebender automatically triggers a skill based on user natural language input.

```text
User: "Help me write a commit message for these changes"
→ Firebender auto-invokes commit-helper skill
```

--------------------------------

### Create project-wide rules

Source: https://docs.firebender.com/api-reference/rules

Defines global guidelines for the entire project.

```markdown
---
alwaysApply: true
---

# Project Context

This is the Firebender Android plugin for JetBrains IDEs.

Key guidelines:
- Use `println()` for logging instead of Android's `Log`
- Prefer JBUI and IntelliJ SDK components (`JBPanel` over `JPanel`)
- Use `@SerializedName` for data classes (plugin is obfuscated)
- Never use `runBlocking {}`, use coroutine scopes from services
```

--------------------------------

### Commit Message Generator Skill Definition

Source: https://docs.firebender.com/api-reference/skills

A SKILL.md example for a commit message generator, detailing the conventional commit format and rules.

```markdown
---
name: commit-helper
description: Generates clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or before committing code.
version: 1.0.0
autoTrigger: true
---

# Commit Message Helper

## Process

1. Run git diff --staged to see changes
2. Analyze the changes:
   - What components are affected?
   - What functionality changed?
   - Why was this change needed?
3. Generate commit message in conventional format

## Format

type(scope): subject

body

footer

## Types
- feat: New feature
- fix: Bug fix
- refactor: Code restructuring
- perf: Performance improvement
- test: Adding tests
- docs: Documentation changes
- chore: Build/tooling changes

## Rules
- Subject line: 50 chars max, present tense
- Body: Explain what and why, not how
- Reference issues in footer: Fixes #123

## Example

feat(auth): add biometric authentication

Implement fingerprint and face recognition for login.
Users can now authenticate using device biometrics as
an alternative to password entry.

- Add BiometricPrompt integration
- Update AuthViewModel with biometric flow
- Add fallback to password on biometric failure

Fixes #456
```

--------------------------------

### Define Agent with MCP Tools

Source: https://docs.firebender.com/api-reference/agents

Demonstrates how to include specific MCP tools in an agent's configuration.

```markdown
---
name: Database Agent
tools: read, mcp_supabase_list_tables, mcp_supabase_execute_sql
---
```

--------------------------------

### Structure skill directories with executable scripts

Source: https://docs.firebender.com/multi-agent/skills

Organize logic into standalone executable files rather than embedding scripts directly in markdown blocks.

```markdown
```bash
#!/bin/bash
# Complex script here...
```
```

```text
my-skill/
├── SKILL.md
├── process.sh       # Executable script
└── analyze.py       # Executable script
```

```markdown
Run the analysis script: `./process.sh input.txt`
```

--------------------------------

### Database Query Helper Skill Definition

Source: https://docs.firebender.com/api-reference/skills

A SKILL.md example for a database utility, demonstrating SQL query documentation and Android Room integration.

```markdown
---
name: database-query
description: Generates SQL queries and analyzes database schemas. Use when working with databases, writing queries, or optimizing database performance.
version: 1.0.0
autoTrigger: true
---

# Database Query Helper

## Schema

Current database schema is documented in [schema.md](schema.md).

## Query Guidelines

### Performance
- Always use indexes for WHERE clauses
- Avoid SELECT * in production
- Use EXPLAIN ANALYZE for complex queries

### Android Room

Example query:

@Query("SELECT * FROM users WHERE age > :minAge ORDER BY name ASC")
suspend fun getUsersOlderThan(minAge: Int): List<User>

### Common Patterns

See [examples.md](examples.md) for:
- Pagination queries
- Join optimization
- Transaction patterns
```

--------------------------------

### Configure Command Description

Source: https://docs.firebender.com/api-reference/commands

Provides a brief summary of the command's purpose.

```yaml
description: Create a GitHub PR with AI-generated title and body
```

--------------------------------

### Define Project Context Rules without Frontmatter

Source: https://docs.firebender.com/api-reference/rules

Example of a rule file without frontmatter, which causes the rule to apply to all files by default.

```markdown
This is a food delivery app similar to DoorDash.

Key technologies:
- Kotlin with Jetpack Compose for Android
- Room for local database
- Retrofit for networking
- Kotlin coroutines for async operations
```

--------------------------------

### Identify SSL Certificate Trust Errors

Source: https://docs.firebender.com/account/business/security

Example of the error message encountered when enterprise environments fail to validate SSL certificates for backend communication.

```text
PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
```

--------------------------------

### Configure AWS SSO profile

Source: https://docs.firebender.com/configurations/firebender-on-amazon-bedrock

Initializes the AWS SSO configuration process to create a profile in ~/.aws/config.

```bash
aws configure sso
```

--------------------------------

### Configure CLI-based MCP Servers

Source: https://docs.firebender.com/context/mcp/overview

Use these configurations to define local command-line servers using Node.js or Python runtimes.

```json
{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "mcp-server"],
      "env": {
        "API_KEY": "value"
      }
    }
  }
}
```

```json
{
  "mcpServers": {
    "server-name": {
      "command": "python",
      "args": ["mcp-server.py"],
      "env": {
        "API_KEY": "value"
      }
    }
  }
}
```

--------------------------------

### Android Test Writer Skill Definition

Source: https://docs.firebender.com/api-reference/skills

A complete SKILL.md example for an Android test generation tool, including unit and UI test code samples.

```markdown
---
name: android-test-writer
description: Writes comprehensive unit and UI tests for Android apps. Use when creating tests, improving test coverage, or debugging test failures.
version: 1.0.0
projectTypes: [android, kotlin]
autoTrigger: true
---

# Android Test Writer

## Unit Tests

Use JUnit 5 with MockK for mocking. Example:

@Test
fun repository returns cached data when available() {
    val cachedUser = User(id = 1, name = "Test")
    every { cache.get("user_1") } returns cachedUser
    
    val result = repository.getUser(1)
    
    assertEquals(cachedUser, result)
    verify(exactly = 0) { api.fetchUser(any()) }
}

## UI Tests

Use Compose Testing for UI verification. Example:

@Test
fun loginScreen_showsErrorOnInvalidCredentials() {
    composeTestRule.setContent {
        LoginScreen(viewModel)
    }
    
    composeTestRule.onNodeWithText("Login").performClick()
    composeTestRule.onNodeWithText("Invalid credentials").assertIsDisplayed()
}

## Best Practices

- Test ViewModels with fake repositories
- Use runTest for coroutine testing
- Mock Android framework dependencies
- Aim for 80%+ coverage on business logic
```

--------------------------------

### Define Agent Behavior with Markdown

Source: https://docs.firebender.com/api-reference/agents

Create an agent definition file using YAML frontmatter for metadata and Markdown for the system prompt.

```markdown
---
name: Code Reviewer
description: Reviews code for best practices and potential issues
color: "#FF5722"
icon: /absolute/path/to/icons/reviewer.svg
tools: read
model: medium
callable: false
---

You are an expert code reviewer. Your role is to:
- Analyze code for bugs, security issues, and performance problems
- Suggest improvements following best practices
- Check for code style consistency
- Identify potential edge cases

Be thorough but constructive in your feedback.
```

--------------------------------

### Migrate command configuration

Source: https://docs.firebender.com/api-reference/commands

Transition from the deprecated firebender.json format to the new .mdc file structure.

```json
{
  "commands": [
    {
      "name": "create pr",
      "path": "commands/pr.md",
      "mode": "write"
    }
  ]
}
```

```markdown
---
name: create pr
mode: write
---

(contents of commands/pr.md)
```

--------------------------------

### Configure RevenueCat MCP Server

Source: https://docs.firebender.com/context/mcp/revenuecat

Manual configuration for the RevenueCat MCP server in the firebender.json file.

```json
{
  "mcpServers": {
    "revenuecat": {
      "url": "https://mcp.revenuecat.ai/mcp"
    }
  }
}
```

--------------------------------

### Reference Supporting Files

Source: https://docs.firebender.com/api-reference/skills

Markdown syntax for linking to auxiliary documentation files within a SKILL.md file.

```markdown
For form filling, see [FORMS.md](FORMS.md).
For detailed API reference, see [REFERENCE.md](REFERENCE.md).
```

--------------------------------

### Fresh Chat Session

Source: https://docs.firebender.com/integrations/deep-links

Launch with a new chat session.

```text
jetbrains://studio/firebender/chat?prompt=Fresh+start&newchat
```

--------------------------------

### Configure MCP Servers

Source: https://docs.firebender.com/api-reference/syntax

Define command-based or URL-based MCP servers with optional environment variables and loading behavior.

```json
{
  "mcpServers": {
    "brave-search": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-brave-search"],
      "env": {"BRAVE_API_KEY": "YOUR_API_KEY"}
    },
    "weather": {
      "command": "npx",
      "args": ["-y", "@h1deya/mcp-server-weather"]
    },
    "api-server": {
      "url": "http://localhost:3000/mcp",
      "headers": {"Authorization": "Bearer YOUR_TOKEN"}
    },
    "orchestrator": {
      "command": "npx",
      "args": ["-y", "@mycompany/orchestrator-mcp"],
      "deferLoading": false
    }
  }
}
```

--------------------------------

### Implement progressive disclosure in documentation

Source: https://docs.firebender.com/multi-agent/skills

Keep core instructions in the main file and link to detailed documentation for advanced or API-specific information.

```markdown
## Quick reference

[Basic instructions here]

For advanced usage, see [advanced.md](advanced.md).
For API details, see [api-reference.md](api-reference.md).
```

--------------------------------

### Executable Script Documentation

Source: https://docs.firebender.com/api-reference/skills

Reference executable scripts in documentation rather than embedding long bash scripts.

```markdown
Run analysis: `./process.sh input.txt`
```

--------------------------------

### Configure Notion MCP Server

Source: https://docs.firebender.com/context/mcp/notion

Manual configuration for the Notion MCP server within the mcp.json file.

```json
{
  "mcpServers": {
    "notion": {
      "url": "https://mcp.notion.com/mcp"
    }
  }
}
```

--------------------------------

### Configure Figma MCP Server

Source: https://docs.firebender.com/context/mcp/figma

Manual configuration for the Figma MCP server within the firebender.json file.

```json
{
  "mcpServers": {
    "figma": {
      "url": "https://mcp.figma.com/mcp"
    }
  }
}
```

--------------------------------

### Define skill version

Source: https://docs.firebender.com/api-reference/skills

Sets the version string for tracking purposes.

```yaml
version: 1.0.0
```

--------------------------------

### Create Symbolic Link for Rules

Source: https://docs.firebender.com/api-reference/rules

Use this command to link a shared rule file into the local project directory.

```bash
ln -s ~/shared-rules/team-standards.mdc .firebender/rules/team-standards.mdc
```

--------------------------------

### Write Mode with GPT-5

Source: https://docs.firebender.com/integrations/deep-links

Launch in Write mode using a specific model.

```text
jetbrains://studio/firebender/chat?prompt=Build+feature&mode=write&model=gpt-5
```

--------------------------------

### Migrated .mdc Rule Files

Source: https://docs.firebender.com/api-reference/rules

New format for defining rules using Markdown files with YAML frontmatter.

```markdown
---
alwaysApply: true
---

- Follow Material Design 3 guidelines
- Use Kotlin coroutines for async operations
```

```markdown
---
globs: "*Test.kt"
---

- Use Kotest BDD style

(contents of test-rules.txt)
```

--------------------------------

### Define agent configuration paths

Source: https://docs.firebender.com/api-reference/syntax

Specifies an array of file paths pointing to agent configuration files.

```json
{
  "agents": [
    ".firebender/agents/code-reviewer.md",
    "~/firebender-agents/test-writer.md",
    "/absolute/path/to/agent.md"
  ]
}
```

--------------------------------

### Define project-specific documentation metadata

Source: https://docs.firebender.com/input/docs

Store project-level documentation in .firebender/docs/ within the repository to share references across the team.

```yaml
# .firebender/docs/design-system.md
---
name: Design System
url: https://design.mycompany.com
category: Design
description: Component library and design tokens
---
```

--------------------------------

### mcpEnvFile Configuration

Source: https://docs.firebender.com/api-reference/syntax

Specifies the path to an environment file for MCP servers.

```APIDOC
## mcpEnvFile

### Description
Optional path to a file containing environment variables for MCP servers. Can be either a full path or a relative path from the project root.

### Example
{
  "mcpEnvFile": ".env.mcp"
}
```

--------------------------------

### Enable alwaysApply

Source: https://docs.firebender.com/api-reference/rules

Forces the rule to apply to all files, overriding glob patterns.

```yaml
alwaysApply: true
```
Tokens:
Raw