A design team inside Claude Code. You give it a raw topic, or just a question. Hydra frames it, analyses it, looks at what others do, explores options and builds them into protos with your design system. You get deliverables you can decide on.
A screen that underperforms, a new screen to design, a page to audit, best practices for a component, an idea to challenge, a label to choose, a build to check against the design. Hydra does the work of a small team around the designer (analysis, research, exploration, UX writing, design QA), and the designer makes the decisions.
It isn't a screen factory. Hydra thinks before it builds. It works out what is true in your product, looks for what works elsewhere, pits several options against each other, and tells you which one it recommends, why, and on what evidence. It won't just tell you what you want to hear: if an idea is weak, it says so and explains why. And when it doesn't know something, it says so instead of making it up.
topics/.Not everything needs the whole chain. Hydra picks the heads based on your request; you don't have to name them. It stops at the deliverable you asked for and suggests the next step, without running it on its own.
| You ask | You get |
|---|---|
| “Audit this page”, “find the friction points in this journey” | The topic sheet and the report: prioritised findings, hypotheses, references, actions. Hydra then offers to explore options. |
| “What are the best patterns for…”, “best practices for…” | A short research deliverable: the answer, how confident it is, the screens as images and links to the sources. |
| “What do studies say about…”, “what works for…”, on a specific question | A research deliverable: what studies, articles and guides establish, what it means for your topic, and the strength of the evidence. |
| An in-depth benchmark or state-of-the-art review | The topic sheet and a full research deliverable: conclusions, what remains unknown, dated references, including live visits to real products. |
| “Challenge this idea”, “help me decide” | The topic sheet and the report: the options, their critique, a recommendation. Hydra then offers to build them into protos. |
| “What should this label say?”, “review this copy” | Reasoned variants, right in the conversation, or a table for a whole screen. |
| “Does it match the design?” | The design QA: the list of fixes for the developer, with measured values. |
When framing, Cortex recommends a mode, and you choose.
Protos straight away, or after your review. When framing, Cortex also asks when to build the protos, the most expensive part. Either straight away, or after you've read the topic sheet, the report and the brief. In the second case, Hydra stops at the brief, and you ask for the protos if the options are worth it.
Hydra can push back on your request, but it still answers it. If it thinks the problem is badly framed, it tells you, and shows its own reading alongside, clearly labelled. But its options and its recommendation serve your goal, not its own. A constraint from your mission (a legal requirement, a brand principle) changes how the goal is reached, never the goal itself. Some decisions are never Hydra's: defining the problem, the metric and its threshold, the scope. They come back to you, even when it runs in one go.
Hydra talks to you and writes its deliverables in your mission's working language: the one you write to it in, which the welcome session records. If in doubt, it uses French. In English, everything switches to English: the headings, the deliverable names and the rendered pages. In any other language, the text is in that language and the headings stay in English.
The copy in the protos follows your product's language, which may be different: you can work in English on a product in French. A label or a quote taken from the product stays as it is, never translated. The method itself is written in French, but you never need to read it.
Each head has its own method. Cortex decides how to run the topic; the others do the work. A topic's discovery phase brings two of them together: Audit, which looks at your current product, and Research, which looks elsewhere. Three heads keep their French names: Maquette (mockups), Recette (design QA) and Accueil (welcome).
02-research), when research is the topicEverything is written in the topic's folder, in markdown turned into HTML pages. Visual references are stored there as images you can open anywhere. The protos are HTML pages: they open in the browser, you can click through them, and they never touch your design file. A finished topic goes into topics/.archive/.
The method is the same for everyone. The context/ folder tailors it to your mission, the client project you're working on: the client, the scope, the business vocabulary, the users, the metrics, the design system, the tone, the tools, the language. Changing missions means replacing this folder, nothing else.
The welcome session sets up the empty templates and fills them in with you, from your answers, a mission brief or a study readout. The mission file comes first, because it pays off the most: the exact domain, your platforms, the team's real jargon, what the team can take on.
Nothing has to be complete right away. Each time it frames a topic, Hydra compares what the topic mentions with what the context holds, asks for what's missing, then offers to add it. It writes it with your approval, and never makes things up to fill a gap.
The design system is read from your libraries. Hydra writes up its foundations, the list of components and the usage rules (principles, what's fixed and what's flexible, rules per component, responsive behaviour), and you approve them. If your team already has a design system file in markdown, it's used as is. Users are described along axes rather than as personas: what changes a design decision, and the combinations that come up, each with its strength of evidence. Tone of voice guidelines are optional. Without them, Writer picks up your product's tone and suggests it to you.
Hydra isn't tied to any tool by name. It reads the tools your mission declares, role by role, and uses them.
A tool declared but not connected: Hydra helps you connect it. No tool for a role: it says so, works without it, and lowers its confidence where it matters. Never silently.
Accessibility and mobile-first design are among the rules every option must meet, along with those your mission declares.
Ideas, not promises:
For a product designer working on a client project who wants a real working partner: someone who analyses what exists, finds the references, challenges their ideas instead of flattering them, and hands over deliverables they can decide on.
You need Claude Code with access to Opus, Node.js 22 or later, and Chrome. You can install Hydra in two ways, and both run the same method: as a Claude Code plugin, for your mission folder only (two commands to install, one to update), or as a copy, downloaded as a ZIP, with no git needed. Requirements and installation are in the README.md, on github.com/MCQX7/hydra-agent.
With the plugin, start Claude Code in your mission folder and write “I just installed Hydra”. It sets up its rules and your context templates there, and the welcome session starts when you restart Claude Code in that folder. With the copy, open a session in Hydra's folder and start with “I just launched Hydra”. The welcome session fills in your context with you; then you start your first topic.
Allow a few minutes for a question, and twenty to thirty minutes for a full topic, through to the protos. Hydra is tuned for Opus at high effort, and that's deliberate. It also works with Sonnet or at a lower effort if your plan doesn't allow more, but its deliverables are weaker.