npx skills add https://github.com/owl-listener/designer-skills
infrasity-labs/dev-gtm-claude-skills
version-control-strategy
Define version control strategies for design files, components, and libraries.
Installation
$
npx skills add infrasity-labs/dev-gtm-claude-skills --skill version-control-strategy
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
version-control-strategy
Linked neighbor
owl-listener/designer-skills
Define version control for design files, components, and libraries — branching, naming, and rel…
1.4K installs
frontend-design
Same topic
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installs
agent-browser
Same topic
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installs
vercel-react-best-practices
Same topic
vercel-labs/agent-skills
697.8K installs
web-design-guidelines
Same topic
vercel-labs/agent-skills
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installs
microsoft-foundry
Same topic
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsAlso in this package
Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.
npx skills add infrasity-labs/dev-gtm-claude-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude Code
Not declared
Cursor
Not declared
Codex
Not declared
GitHub Copilot
Not declared
Windsurf
Not declared
Gemini CLI
Not declared
Cline
Not declared
OpenCode
Not declared
Also listed on
Alternate registries and mirrors of this skill.
Repository health
Stars
123
License
LICENSE
Default branch
main
Open issues
0
Status
Active
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,723 B -
docs
SUMMARY.md110 B
History
- First seen on skills.sh
- First recorded snapshot · 54 installs
SKILL.md
Version Control Strategy
You are an expert in managing design file versions, component libraries, and design assets.
What You Do
You define strategies for versioning design work so teams can collaborate, track changes, and maintain consistency.
What to Version
- Design files (Figma, Sketch, etc.)
- Component libraries
- Design tokens
- Icon sets and assets
- Documentation
Versioning Approaches
Design Files
- Named versions at key milestones (v1-exploration, v2-refinement, v3-final)
- Branch-based: main branch for approved, feature branches for work-in-progress
- Page-based: version history within the file using pages
Component Libraries
- Semantic versioning (major.minor.patch)
- Major: breaking changes (renamed components, removed props)
- Minor: new components or features (backward compatible)
- Patch: bug fixes and refinements
Design Tokens
- Version alongside the component library
- Changelog documenting token additions, changes, removals
- Migration guides for breaking changes
Branching Strategy
- Main: production-ready, approved designs
- Feature branches: work-in-progress designs
- Review process before merging to main
- Archive old versions, don't delete
Changelog Practices
- Document what changed and why
- Link to relevant design decisions
- Note breaking changes prominently
- Include migration instructions
Best Practices
- Version at meaningful milestones, not every save
- Name versions descriptively
- Keep a changelog
- Communicate changes to consumers (developers, other designers)
- Archive rather than delete old versions