OpenCode Config Agent ships a shareableDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/lnardev/opencode-config-agent/llms.txt
Use this file to discover all available pages before exploring further.
opencode.json configuration that turns your AI coding sessions into something closer to working alongside a seasoned senior engineer. Instead of a default assistant that silently hands you code snippets on demand, this config installs Tony Stark — a 15-year-veteran Senior Architect persona that teaches, pushes back, corrects ruthlessly, and forces you to understand the fundamentals before you write a single line. It also ships a second primary agent, sdd-orchestrator, which coordinates a full suite of Spec-Driven Development sub-agents for structured, large-scale changes. Both agents are wired to the Engram persistent memory system so context survives across sessions, compactions, and context-window resets.
Agents in this config
tony stark
Primary agent — Mentor & Architect modeLoaded directly from
AGENTS.md. A Senior Architect with 15+ years of experience, GDE & MVP credentials, Colombian coastal personality, and an absolute refusal to hand you code without understanding. Tools: edit, write.sdd-orchestrator
Primary agent — SDD CoordinatorCoordinates the full Spec-Driven Development workflow: explore → propose → spec → design → tasks → apply → verify → archive. Delegates all real work to hidden sub-agents; never inflates its own context. Tools:
bash, delegate, delegation_list, delegation_read, edit, read, write.How to activate Tony Stark
Tony Stark is configured as aprimary mode agent in opencode.json, so it appears in the OpenCode agent picker alongside any other primary agents you have installed.
Select the agent
Open the agent picker (default shortcut:
/ or the model/agent selector in the chat bar) and choose tony stark from the list.You can also reference the agent by typing
tony stark in a session that supports inline agent switching. Tony Stark’s prompt is loaded directly from the AGENTS.md file in the config repo via the {file:./AGENTS.md} directive in opencode.json.What Tony Stark will and won’t do
Understanding the boundaries upfront saves you from frustration — the push-back is intentional and part of the value.- Will do
- Won't do
- Explain why something is architecturally wrong before suggesting a fix
- Use construction and engineering analogies to make abstract concepts concrete
- Propose alternatives with real tradeoffs instead of giving a single answer
- Auto-load context-specific skills (e.g.
go-testingwhen it detects Go tests) - Proactively save decisions, bug fixes, and discoveries to Engram memory
- Verify technical claims against code or docs before stating them as fact
- Acknowledge mistakes — with evidence — when it’s wrong
- End every session with a mandatory
mem_session_summaryso the next session starts with full context
Tools available to Tony Stark
Thetony stark agent in opencode.json is intentionally scoped to a minimal, focused tool set:
| Tool | Purpose |
|---|---|
edit | Modify existing files — used only after explaining the change |
write | Create new files — similarly gated by context and reasoning |
bash, read, delegate) are intentionally absent. Tony Stark is a mentor and architect, not an autonomous executor. If you need automated multi-file operations, switch to the sdd-orchestrator agent.
Explore further
Personality & Philosophy
Deep dive into Tony Stark’s language rules, Colombian coastal tone, core philosophy pillars, and exact behavior when you ask a bad question.
Engram Memory
How persistent cross-session memory works, when the agent saves automatically, the session-close protocol, and what happens after a compaction.
SDD Overview
The full Spec-Driven Development workflow coordinated by the
sdd-orchestrator agent — from exploration to archived change records.