af
The af skill provides a quick reference for Agent Farm CLI commands used to manage Tower (the dashboard server), builders, and project workflows. Use this when running af commands to verify correct syntax, available subcommands, and required flags, particularly for spawning builders, checking status, managing dashboards, and performing cleanup operations.
git clone --depth 1 https://github.com/majiayu000/claude-skill-registry /tmp/af && cp -r /tmp/af/skills/agent/af ~/.claude/skills/afSKILL.md
# Agent Farm Quick Reference
## Tower (Dashboard Server)
```bash
af tower start # Start Tower on port 4100
af tower stop # Stop Tower
af tower log # Tail Tower logs
af tower status # Check if Tower is running
```
There is NO `af tower restart` — use `af tower stop && af tower start`.
## Dashboard
```bash
af dash start # Start architect dashboard for current project
af dash stop # Stop dashboard for current project
af dash open # Open dashboard in browser
```
## Builder Management
```bash
af spawn -p 0003 # Spawn builder for spec (strict mode, default)
af spawn --soft -p 0003 # Spawn builder (soft mode)
af spawn --issue 42 # Spawn builder for a bugfix
af spawn -p 0003 --resume # Resume builder in existing worktree
af status # Check all builder status
af cleanup --project 0003 # Clean up builder worktree (safe)
af cleanup --project 0003 -f # Force cleanup
```
### Resuming Builders
When a builder's Claude process dies but the worktree and porch state survive,
use `--resume` to restart it without recreating the worktree:
```bash
af spawn -p 0003 --resume
```
This reuses the existing `.builders/0003` worktree, creates a fresh terminal
session registered with the Tower (so it appears in the dashboard), and lets
porch pick up from whatever phase the builder was in. Works with all spawn
modes: `-p`, `--issue`, `--task`, `--protocol`, `--worktree`.
## Utility
```bash
af util # Open utility shell
af open file.ts # Open file in annotation viewer
af ports list # List port allocations
af send <builder> "msg" # Send message to a builder
```
## Configuration
Edit `af-config.json` at project root to customize shell commands.
```json
{
"shell": {
"architect": "claude",
"builder": "claude",
"shell": "bash"
}
}
```
## Pre-Spawn Checklist
**Before `af spawn`, commit all local changes.** Builders work in git worktrees
branched from HEAD — uncommitted files (specs, plans, codev updates) are invisible
to the builder. The spawn command will refuse if the worktree is dirty (override
with `--force`).
## Common Mistakes
- **Spawning with uncommitted changes** — builder won't see specs, plans, or codev updates
- There is NO `codev tower` command — Tower is managed via `af tower`
- There is NO `restart` subcommand — stop then start
- There is NO `af start` for Tower — use `af tower start` or `af dash start`Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. This should trigger for requests such as Create AGENTS.md; Update AGENTS.md file; Add agent instructions. Part of cursor-rules-java project
>
Generated skill from request: trinity auto-boot validator
Create your OpenAI Agents SDK skill in one prompt, then learn to improve it throughout the chapter
Create your OpenAI Agents SDK skill in one prompt, then learn to improve it throughout the chapter
Create your Google Agent Development Kit skill in one prompt, then learn to improve it throughout the chapter