The anthara plugin
The anthara plugin is a Claude Code plugin. It gives a developer’s session three things: commands for planning and building work, your organization’s coding standards, and shared memory.
This page describes version 0.16.0.
How it loads
Section titled “How it loads”The plugin lives inside each repository, in the .anthara/ folder. Anthara commits it there when someone activates the repository.
When a developer starts Claude Code in the repository, a session-start hook installs the plugin from that folder. There is no separate download. For the developer’s steps, see Install the plugin and sign in.
What it contains
Section titled “What it contains”| Part | Count | What it is |
|---|---|---|
| Commands | 14 | Slash commands you run, such as /anthara:start. |
| Craft skills | 8 | Guidance that loads by itself when the work calls for it, such as code-craft. |
| Agents | 9 | Helpers that some commands start, such as slice-builder. You don’t start them yourself. |
| Hooks | Scripts that run at set points in a session. They are described below. | |
| MCP servers | 2 | anthara-fabric and chrome-devtools. |
Commands
Section titled “Commands”| Command | What it does |
|---|---|
/anthara:start |
Asks what you want to do and suggests the right command. |
/anthara:brainstorm |
Explores options for an open-ended problem. |
/anthara:discovery |
Turns research notes and interviews into one sourced brief. |
/anthara:spec-writer |
Writes a spec split into slices that can each be tested. |
/anthara:create-ticket |
Creates a ticket in your tracker, from a spec or from a description. |
/anthara:planner |
Writes the step-by-step plan for building a spec or ticket. |
/anthara:plan-implementer |
Builds a plan slice by slice, then reviews the result. |
/anthara:collaboration-loop |
Answers @anthara comments you left in a spec or brief. |
/anthara:debug-fix |
Works through a bug from reproduction to a tested fix. |
/anthara:code-review |
Reviews a pull request and posts its findings as one comment. |
/anthara:pr-walkthrough |
Explains a pull request so you can review it. |
/anthara:workflow-builder |
Drafts an agentic workflow YAML file from a short interview. |
/anthara:inbox |
Ranks the work waiting for you across your connected tools. |
/anthara:team-update |
Summarizes what your team did over a period of time. |
Plugin commands lists every command, skill, and agent.
What the hooks do
Section titled “What the hooks do”Hooks run without being asked. These are the ones a developer notices.
| Hook | When it runs | What you see |
|---|---|---|
| Sign-in check | At session start and on every prompt | If you have not signed in to Fabric, your prompt is not sent. A message tells you to run /mcp and authenticate. |
| Standards loading | At session start and on every prompt | Before Claude writes code, it asks Fabric for the standards that apply to the repository and the task. |
| Craft selection | At session start and on every prompt | Claude loads the craft skills that match the work, and names them in one line. |
| Shared memory confirmation | Before each shared memory write | Claude Code asks you to approve the write and shows the text to be saved. |
| Local memory block | Before each file write | Writes to Claude Code’s local memory folder, .claude/projects/*/memory/, are refused. Memory goes to Fabric. |
| Memory reminders | On every prompt and before context is compacted | Claude is reminded when to search memory and when to save something. |
Two more hooks report to Fabric and show nothing to the developer:
- A usage hook records which Anthara command or skill ran, with a session identifier.
- A findings hook records the findings from review agents.
Every call to a Fabric tool also carries the session identifier, so Fabric can group one session’s activity.
Bundled MCP servers
Section titled “Bundled MCP servers”The plugin’s .mcp.json file declares two servers.
| Server | Type | Purpose |
|---|---|---|
anthara-fabric |
HTTP | Memory and standards. See Fabric MCP. |
chrome-devtools |
Local command | Lets Claude drive a browser to check UI work. It runs npx -y chrome-devtools-mcp@latest, so it needs Node.js and network access to the npm registry. |
What the plugin does not do
Section titled “What the plugin does not do”- It does not write
.cursorrulesor any other rules file into your repository. Standards are fetched from Fabric during the session. - It does not need an API key. Developers sign in to Fabric in the browser.