Practical Notes
- Setup time ~10 minutes (clone + locate the implemented
.claude/examples) - One concrete demo included:
/weather-orchestratorworkflow in.claude/commands/ - GitHub stars + forks (verified): see Source & Thanks
Treat this repo like an internal engineering handbook:
- Start by reading the implemented docs (not just theory).
- Pick one pattern (e.g., commands + subagents + skills), then copy the minimal files into a real project.
- Turn the pattern into a team habit: keep everything in version control, review changes in PRs, and require explicit guardrails for risky operations.
If you already use multiple agents in parallel, use the repo as a checklist: consistent .claude/ structure, hooks for formatting/tests, and a small set of shared commands the whole team relies on.
FAQ
Q: Is this a tool or a reference repo? A: Primarily a reference repo with implemented examples you can copy into projects.
Q: What should I try first?
A: Run the /weather-orchestrator workflow to understand the command → agent → skill pattern.
Q: How do I keep practices from drifting?
A: Version-control your .claude/ assets and review changes in PRs like code.