Understanding an unfamiliar project
Start with read-only investigation before deciding what to change. To restrict tool operations, choose Read Only in/permissions.
/init to capture project conventions in AGENTS.md.
See Migrating from other agents for reusing project instructions from other tools.
Implementing a feature
Provide requirements and acceptance criteria together. Plan first when changes span modules.Fixing bugs
Include symptoms, reproduction conditions, expected behavior, and relevant files. Attach screenshots or use! to add diagnostic command output to context.
Tests and refactoring
/fork to separate conversation experiments. Code changes still share the working directory; use a Git worktree when file isolation is needed.
Delegating long tasks
Use/goal for hours-long work. Step Code continues after you set the goal; check progress with /goal status.
/goal pause to pause and /goal resume to continue. Keep the process and network available. See Goal mode.
Ask the model to create a cron schedule for recurring work, such as dependency security checks, and manage it with /cron. Scheduled tasks require the Step Code process to remain running.
Parallel agents
Use workflow for batches of similar tasks, such as audits or comparing alternatives. Explicitly authorize it withultraloop or ultracode; task size alone does not enable it.
Publishing static websites
The built-in steppage plugin publishes a directory as a shareable static website. Install it and setSTEPFUN_API_KEY:
/mcp, then request deployment:
Generating and maintaining documentation
/export to preserve important discussions.
