Step-by-Step: Authoring Custom Slash Commands in aiFetchly

Direct Answer: Power users author custom slash commands in aiFetchly by saving structured Markdown prompt templates with YAML frontmatter into a personal or workspace commands directory. Argument hints, {{arg}} substitution tokens, and autonomous /goal loops turn multi-clause prompts into instant keystroke shortcuts.

Prompt fatigue is a pervasive friction point in advanced agentic development workflows. As local developer environments and AI chat tools converge, engineers waste context repeatedly copy-pasting structured instructions and system constraints. The aiFetchly desktop application solves this with AI Chat V2: low-latency keystroke autocomplete, dynamic parameter injection, and a resilient four-tier command resolution hierarchy.

Here is how power users can build, configure, and execute custom slash commands in three straightforward steps.

Step 1: Create Your Command Markdown Template

Custom slash commands in aiFetchly are plain Markdown files stored inside your local commands directory (~/.aifetchly/commands/ for personal macros or .aifetchly/commands/ in your workspace root for project-wide templates). Each command requires YAML frontmatter defining its invocation trigger, human-readable description, and expected argument tokens.

Create a file named audit.md:

---
name: audit
description: "Audit security and code style for a target file"
arguments:
  - name: path
    description: "Path to source file"
    required: true
---

Review the source code at `{{path}}`. Check for unvalidated inputs, race conditions, memory leaks, and adherence to clean architecture principles. Output findings in an actionable markdown table.

When you type /audit in the chat composer, aiFetchly's autocomplete menu parses the frontmatter in milliseconds, displaying your description and prompting for the required {{path}} argument.

Step 2: Leverage the Four-Tier Scope Resolution

aiFetchly evaluates slash commands through a strict hierarchical scope structure to eliminate namespace collisions across teams:

1. Built-in Commands: Core primitives bundled with the client runtime, including /goal, /loop, /compact, and /model.
2. Workspace Commands: Shared repository templates stored in ./.aifetchly/commands/ that sync across engineering teams via version control.
3. User Commands: Personal productivity macros located in ~/.aifetchly/commands/ available across all your local projects.
4. Plugin Commands: Specialized capabilities contributed by installed extensions and Model Context Protocol (MCP) servers.

Workspace commands gracefully override user defaults, ensuring uniform review standards across collaborative projects while preserving individual developer customization.

Step 3: Chain Autonomous Execution Loops

For complex workflows, custom macros can invoke built-in autonomous loops. Chaining /goal or /loop inside your custom templates lets aiFetchly iteratively generate code, evaluate compiler errors, and refactor codebases until predefined exit criteria are met. This converts repetitive multi-turn guidance into a single, reliable command execution.

For complete frontmatter specifications and advanced templating filters, consult the official Slash Commands manual. Building modular prompt macros turns routine debugging and code generation into frictionless, repeatable keystrokes.

---

Which slash command would you author first — /audit, /review, or a team-specific macro?