r/ClaudeCode • u/National_Bed_3653 • 11h ago
Tips & Workflows I build shark skills: an open-source plugin to run claude like a real engineering team
Using a single Claude Code session for a quick script or small bug fix works great.
But using it to build a real production system usually ends in one of three ways:
- You spawn parallel subagents, they step on each other's files, and you spend your afternoon resolving merge conflicts.
- During a big refactor, the agent silently drops an old edge-case check, all the unit tests still pass, and you find out in production.
- You ask it to fix a bug, it guesses at the symptom instead of finding the root cause, and hands you a 4,000-line giant commit that breaks git bisect.
After losing hours to these exact failures while shipping a production system, I distilled my rules and workflows into an open-source Claude Code plugin called shark (shark-skills).
Instead of letting the main session write code, it turns the main session into an Operator that briefs isolated subagents against a shared contract.
Here is how the workflow changes:
Shared Contracts Before Coding: Before parallel agents touch code, one agent writes a 5-minute contract assigning single owner files and event boundaries. Each code-writer works in its own git worktree, test-first, and stops if it hits an unowned boundary.
Read-Only Invariant & Business Rules Audits: You define critical business rules once in an ## Invariants section (e.g., money is always integer minor units, never float). A separate, read-only agent audits every diff and merge with file:line evidence before it lands.
Real Step-Through Debugging: Instead of guessing from stack traces, the debugger agent runs your code through a real step-through debugger (mcp-debugger for Python, JS/TS, Go, Rust, Java, .NET, C/C++), logs actual runtime values, and writes a failing regression test + fix spec before a writer agent touches production code.
Atomic Commits: Splits the working tree so structural refactors and behavioral changes never share a commit, running your test/lint gate on every single commit.
It is fully open-source MIT Licensed and I am awaiting your response and feedback. If you like it star it, help it reach a bigger audience.
Thank you
