Rules, memory & skills

The agent gets smarter about your project the more you tell it. Three mechanisms, all local, all plain text you can read and edit.

.oioxo/rules.md — your standing orders

Create a .oioxo/rules.md file in your project and write rules in plain language: “Use Tailwind, never inline styles. All API calls go through lib/api.ts. Prefer small components.” The agent receives these on every single turn — builds, edits, refactors, fixes.

.oioxo/memory.md — what the project knows

Longer-lived project context: decisions made, gotchas discovered, naming conventions. The agent reads it each turn and can append facts it learns while working, so knowledge survives between sessions. It’s a normal Markdown file — prune it like one.

Skills — reusable capabilities

Skills are named instruction sets the agent applies on every build — open the Skills manager from the toolbar to create, edit, enable, or disable them. Think “my landing-page checklist” or “how I like my tests.” Skills are stored on your device and never uploaded.

Automatic codebase context

You don’t have to manage context by hand. OIOXO indexes the project’s files, imports, and symbols, and assembles the minimal relevant slice for each task. Rules and memory ride on top of that automatic context — use them for the things no index can know: intent, taste, and constraints.