← all projects

Shared rules for coding agents

Internal team tooling

Instead of making Codex or Claude rediscover each repository, we give them the project rules, bounded MCP tools, and checks they must run.

AGENT / REVIEW
Explanatory workflow from repository context and system design through implementation, checks, and human reviewAn original interface concept, not a production screenshot. All displayed content is illustrative.AMAGENTS / WORKFLOW EDITORStudyContext in. Reviewed code out.Human reviewProject contextAGENTS.md / rulesDesign skillShared system decisionsCoding agentCodex / ClaudeChecks & reviewTYPECHECK / LINT / E2EMCP toolsTools with project contextsystem-design / SKILL.mdProject rules travel with the task.An engineer approves the result.INTERFACE CONCEPT · ILLUSTRATIVE CONTENT ONLY↗
Project workflow diagram.

The workflow

I build shared project skills and rules that give Codex and Claude the context they need to work across our repositories. The same guidance explains the project conventions, the tools available for a task, and the checks expected before review.

Tools and review

I use bounded MCP tools alongside the project instructions so an agent can work within a clear task scope. Type checks, linting, end-to-end checks, and human review remain part of the workflow.

Why it helps

A shared approach makes agent-assisted work easier to start, inspect, and review across different projects. The tools can change while the repository rules and quality checks stay familiar to the team.

Next project: Web application firewall management →