​

Specialists

• Backend agent — runs the work (built-in engine, Claude Code, Codex, Gemini CLI, etc.)
• Rules — a Markdown system prompt defining behavior
• Skills — extra capabilities (decks, spreadsheets, reports, MCP tools, etc.)
• Display metadata — name, avatar (emoji or built-in icon), description

​

The 20+ built-in Specialists

​

What makes a specialist

• 🖥️ Local-first — runs on your machine. Rules are stored as Markdown files under the data directory.
• 🔌 Pluggable backend — every specialist can pick its own agent (built-in, Claude Code, Codex, etc.).
• 🎛️ Customizable — built-in specialists allow tweaking backend, rules, skills, and description.
• 🧩 Stackable skills — multiple skills can be enabled at once. Skills can be built-in, user-imported, or extension-contributed.

​

Picking a specialist

​

Hiring a custom specialist

​

Configuring rules

• 🔁 Workflows — “When the user asks for X, do A, then B, then C”
• 🚧 Constraints — “Never modify files outside the project root”
• 📚 Domain context — “This codebase uses Bun + Vite; tests are Vitest”
• 🎨 Output style — “Always answer in Markdown with a TL;DR at the top”

​

Example rule file

# File Management Specialist

## Path conventions
- All files mentioned by the user live under the current project directory unless explicitly stated
- Use Glob to locate files when only the name is given — never ask "where is the file?"
- Avoid creating new files when an existing one can be edited

## Execution principles
- Break complex tasks into steps and report progress
- Confirm destructive operations (delete, overwrite) before executing
- Keep solutions minimal and focused

• ✏️ Be explicit — short imperative sentences work best.
• 📋 Use headings and bullet lists; agents pay attention to structure.
• 💡 Provide concrete examples for cases you care about.
• 🚫 Don’t dump large reference docs into rules — use Skills for that.

​

Configuring skills

1. Open the specialist → Skills section.
2. Toggle existing skills on/off with checkboxes.
3. To add custom skills, click Add skills and pick a path or paste an absolute path.

​

Editing and deleting specialists

​

Specialist vs. model

​

Use cases

# File Management Specialist

## Core duties
- Batch rename, smart classify, and organize files in the project directory
- Never delete without explicit confirmation
- Report a summary of every operation after completion

## Naming conventions
- Use snake_case for all new files
- Prefix temp files with `tmp_` and clean them up at the end of each session

# Code Review Specialist

## Review checklist
- Flag debug prints (console.log, print, fmt.Println)
- Flag hardcoded secrets (API keys, passwords, tokens)
- Flag bare except/catch clauses
- Flag unresolved TODOs and FIXMEs
- Check for missing tests on new functions

## Output format
- List issues by severity: Critical, Warning, Info
- Include file path and line number for each issue
- Suggest a fix for each Critical issue

# Research Specialist

## Process
1. Break the research question into sub-questions
2. Search for each sub-question independently
3. Cross-reference findings across sources
4. Flag contradictions and gaps
5. Write a structured summary with citations

## Output
- Executive summary (3 sentences)
- Key findings (bullet list with source links)
- Gaps and contradictions
- Recommended next steps