Back to index

Task Types

agent-sync supports the following three task types:

1. Memory (type: memory)

Defines context information for AI agents. This serves as the agent’s “memory” and can include general rules, architecture information, coding style, etc.

Default output locations:

Note: For Roo, Cline, and similar agents, {filename} is derived from the input file’s basename (the filename without its directory path). For example, an input file named my-project/memories/coding-rules.md would result in an output file named coding-rules.md in the appropriate output directory.

2. Command (type: command)

Provides custom command definitions for AI agents. This creates shortcuts for performing specific tasks.

Default output locations:

Note: For Claude, Cline, Copilot, and similar agents, {filename} is derived from the input file’s basename (the filename without its directory path). For example, an input file named my-project/commands/deploy.md would result in an output file named deploy.md in the appropriate output directory.

3. Mode (type: mode)

Defines subagents/modes for compatible agents (Claude Code subagents and Roo custom modes). Frontmatter defines agent-specific mode metadata; the body is processed through the template engine.

Default output locations:

Notes:

• Directory path (trailing slash) = per-file outputs. File path (no trailing slash) = aggregation into a single file.
• Roo modes default to aggregation into a single file: .roomodes for project scope, and custom_modes.yaml in VS Code globalStorage for user scope.
• Claude modes default to per-file markdown outputs under .claude/agents/ (project) or ~/.claude/agents/ (user).

Roo mode output path details:

• Project scope example (aggregation):
  • .roomodes in the project root (single YAML file aggregating all modes)
• User scope examples (aggregation to VS Code globalStorage custom_modes.yaml):
  • macOS: ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/custom_modes.yaml
  • Linux: ~/.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/custom_modes.yaml
  • Windows: %APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\custom_modes.yaml

Trailing slash rule examples:

• Directory (per-file): ".claude/agents/" → each input mode becomes its own file
• File (aggregation): ".roomodes" → all input modes aggregated into one YAML file
• For Roo modes, the defaults are aggregation-oriented (no trailing slash).

Agent-specific Command Frontmatter

Each agent may support specific frontmatter attributes for commands:

Claude Command Frontmatter

• claude.description: Brief description of the command shown in the help menu
• claude.allowed-tools: List of tools the command is permitted to use

Roo Frontmatter (slash commands)

Supported frontmatter:

• Top-level:
  • description: Brief description of what the slash command does
• Roo-specific (under roo:):
  • argument-hint (optional): Short hint string for expected arguments (e.g., “[path]” or “[owner repo]”)

Legacy compatibility:

• If no top-level description is provided, agent-sync maps legacy Roo fields:
  • description is synthesized from roo.roleDefinition if present, otherwise from roo.name
• Legacy roo.whenToUse and roo.groups are ignored in slash command output

Cline Frontmatter

• Cline workflows use standard markdown without special frontmatter requirements

Copilot Command Frontmatter

• mode: The operational mode for Copilot (e.g., “chat”, “inline”)
• model: The specific model to use
• tools: List of available tools
• description: Brief description of the prompt’s purpose

Navigation

• Main Configuration Guide
• Configuration Reference
• Input and Output Processing
• Template System
• Command Line Interface
• Troubleshooting
• Examples and Best Practices

Back to index