An interface core without a UI kit
Shared tokens and validation rules can travel between projects without forcing every project to look the same.
Reusing interface foundations should not mean reusing the same page composition. A brand-specific portfolio, a dense dashboard and a creative tool may share token rules while needing completely different layouts.
Define contracts, not appearances.
PFx Interface Core validates and resolves design tokens, composes mode overrides and compiles machine-readable foundations into CSS. Style Dictionary is the transformation engine behind the compiler boundary. The system does not prescribe navigation, hero composition, cards or motion choreography.
A common foundation, different results.
The repository validates the same public API against different consumer scenarios: an expressive site and a compact dashboard. That is a more useful test than expecting a shared set of components to produce one recognizable visual style.
This core is a private, unpublished package in active development, rather than a stable design-system release. The intended boundary is clear: shared rules are reusable; the consuming project remains responsible for its identity.