krds-onboarding

To set up a KRDS design system project, you need an automated onboarding workflow that validates your environment, installs required UI assets like CSS tokens and HTML snippets, and classifies your institutional type. This ensures immediate compliance with government design standards.

The KRDS workflow for public institutions involves environment validation, institutional type selection, and sequential progression through style, components, patterns, verification, and licensing skills. Following this orchestrated sequence ensures full regulatory compliance for government digital services.

Yes, installing krds-uiux is a mandatory prerequisite for KRDS onboarding. The onboarding process validates this dependency to properly bootstrap your environment with essential design assets including HTML snippets, CSS tokens, icons, and fonts.

Institutional classification determines the specific KRDS application type for local governments, central administrations, or public institutions. This guided classification sets up tailored follow-on steps to ensure the design system matches your exact governmental context and requirements.

The KRDS environment bootstrap automatically validates and prepares HTML snippets, CSS tokens, icons, fonts, and CDN resources from krds-uiux. These assets are extracted and configured for immediate use in your government web project.

KRDS verification and licensing skills run as downstream steps after environment setup and component implementation. They should be executed sequentially after patterns are applied to ensure final compliance before delivering your government website project.