Skip to content

docs(AGENTS): add Figma design system minimum criteria#93

Open
seonghobae with Copilot wants to merge 1 commit into
masterfrom
copilot/task-295022177-102973287-331a969f-e64a-48ce-8374-cf9791c16331
Open

docs(AGENTS): add Figma design system minimum criteria#93
seonghobae with Copilot wants to merge 1 commit into
masterfrom
copilot/task-295022177-102973287-331a969f-e64a-48ce-8374-cf9791c16331

Conversation

Copilot AI commented Jul 2, 2026

Copy link
Copy Markdown

Defines what qualifies a Figma file to be called a "design system" per KRDS standards — having only some components is insufficient.

Added to AGENTS.md

  • 10 required criteria to use the "design system" label:

    1. Defined purpose, scope, and target audience
    2. Systematized Foundation (color, typography, shape, layout, icon, elevation)
    3. Three-tier design token structure (primitive → semantic → component)
    4. Component library with variant/state/property/accessibility per component
    5. Variant, State, Property system
    6. Basic patterns (task-level component compositions)
    7. Service patterns / user-journey templates
    8. Accessibility & digital inclusion criteria at design stage
    9. Documentation and usage guides inside Figma
    10. Code mapping (Figma component ↔ dev component, token ↔ variable)
  • When to downgrade the label to "UI Kit / Figma Library / Component Draft" — e.g., arbitrary color values, no tokens/variables, missing states, no accessibility baseline, no dev mapping

  • Definition of Done checklist — 11 items that must all be satisfied before the "design system" name applies

Copilot AI changed the title [Figma] 디자인 시스템 명칭 사용을 위한 최소 구성요소 및 작업 기준 정의 docs(AGENTS): add Figma design system minimum criteria Jul 2, 2026
Copilot AI requested a review from seonghobae July 2, 2026 07:13
@seonghobae seonghobae marked this pull request as ready for review July 2, 2026 07:37
Copilot AI review requested due to automatic review settings July 2, 2026 07:37

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot couldn't run its full agentic review because no GitHub Actions runner was available. Make sure your repository has a runner available to run Copilot's review, or add a copilot-setup-steps.yml file specifying one with the runs-on attribute. See the docs for more details.

Adds KRDS-aligned minimum criteria for when a Figma file can be labeled a “design system,” clarifying required foundations, token structure, component/pattern expectations, accessibility, documentation, and dev mapping.

Changes:

  • Documents 10 minimum criteria for using the “design system” label in Figma deliverables.
  • Adds guidance on when to downgrade the label (UI Kit / Library / Draft) and an explicit Definition of Done checklist.
  • Includes supporting KRDS/Figma references via footnotes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread AGENTS.md
Comment on lines +74 to +81
| 구분 | 있어야 하는 내용 |
| ------ | -------------------------------------------------- |
| 색상 | 색상 팔레트, 주요 색상, 시스템 색상, 강조 색상, 상태 색상, 대비 기준, 사용 가이드 |
| 타이포그래피 | 서체, 굵기, 크기, 줄 간격, 글자 스케일, 계층 구조, 접근성 기준 |
| 형태 | radius 값, 형태 원칙, 적용 기준 |
| 레이아웃 | 그리드, 브레이크포인트, 콘텐츠 영역, 간격 체계, 반응형 기준 |
| 아이콘 | 시스템 아이콘, 크기, 키라인, 두께, 색상, 사용 기준 |
| 엘리베이션 | 그림자, 경계선, 딤드 처리, 레이어 위계, 적용 기준 |
Comment thread AGENTS.md

KRDS는 디자인 시스템을 단순한 화면 시안이나 UI 컴포넌트 묶음이 아니라, **편의성·일관성·접근성·사용성 보장**과 **표준화된 UX/UI 제공**을 목적으로 하는 체계로 설명한다. 또한 KRDS 디자인 시스템은 "규칙, 원칙, 컴포넌트, 스타일 가이드, 패턴 및 도구들의 모음"으로 정의되어 있으므로, Figma 파일에 일부 컴포넌트만 존재하는 상태를 곧바로 "디자인 시스템"이라고 부르는 것은 부정확하다. ([KRDS][1])

따라서 본 이슈에서는 Figma 작업물이 **디자인 시스템**이라는 명칭을 사용하기 위해 기본적으로 갖춰야 할 사항을 아래와 같이 정의한다.
Comment thread AGENTS.md
Comment on lines +249 to +251
[5]: https://www.krds.go.kr/html/site/component/component_summary.html "공식 배너 (Masthead) | 컴포넌트 - KRDS"
[7]: https://help.figma.com/hc/en-us/articles/360056440594-Create-and-use-variants "Create and use variants"
[8]: https://help.figma.com/hc/en-us/articles/360061175334-Create-interactive-components-with-variants "Create interactive components with variants"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants