Ask HN: How do you share /skills across your dev team?
A developer asks how to share a common set of AI skills (design rules, component references, copy guidelines) across a team without pulling in individuals' personal or experimental skills. They seek solutions beyond simply .gitignore, ideally combining technical separation with team communication norms.
Background
- **.claude/skills** is a directory used by Claude Code (Anthropic's CLI coding agent). It stores "skills" — reusable prompts, design rules, style guides, and conventions that the AI reads to align with a team's coding practices.
- **.gitignore** is a Git config file that tells the version control system to ignore certain files/directories. Putting `.claude/skills` there means each developer's personal skills file stays on their machine and never gets committed to the shared repository.
- The dilemma: the team wants to *share* official skills (e.g. "use our Button component, not raw `<button>`") via the codebase, but currently can't because the whole folder is ignored. If they un-ignore it, everyone's personal experiments and half-baked skills get pushed into the repo too.
- This is a narrow but practical workflow problem for teams adopting AI-assisted coding tools — how to separate personal AI config from team-wide standards in a way that Git handles cleanly.