VelinStyle Core Features vs Compat/Migrate 1.4.0
A strict separation between native Core Features and the Tailwind migration product line.
Product boundary: Core Features are Velin-native. They do not extend Tailwind Compat/Migrate and do not port Shadcn, Radix, or Tailwind UI.
Different product lines
| Concern | Compat / Migrate | Core Features |
|---|---|---|
| Purpose | Tailwind-to-VelinStyle migration assistance | Native semantic adaptation and owned Blocks |
| Package focus | @birdapi/velinstyle-tailwind, migrate CLI | /adapt, /blocks, /inspector |
| Success measure | Honest mapped coverage and safe dry-runs | Allowlisted adaptation and ownership DX |
| Dependency | Optional for migration projects | No Tailwind/Compat dependency |
Velin Blocks are not ports
| Not provided | Provided |
|---|---|
| Shadcn file conversion | Velin-native HTML/CSS/JS source |
| Radix primitive reimplementation | Existing Velin Web Components where useful |
| Tailwind utility dependency | @birdapi/velinstyle peer |
| Opaque hosted widgets | Source copied into and owned by the project |
Operational rule
Keep migration flags, coverage reports, and roadmaps separate from Adapt and Blocks. Neither line unlocks capabilities in the other.
Continue
- Core Features architecture — module and data-flow boundaries
- Tailwind Migrate — the separate migration track
- Tailwind Compat — the compatibility package