My team wants to adopt a shared set of skills in our codebase: design rules, reusable component references, copy guidelines, etc. Currently, we've kept .claude/skills in .gitignore, since devs constantly tinker with their own set of skills, and we want to keep encouraging that. So, if we remove it from .gitignore, everyone gets the shared skills automatically- but doing so pulls in everyone's half-finished, personal, or irrelevant experiments into the shared codebase.
How have other teams solved this? It's feeling like a combination of technical solution but also communication: keep your dirty skills outside of commits. Would love to hear what's actually worked!
Comments URL: [https://news.ycombinator.com/item?id=48737209](https://news.ycombinator.com/item?id=48737209)
Points: 1
source & further reading
news.ycombinator.com — original article
Ask HN: You have model orders of magnitudes faster than transformer, so?
Ask HN: How to Stay Marketable in the AI Era?
Ask HN: What agent skills are necessary?