Team Workflow OS — shared clarc setup for engineering teams. Covers shared rules distribution, private skill packs, team sync patterns, onboarding, and multi-developer conventions.
From clarcnpx claudepluginhub marvinrichter/clarc --plugin clarcThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Patterns and workflows for running clarc as a shared engineering team OS — consistent rules, private skill packs, and synchronized conventions across all developers.
/team-synccompany-clarc private repository to house organization-specific rules and skills# Team lead: create private rules + skills
mkdir -p ~/.company/private-rules ~/.company/private-skills
# Install for all team members via shared command
./install.sh --team-mode \
--company-prefix yourco \ # replace with your company/team prefix
--private-rules ~/.company/private-rules \
--private-skills ~/.company/private-skills \
typescript
# Each developer runs the same command
# → ~/.claude/rules/yourco/ (private rules)
# → ~/.claude/skills/yourco/ (private skills)
Recommended: Store team config in a private git repo:
company-clarc/
├── install-team.sh # wrapper: calls clarc install.sh + team flags
├── private-rules/
│ ├── api-standards.md # company API conventions
│ ├── security-policy.md # internal security requirements
│ └── code-review.md # review checklist
├── private-skills/
│ ├── deploy-flow/SKILL.md # company-specific deploy workflow
│ └── pr-process/SKILL.md # internal PR process
└── README.md
install-team.sh:
#!/usr/bin/env bash
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
CLARC_DIR="${HOME}/.clarc"
if [[ ! -d "$CLARC_DIR" ]]; then
git clone https://github.com/marvinrichter/clarc.git "$CLARC_DIR"
fi
bash "$CLARC_DIR/install.sh" \
--team-mode \
--company-prefix yourco \
--private-rules "$SCRIPT_DIR/private-rules" \
--private-skills "$SCRIPT_DIR/private-skills" \
"$@"
New developer onboarding:
git clone git@github.com:yourco/company-clarc.git
cd company-clarc && ./install-team.sh typescript
Private rules follow the same format as clarc rules:
private-rules/
├── api-standards.md # REST/GraphQL API conventions
├── security-policy.md # Security requirements specific to company
├── code-review.md # Custom review checklist
├── deployment.md # Deployment process
└── incident-response.md # On-call and incident protocols
Each file is a plain Markdown file. Claude loads them from ~/.claude/rules/<prefix>/ automatically.
Private skills use the standard clarc SKILL.md format:
private-skills/
├── deploy-flow/
│ └── SKILL.md # "How to deploy at Acme"
├── feature-flags/
│ └── SKILL.md # "Company feature flag process"
└── data-access/
└── SKILL.md # "Internal data access patterns"
Run /team-sync to:
cd ~/.clarc && git pullcd ~/company-clarc && git pullAdd to the project CLAUDE.md:
## Team clarc Setup
This project uses company-clarc. Install with:
cd ~/company-clarc && ./install-team.sh typescript
Team rules are in `~/.claude/rules/yourco/`:
- api-standards.md — REST API conventions
- security-policy.md — security requirements
Private skills available: /deploy-flow, /pr-process
~/.claude/rules/yourco/[ ] Clone company-clarc
[ ] Run ./install-team.sh <language>
[ ] Verify: ls ~/.claude/rules/yourco/
[ ] Verify: ls ~/.claude/agents/ (should list 50+ agents)
[ ] Read CLAUDE.md in the project repository
[ ] Enable Memory Bank: mkdir .clarc (in project root)
[ ] Test: open Claude Code, run /doctor