Factory Droid — Commands
- File format
- Markdown
- Discovery path
-
.factory/commands - Global install path
-
~/.factory/commands - Syllago install method
- Symlink, Direct copy
- Symlink support
- Yes
Features
How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.
Other features
Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.
| Feature | Conversion | Summary |
|---|---|---|
argument_substitution | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | $ARGUMENTS substitution in Markdown-type commands; equivalent to Claude Code's $ARGUMENTS pattern; Executable commands receive args via shell process stdin/args |
| Command Discovery Paths | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | Commands are discovered from .factory/commands/ (project) or ~/.factory/commands/ (personal); filename becomes the slash command name. |
| Two Command Types | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | Commands are either Markdown templates (with $ARGUMENTS substitution) or Executable scripts whose stdout is injected into the conversation. |
| Skills Supersede Commands | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Factory's docs recommend skills over commands for new work; commands remain supported only for backwards compatibility. |
Sources
| Source |
|---|
| https://docs.factory.ai/cli/configuration/custom-slash-commands |