The Golden Rule of Overrides
NEVER hack core system prompts via
AGENTS.mdinjection. OMP uses an elegant, “Oh My Zsh”-style Overlay Filesystem at~/.omp/agent/. If a file exists here, it cleanly shadows and replaces the core package default. 100% native, zero dirty hacks.
🏗️ The Overlay Architecture
| Target | Overlay Path | Action / Effect |
|---|---|---|
| 🤖 Agent Roles | ~/.omp/agent/agents/<role>.md | Drop designer.md or plan.md here. Instantly overwrites the built-in agent persona for all projects. |
| ⚙️ Model Tiers | ~/.omp/agent/config.yml | Edit the modelRoles: block to remap smol, slow, or default to different LLMs on the fly. |
| 🪄 Magic Words | ~/.omp/agent/system/<notice>.md | Shadow core system notices (like ultrathink-notice.md) to redefine what magic words do globally. |
| 🔧 Skills & Tools | ~/.omp/agent/skills/<skill>.md | Expand the agent’s capabilities. Auto-loaded as skill://<name>. Managed via manage_skill. |
⚡ Quick-Start: Overwriting an Agent
Want to completely redefine the Designer agent?
- Locate: Decide which agent to overwrite (e.g.,
designer). - Create: Open or create
~/.omp/agent/agents/designer.md. - Write: Define your absolute, god-tier instructions:
# Custom Designer You are the ultimate UX/UI god. Strictly use Tailwind CSS v4 and standard OKLCH colors... - Deploy: The moment OMP spawns the
designer, it uses your overlay. Zero restarts.
🧠 Pro-Tips for Peak Efficiency
- Config is Live: Saving
config.ymlupdates model routing instantly. No server reboots required. - Keep it Modular: Only overlay what you explicitly need to change. Let the core package handle the rest.
- Know the Scope:
AGENTS.md= Project-specific context (lives in your repo).~/.omp/agent/= Global architecture overlay (lives on your machine).