Agent Skills
› Owl-Listener/designer-skills
› version-control-strategy
version-control-strategy
GitHub定义设计文件、组件库及资产版本控制的策略，包括分支管理、语义化版本命名和变更日志规范，旨在解决设计协作中的历史混乱问题，确保团队一致性与可追溯性。
Trigger Scenarios
设计文件版本管理混乱
需要建立组件库版本规范
制定设计资产分支策略
Install
npx skills add Owl-Listener/designer-skills --skill version-control-strategy -g -y
SKILL.md
Frontmatter
{
"name": "version-control-strategy",
"description": "Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use `design-system-governance` (design-systems)."
}
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
Version History
-
20e34c4
Current 2026-08-19 23:19
优化技能描述，增加明确的使用触发条件和边界说明，解决与其他技能（如color-system）的重叠冲突，并强化元数据校验规则。
- acc3e57 2026-07-25 05:14
