Skip to main content
Your best engineers have prompts that work - ways of reviewing code, writing tests, or debugging issues that they’ve refined over time. Slash commands let you capture that expertise and share it with everyone. Type /review-code and get a review with the same rigor your senior engineer would apply. Type /security-check and catch the vulnerabilities they’d catch. Everyone gets access to your team’s best practices.

​
Why this matters

Without shared commands, quality varies. One developer’s code review catches security issues; another’s misses them. One person knows how to write tests that actually test behavior; others write tests that just hit coverage targets. With slash commands:
  • Expertise scales: A senior engineer’s review checklist becomes available to the whole team
  • Quality standardizes: Everyone follows the same thorough process
  • Onboarding accelerates: New team members immediately have access to proven workflows

​
What a great command looks like

Here’s a real example - a code review command that captures one engineer’s review philosophy: 
/review-like-mads

You are reviewing code changes with Mads Hartmann's perspective. Apply his review philosophy systematically:

## Design System First
- **Theme compatibility**: Works in light/dark AND old/new themes?
- **Semantic tokens**: Replace hardcoded colors with `border-subtle`, `surface-glass`
- **Visual evidence**: Request screenshots/videos if missing
- **Design alignment**: Matches Figma specs?

## Aggressive Cleanup
- **Remove unused**: Components, imports, files, commented code
- **Consolidate**: Similar components that could be unified
- **File organization**: Components in right locations?

## Technical Excellence
- **React patterns**: Proper `forwardRef`, `useImperativeHandle`, TypeScript
- **Component reuse**: Composing existing vs creating new
- **Accessibility**: ARIA, keyboard nav, screen readers

## Red Flags
- Hardcoded colors (`#fff`, `rgb()`)
- Duplicate patterns
- Missing visual docs
- Poor TypeScript

**Priority order**: Design system consistency → Code cleanliness → Component reusability → Technical implementation → Test coverage
Now anyone can type /review-like-mads and get a review with that level of rigor.

​
More examples

CommandWhat it codifies
/security-reviewYour security team’s checklist for reviewing PRs
/write-testsHow your team writes tests that actually catch bugs
/explain-thisYour standard for documentation and code explanation
/debug-strategyYour senior engineer’s approach to debugging
/deploy-checklistEverything to verify before shipping

​
Create your first command

  1. Go to Settings > Agents
  2. Click New Command
  3. Configure:
    • Name: What appears in the command list (e.g., “Review like Mads”)
    • Command: The slash trigger (e.g., review-like-mads)
    • Description: When to use it
    • Prompt: The full prompt text
  4. Click Create Command
Ona settings interface for creating a new custom slash command with name, trigger, description, and prompt fields

​
Using commands

Type / in Ona Agent to see available commands. Start typing to filter, then select with arrow keys or click. You can add context after the command: 
/review-like-mads

Focus especially on the authentication changes in src/auth/
Ona Agent combines your command’s prompt with the additional context you provide.

​
Tips for good commands

Capture real expertise: Base commands on how your best people actually work, not theoretical ideals. Be specific: /security-review is better than /review. Include the actual checklist, not just “check for security issues.” Include priorities: Tell agents what matters most. “Focus on X before Y” helps them make tradeoffs. Update over time: When someone catches something your command missed, add it to the prompt.

​
Next steps