Skills, not docs

Second in a series on using @relax.js/core with a coding agent. The first piece made the argument; this one is about the first thing you do in a project. Install the rules, not the manual npx @relax.js/core init-agents That writes seven files into .claude/skills/, one per area: the core model, then templates, forms, routing, services, testing and setup. Claude Code loads a skill when its description matches what the agent is doing. Other tools without skill support can be pointed at node_modules/@relax.js/core/skills/relaxjs/SKILL.md from their instruction file; the core skill links to the rest. Each copy is stamped with the package version it came from. Run the command again after an upgrade and it lists the copies that are behind, and leaves them alone unless you pass --force. A skill is a snapshot, and a snapshot that describes an older library is worse than none, because the agent trusts it. The border The interesting decision was not to write the