A new hire's first week

Small teamsStartup adding its 6th engineer

Our new engineer's agent kept proposing patterns the team had dropped months ago: Redux, a REST layer we had removed, a second ORM.

How do I get a new engineer's AI agent to follow our team's existing conventions?

Record team decisions with ArcRoom's arcroom decide, and add rules for what each folder is for. Both are in the playbook from the new hire's first day. Recall puts the matching decisions and rules in front of every prompt, so their agent works the team's way from the first task. It only knows what the team recorded: unwritten habits stay unwritten.

Also asked as: Why does our new hire's agent keep suggesting patterns we dropped months ago? · How do I onboard a new developer's AI agent to our codebase? · Can a new engineer's AI agent know our team's past decisions?

The work

Team decisions recorded with arcroom decide are in the playbook from day one.

ArcRoom keeps
  • Code map
  • Decision
  • Recall
The next agent gets

Decision (Jul 14): state in React Query only, no Redux. Why: one cache, fewer bugs.

Step by step

  1. Team decisions recorded with arcroom decide are in the playbook from day one.
  2. Rules explain what each folder is for.
  3. Recall puts the matching decisions and notes in front of every prompt, so the agent works the team's way from the first task.

What the agent sees

Decision (Jul 14): state in React Query only, no Redux. Why: one cache, fewer bugs.
Code map: packages/api — tRPC only; the REST layer was removed in June.

Compared with today's tools

CLAUDE.md + AGENTS.md in the repo

Keep a "we don't use" list (Redux, the old REST layer, a second ORM) in rule files checked into the repo.

Setup
30 min
Ongoing
maintain two files and review changes in PRs

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min per person (npx arcroom init)
Ongoing
None

Repo rule files are the right home for firm rules and simpler; ArcRoom adds the answers and decisions the team built up in other sessions.

Where it stops

Only knows what the team recorded. Unwritten habits stay unwritten.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in small teams