Six months of accumulated Claude Code configuration — 50 skills, 50 subagents, 40 commands, hooks, rules, and the sync pipeline that pushes all of it to a public GitHub mirror with a fail-closed two-tier audit. What's inside, why I built it, and the workflow philosophy behind it.

AX-skills is the public mirror of my personal Claude Code skills directory — eleven workflows for writing, research, image generation, knowledge sync, and one cyber half-immortal divination skill. After a year of writing them, I think a skill isn't a stored prompt — it's how you encode care.

先是裸跑 Claude Code。再是 GSD 多 agent 仪式。再是 superpowers 的 skill 库。最后在上面包了一个自己的 orchestrator。每一版崩盘都来自一个具体 session。最后我才想明白：solo dev 的 harness 跟团队的不是一个物种，而且真正的答案不是选一个默认引擎——是按工作形状路由。

Vanilla Claude Code. Then GSD's multi-agent ceremony. Then superpowers' skill system. Then a custom orchestrator on top. Each rewrite came from a specific session that broke. What I learned: solo dev harnesses and team harnesses are different species, and the right answer isn't a default engine — it's routing by work shape.

一个 Claude Code session 里同时跑了三种协作模式：直接结对编程（用户反馈驱动三次生产部署）、后台 agent 并发更新文档、自治审查团队迭代三轮直到零问题——全部交叠进行。传统的 code-test-review-release 流水线被压缩成了并行流。

A single Claude Code session that combined direct pair programming (three production deploys from user feedback), a background docs agent running concurrently, and an autonomous review team iterating three rounds until clean — all overlapping. The traditional code-test-review-release pipeline collapsed into parallel streams.