Shared rules and skills for AI coding tools
We maintain our AI coding rules, skills, and workflows in one repository, then generate the files each client needs. It saves copying and updating them by hand.
We want to edit a rule once and use it in each of our coding tools.
01 / Context
Claude, Codex, Cursor, and Gemini use different directories and formats. After a few manual copies, it becomes hard to tell which version is current or whether an install will overwrite local edits.
What we built
A single set of source files now feeds each client. Manifests determine what gets generated, installs can be previewed, and change records support inspection and rollback.
02 / System
Rules, skills, agents, commands, and hooks are maintained in the capabilities and workflows directories.
Manifests list the content, install profiles, and target clients. The generator writes files in the corresponding formats.
Checks cover formats, links, and generated files. The installer previews changes and records which files it wrote so later cleanup can identify them.
03 / Decisions
Edits go into the source files and regenerate targets, keeping client copies in sync.
Profiles such as core, quality, and frontend let us install the tools we need for a task.
04 / Our work
Role：We designed and built the repository structure, generators, installation flow, and checks.
