-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Labels
enhancementNew feature or requestNew feature or request
Description
Overview
Extend size profiles to support platform-specific variations, preparing for RFC #624 multi-platform architecture.
Context
RFC #624 proposes hierarchical token architecture: Foundation → Platform → Product. Component schemas should support platform-specific profiles and overrides.
Goals
- Platform-specific size profiles
- Platform-specific anatomy parts
- Override mechanisms
- Inheritance model
Tasks
-
Extend size profile schema
- Add platform field (
web,ios,android,desktop) - Support platform-specific overrides
- Define inheritance rules (foundation → platform)
- Version platform profiles independently
- Add platform field (
-
Update component schema
- Support platform-specific
tokenNaming - Platform-specific anatomy arrays
- Platform-specific property mappings
- Fallback to foundation if platform not specified
- Support platform-specific
-
Build platform selector UI
- Toggle between platforms in tool
- Show platform-specific vs shared values
- Highlight overrides
- Compare platforms side-by-side
-
Add platform validation
- Validate platform-specific profiles exist
- Check inheritance chain
- Warn about divergence from foundation
- Suggest consolidation opportunities
-
Add platform migration tools
- Convert existing profiles to multi-platform
- Split shared profiles into foundation + platform
- Bulk apply platform-specific overrides
-
Document platform patterns
- When to use platform-specific profiles
- How to override foundation values
- Platform naming conventions
- Examples for each platform
Success Criteria
- Size profiles support 4 platforms (web, iOS, Android, desktop)
- Tool can display and edit platform-specific values
- Foundation profiles reused across platforms
- Clear documentation for platform extensibility
Dependencies
- [Epic] v1 MVP: Schema Foundation for Token Mapping #647 (Schema Foundation)
- RFC [DRAFT RFC] Token Structure Changes for Multi-Platform Support #624 design decisions
Estimated Effort
3-4 weeks
Related
- RFC [DRAFT RFC] Token Structure Changes for Multi-Platform Support #624: Multi-Platform Support
- RFC Context Summary
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request