SERVICE 03
Developer Enablement
Turn your engineering org into a Claude Code org.
# CLAUDE.md — project-level context for Claude Code
## Stack
- Node 22, TypeScript, Postgres 16, Redis 7
## Commit conventions
feat:, fix:, chore: — conventional commits, no emoji
## Never touch
- /db/migrations (always ask before modifying)
- .env files (use 1Password references only)
## Custom commands
/review-pr, /run-evals, /deploy-staging
# .claude/rules/testing.md — path-scoped, loads only for test files
---
paths: ["**/*.test.ts", "**/*.spec.ts"]
---
Use vitest. No snapshot tests. Mock at the module boundary.What it is
Claude Code is a force multiplier — but only if it matches how your team actually works. Default Claude Code ignores your conventions, doesn't know your architecture, and surfaces the wrong tools for your stack. The gap between "installed" and "productive" is configuration.
We run structured enablement engagements: audit your workflows, design the CLAUDE.md hierarchy, add path-scoped rules that load conventions only where they apply (API handlers, test files, infra code), ship Agent Skills and custom slash commands for the highest-frequency tasks, wire up MCP servers for your internal tools, and lock down plan mode, permissions, and hooks to match your security posture. Workshops and async support cover teams of 10 to 500 engineers, with a 30-day support window on your shared Slack.
What you get
- 01 CLAUDE.md hierarchy Project- and directory-level configuration encoding your stack, conventions, and off-limits paths — plus path-scoped rules that only load where they apply.
- 02 Agent Skills & slash commands Reusable skills and commands for your highest-frequency tasks — PR review, migration generation, deploy workflows.
- 03 MCP tool integration Claude Code wired to your internal APIs, docs systems, and CI/CD pipelines through typed MCP servers.
- 04 Plan mode, permissions, hooks Fine-grained tool permissions, plan-mode defaults, and lifecycle hooks that match your security posture.
- 05 Team training Hands-on workshops covering effective prompting, context management, plan mode, and Agent Skills authoring.
- 06 Rollout playbook Phased adoption plan for 10–500 engineers, with a feedback loop and async support for the first 30 days.
How we engage
A process designed for production.
Workflow audit
We shadow your engineering workflow — pull request cycles, code review, common tasks, and the tooling you're already using.
Configuration design
CLAUDE.md hierarchy, Agent Skills library, slash commands, and MCP integrations designed against the audit findings.
Build & pilot
Implementation with a pilot cohort of 2–4 engineers who stress-test the configuration against real work before team-wide rollout.
Train & hand off
Team workshop, documentation, and a 30-day async support window on your shared Slack to handle questions and iterate on the config.
Tech stack
Ready to build something that actually works?
We start every engagement with a two-week discovery sprint. No retainer required. You walk away with a spec whether you build with us or not.
Start a project →