Claude skills for agencies: one standard across many client projects
Agencies juggle many codebases with different styles. How skills let a team carry its own standards into every project while respecting each client's system.
An agency's problem is the opposite of a product team's. The team is constant and the codebases keep changing. Skills let the constant part, how you work, travel with the people.
| Kind of skill | Where it lives |
|---|---|
| Agency standards: review, handover docs, release notes | Every developer's personal skills |
| A client's design system | That client's repo, in .claude/skills/ |
| A client's domain rules | That client's repo |
Precedence, stated once
Say in the agency skills that a project's own design system wins. Without that line, two skills may compete on every styling request, as in two skills wanting the same prompt.
Turning a client's guidelines into a skill follows give Claude Code your design system as a skill; rolling it out to the team follows sharing skills with a team.
Questions
Should an agency's skills be personal or per project?
Both. Put the agency's house standards in personal or shared skills everyone installs, and each client's design system in that client's repository.
How do we stop our house style overriding a client's?
Make the client's design skill specific to that project and say in the house skill that a project's own design system takes precedence.
Can a skill capture a client's brand guidelines?
Yes, if the guidelines can be written as tokens and checkable rules. That is the same shape as any design system skill.