# Roadmap

This page captures sensible next steps for the package without over-expanding its scope.

## Near-term improvements

- Expand example coverage for links, toggles, and card-like surfaces
- Add more documentation around semantic usage patterns
- Add package badges and npm usage guidance after publish
- Add visual regression snapshots if the package grows in complexity

## Possible future enhancements

- Additional documented size profiles if demand is real
- More formal migration notes for token evolution
- Optional companion examples for React, Vue, and Svelte integrations
- Theme recipe examples for light, dark, and brand-accent variants

## Guardrails for future work

The package should remain:

- small
- framework-agnostic
- accessibility-forward
- token-driven
- focused on interaction surfaces rather than becoming a full utility framework

## What should probably stay out

- large bundles of unrelated helper classes
- framework-specific wrappers in the main package
- brittle visual flourishes that reduce accessibility or predictability