ngCorex is a deterministic, governance-first design token engine and utility CSS generator.
It is built for enterprise-scale systems that require:
- Strong token constraints
- Predictable output
- Build-time processing
- Clear architectural boundaries
ngCorex is not a component library. It is not a runtime styling framework. It is not CSS-in-JS.
All processing happens at build time.
ngCorex is structured as a layered ecosystem:
@ngcorex/css
Build-time token normalization, validation, and CSS variable generation.
Includes CLI commands:
ngcorex init
ngcorex build@ngcorex/angular
Angular CLI adapter that provides:
npx ng add @ngcorex/angularThis integration:
- Adds
@ngcorex/cssas a devDependency - Adds CLI scripts
- Injects generated CSS into
angular.json - Keeps all processing build-time
No runtime logic is introduced.
npx ng add @ngcorex/angular
npm run ngcorex:dev
ng serveThe ngcorex:dev command automatically:
- Creates
tokens.jsonandngcorex.config.ts - Generates initial CSS
- Watches for changes and auto-rebuilds
Alternative: After running
ng add, you can usenpm run ngcorex:setupfor a one-time setup, thennpm run ngcorex:watchin a separate terminal for automatic rebuilds during development.
ngCorex is:
- Deterministic
- Constraint-driven
- Governance-first
- Build-time only
- Framework-agnostic at its core
The Angular adapter exists only to reinforce workflow — not to alter architecture.
Dependency direction:
Angular Project
↓
@ngcorex/angular
↓
@ngcorex/css
The core engine never depends on Angular.
Full documentation:
https://ngcorex-docs.vercel.app
ngCorex follows semantic versioning.
Angular adapter minor version aligns with core minor version to guarantee compatibility.
Example:
@ngcorex/css@0.2.x
@ngcorex/angular@0.2.x
- Core governance expansion
- Constraint tooling
- Visualization tooling
- Enterprise governance layer (private)
MIT