aj604/agentic-atlas
Do design work with Agentic Atlas over hosted MCP at agentic-atlas.dev/mcp/. Three skills — audit an existing agent artifact, design a new agent system, apply one named pattern — over two read-only agents; no SDK, CLI, local server, or content bundle is installed.
Apply one named Agentic Atlas pattern to one existing skill, agent, plugin, or workflow as concrete, cited edits. Use when the user points at a specific pattern (by id, title, or agentic-atlas.dev link) and wants their artifact changed to follow it: "apply this pattern to my skill", "retrofit my plugin with progressive disclosure". A review against every pattern goes to reviewing-agent-designs; nothing built yet goes to designing-agent-systems. Changes that do not trace to a named pattern stay with the normal development workflow.
Design a new agent system (skill, subagent, plugin, hook set, or multi-agent workflow) from the Agentic Atlas patterns, with a citation behind each structural choice. Use when the user is starting one or rethinking its shape: "help me design an agent for X", "should this be one agent or several", "what context should each dispatch carry", or where verification belongs in the decomposition. Also answers quick atlas questions like "what does the atlas say about X". An artifact that already exists goes to reviewing-agent-designs; one named pattern to retrofit goes to applying-a-pattern. Not for ordinary software design (schemas, APIs, app code).
Audit an existing agent artifact (skill, subagent, plugin, hooks, or multi-agent workflow) against the Agentic Atlas patterns and return cited, checkable findings. Use when the user wants something they already wrote reviewed, critiqued, or graded: "review my skill", "is this agent definition right", "why does my skill never trigger", even if they never mention the atlas. Nothing written yet goes to designing-agent-systems; one named pattern to retrofit goes to applying-a-pattern. Not for ordinary application code that merely sits near agents.