Put project knowledge in the right place
CLAUDE.md contains persistent project conventions. Skills describe reusable tasks, while MCP connects additional systems. These components solve different problems. The team file should explain how to build and verify the project, its architectural boundaries and who approves changes to critical modules.
Back instructions with technical checks
A written rule is not an access control. Hooks can execute defined steps on lifecycle events; permissions and repository protection also need to fit. Formatting after edits and required CI checks are a useful starting point. Review hooks as source code because even a validation script can contain unwanted access or network calls.
Assign bounded work with visible acceptance
Instead of asking it to modernize an application, give the first pilot a reproducible bug, an expected state and a bounded change area. The agent works on its own branch. The review explains the problem, change, checks performed and remaining limits. A second person closely reviews authentication, payments and data migrations.
Measure team benefit rather than generated lines
Track review time, rework, failed builds and reopened defects during adoption. A fast first draft can cost more overall if the team spends a long time correcting it. Several comparable tasks provide evidence for improving skills and adjusting access to real needs. Success means a steadier development process, not more unreviewed code.
Keep it verifiable
Primary sources
- Extend Claude CodeSource checked:
- Claude Code project memorySource checked:
- Automate workflows with hooksSource checked:
- Configure Claude Code permissionsSource checked:
