For engineering teams

Every coding agent your team runs, working from the same standards.

Claude Code on one laptop knows your conventions. The agent on the next laptop doesn't. Put architecture decisions, coding standards and runbooks in one governed place, and every agent reads the version your leads approved.

Get PromptOwl free Get a demo

In their words

What engineering teams say when AI starts to drift.

Each of these has the same cause: the knowledge your AI needs has no governed home that every agent reads from. Find your problem →

“Each engineer's agent follows a different set of conventions.”
“The agent suggested the pattern we retired last quarter.”
“New engineers spend their first month asking where the decisions are written down.”
“We re-explain the architecture at the start of every session.”

One set of standards for every agent

Shared, approved context is how a dozen engineers' agents stop pulling in a dozen directions.

Your team's shared brain

What goes in, and the agents that run on it.

What goes in

Architecture decisions, with who decided and when
Coding standards and review rules
Runbooks and incident playbooks
Onboarding guides for new engineers

Each area gets an owner who approves changes, so agents read the version your team signed off on.

Code reviewer

Checks pull requests against the approved standards.

Never sees: HR, finance or customer data.

Onboarding guide

Answers a new engineer's questions from the decisions and runbooks.

Never sees: Draft decisions nobody has approved.

Incident helper

Pulls the right runbook while an incident is open.

Never sees: Retired runbooks.

Get started

Three steps to a working start.

1
Start a nest from the developer starter
One command creates a nest with folders for architecture, standards and onboarding. Or distill a GitHub repository into a first draft of the same thing.
Terminal
```
$ npx @promptowl/contextnest-cli init --starter developer
```
Distill a GitHub repo →
2
Add what you already have and approve it
Drop in your ADRs, style guides and runbooks. A lead approves each area, so agents read the approved version.
Download ContextNest free →
3
Connect your agent and ask it to map how it can help
In Claude Code, add the ContextNest plugin (or use the Connect button in a hosted nest), then paste the prompt below. It reads your nest, proves it, and drafts an opportunity map for you to approve.
In Claude Code
```
$ /plugin marketplace add promptowl/contextnest
```
Then
```
$ /plugin install contextnest
```

Map how it can help

Ask your agent what it could do for your team.

Paste this into Claude Code once it's connected to your nest. The agent proves it can read your knowledge, then drafts an opportunity map for you to approve.

Claude Code · a fictional support team's nest

Example

1. Prove it
2. Get oriented
3. Map it
4. Save as a draft

The prompt

My team is the engineering team.

You're connected to my ContextNest nest. Before anything else, prove it: search the nest, open two or three documents, and tell me their titles and one line from each. If you can't read real documents, say so and stop. Don't guess what's in the nest.

Use search and single-document reads. If one way of reaching the nest fails, try the other tools you have (the ContextNest MCP tools, the ctx command line or the REST API) before you give up.

If the nest is empty or nearly empty, ask me three questions first: what my team does, which questions people ask us most, and which documents we'd trust an agent to answer from. Then work from my answers.

Then build me an opportunity map:
1. Five things you can do for me today with what's in the nest. For each one, name the documents it relies on.
2. What's missing: the documents or decisions that would let you do three more things, and who on my team probably owns each one.
3. The agents you'd run on this nest: what each one does, and what each one should not be allowed to see.

Save the map back to the nest as a draft titled "How AI can help us: opportunity map". Don't publish it or share it anywhere. Ask me before you publish anything.

One shared brain

Every team adds its own area.

Start with one team. The next team starts from what's already approved.

See every team See how it can help

Start with your team. Free.

Connect the AI tools you already use, and approve what they're allowed to rely on.