What problem does it solve?
Working with zard/ui requires knowing the real component APIs, the project configuration in components.json, and the correct CLI commands — guessing inputs or import paths is the most common failure mode. This Skill grounds every action in the actual project configuration, the published registry, and the component documentation instead of remembered APIs.
Core Features & Use Cases
- Project-aware component management: Reads components.json to resolve aliases, project type (angular, nx, analog, libraries), icon family, and package manager before running zard-cli init or add.
- Real API access: Uses the registry index, published Markdown docs, and the zard-mcp server (list-components, get-component-docs, install-component) so code is written against the actual component API.
- Enforced conventions: Applies zard/ui rules for standalone OnPush components, signal inputs, semantic Tailwind v4 tokens, CVA variants, composition patterns, forms, icons, and typeset prose styling.
- Use Case: A developer asks to add a settings page to an Nx workspace — the Skill reads components.json, confirms which components are installed, adds card/field/input/button via npx zard-cli add, and composes the page using z-card, z-field-group, and variant inputs rather than custom markup.
Quick Start
Ask the assistant to set up zard/ui in your Angular project and add a button and card component using the project's package manager.