krds-components

Deliver ready-made KRDS UI components with HTML snippets and ARIA semantics.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/JiminLee-way/Awsome-KRDS-KoreaDesignSystem --skill krds-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: krds-components
Source: https://github.com/JiminLee-way/Awsome-KRDS-KoreaDesignSystem/tree/main/plugins/krds/skills/krds-components
Command: npx skills add https://github.com/JiminLee-way/Awsome-KRDS-KoreaDesignSystem --skill krds-components

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

KRDS components provide ready-made UI building blocks and reference materials to ensure government digital services implement consistent, accessible interfaces with reduced design-to-development gaps.

Core Features & Use Cases

  • 74 HTML code snippets for UI patterns and 43 UI components with KRDS naming conventions.
  • Centralized design tokens, tokens in CSS, ARIA guidelines, and comprehensive reference files to accelerate development.
  • Use Case: A government portal implements a consistent search, navigation, and form UI using the provided KRDS assets and references.

Quick Start

Use the KRDS HTML snippets from html/code and apply the KRDS tokens to ensure accessibility and consistency.

Frequently Asked Questions about krds-components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are KRDS UI components and how do they support government digital services?

KRDS UI components are ready-made building blocks for government digital services, providing consistent and accessible interfaces. They include 43 UI components and 74 HTML snippets with proper ARIA semantics to reduce design-to-development gaps.

How do I build accessible government interfaces using KRDS design tokens and HTML snippets?

To build accessible government interfaces, apply the provided KRDS HTML snippets and centralized design tokens to your frontend. This ensures responsive behavior and proper ARIA semantics for UI patterns like buttons, inputs, and navigation.

Can I use KRDS components for frontend forms, search, and navigation UI?

Yes, you can use KRDS components for frontend forms, search, and navigation UI. The package delivers ready-made components with KRDS naming conventions and reference guides to implement consistent, accessible interfaces across your workflow.

Do I need external dependencies to render KRDS UI components?

No external dependencies are required to render KRDS UI components. The package leverages internal HTML code snippets, KRDS tokens, and reference guides to deliver compliant components directly within your frontend design and development workflow.

Why use KRDS design tokens instead of custom CSS for government portals?

Using KRDS design tokens instead of custom CSS ensures accessibility and consistency across government portals. The centralized tokens enforce KRDS naming conventions and compliant ARIA guidelines, reducing the design-to-development gap for digital services.