For agents

Codex

Use the AGENTS.md file or JSON export to add Blueprint doctrine to Codex-based workflows.

Install the doctrine file

Download AGENTS.md from the agent assets page and place it at the root of your repository. Codex reads AGENTS.md automatically — it is the canonical multi-tool doctrine file for repo-aware agents. No configuration or restart is required.

What Codex reads

AGENTS.md carries the same eight core directives as the Cursor rule file, plus explicit guidance on agent boundaries, approval flows, reversibility, and structured output requirements. It is updated in sync with the live MCP content and can also be downloaded as a JSON or Markdown export for offline use.

Optional MCP layer

If your Codex setup supports MCP configuration, add the Blueprint public endpoint (https://aidesignblueprint.com/mcp) for live principle and example retrieval. The AGENTS.md file works standalone — MCP is additive, not required.

Codex

MCP + local exports

Register the MCP endpoint with the same `.mcp.json` block used by the other clients. Keep the JSON or Markdown export as a local fallback when you want a readable doctrine bundle without live calls.

MCP config

{
  "aidesignblueprint": {
    "type": "http",
    "url": "https://aidesignblueprint.com/mcp"
  }
}

Agentic Design Blueprint JSON Agentic Design Blueprint Markdown

Kickoff prompt

Configure the blueprint as an HTTP MCP server and keep the local JSON as fallback. Start with list_principles, then search examples for visibility, orchestration, or steering based on the task.

Also in this section

Cursor Claude Code Start here