Skill1.5k estrellas del repoactualizado yesterday

version-control-strategy

The version-control-strategy skill guides design teams in establishing systematic approaches for managing design file versions, component libraries, design tokens, and related assets. Use this when establishing workflows for tracking changes across design systems, coordinating collaborative design work, or ensuring design consistency and traceability in larger organizations.

Ver fuente Repositorio: designer-skills

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/version-control-strategy && cp -r /tmp/version-control-strategy/design-ops/skills/version-control-strategy ~/.claude/skills/version-control-strategy

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

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

Del mismo repositorio

design-critiqueSkill

Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.

design-debt-auditSkill

Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.

design-impact-reportingSkill

Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.

design-qa-checklistSkill

Create QA checklists for verifying design implementation accuracy.

design-review-processSkill

Establish design review gates with criteria, checklists, and approval workflows.

design-sprint-planSkill

Plan and facilitate design sprints from challenge framing through prototype testing.

handoff-specSkill

Create developer handoff specifications with measurements, behaviors, assets, and edge cases.

team-workflowSkill

Design team workflows covering task management, collaboration rituals, and tooling.