docs/guides/writing-a-score.md: - Add Design Principles section: capabilities are industry concepts not tools, Scores encapsulate operational complexity, idempotency rules, no execution order dependencies CLAUDE.md: - Add Capability and Score Design Rules section with the swap test: if swapping the underlying tool breaks Scores, the capability boundary is wrong