A CLEAR BRIEF. A BETTER START.
Your next screen.
Start with a foundation.

Choose a screen and copy a design brief grounded in actual blocks, tokens and usage principles.
What are you building?

Actual examples in your brief

READY FOR YOUR AI
Copy it and start building

Markdown
# KLIC Admin & data interfaces

Review the actual KLIC examples and design principles, then propose a screen for my project.

## Purpose
Support work, permission review and data import. Explore working interactions and choose an interface for your task.

## Primary references
- https://design.klic.co.kr/solutions/admin?lang=en
- https://design.klic.co.kr/about?lang=en
- https://design.klic.co.kr/guides/tokens?lang=en
- KLIC motion catalog: https://design.klic.co.kr/api/v1/motions.json
- https://design.klic.co.kr/share/block/support-tickets?lang=en
  DESIGN.md: https://design.klic.co.kr/design/block/support-tickets/DESIGN.md
  contract.json: https://design.klic.co.kr/design/block/support-tickets/contract.json
- https://design.klic.co.kr/share/block/access-permissions-matrix?lang=en
  DESIGN.md: https://design.klic.co.kr/design/block/access-permissions-matrix/DESIGN.md
  contract.json: https://design.klic.co.kr/design/block/access-permissions-matrix/contract.json
- https://design.klic.co.kr/share/block/dialog-bulk-import-csv?lang=en
  DESIGN.md: https://design.klic.co.kr/design/block/dialog-bulk-import-csv/DESIGN.md
  contract.json: https://design.klic.co.kr/design/block/dialog-bulk-import-csv/contract.json

## Design requirements
- 7 dimensions: size, typography, color, layout, spacing, surface, interaction.
- klic.primitive → klic.brand → klic.semantic → klic.component.
- Use blue, navy and neutral surfaces; reference tokens before hardcoding values.
- Make the scope of search, filters and selection visible.
- Confirm the target and recovery path before a bulk change.
- Explain denied access, empty results and input errors separately.
- Include keyboard/focus, loading, empty/error/recovery states, narrow layouts and fit-to-screen previews.
- Use motion only when it helps, respect reduced-motion preferences and provide a static alternative.

## Shared design criteria

Policy revision: 6f9c8f5e4d7c767f79a7db999670fb4d0936e07acb1b472fe162a7a9ade60c97

Canonical policy: https://design.klic.co.kr/api/v1/design-system.json

Read the same criteria and revision in API, CLI, MCP and WebMCP designSystem responses and the bundled KLIC-DESIGN-SYSTEM.json. Item contracts link through item.design.system.

| Dimension | Token responsibility | Structure and behavior responsibility |
| --- | --- | --- |
| Size and proportion | Control sizes, icons and content width | Component recipes and the DOM ensure min-height, padding, wrapping and actual hit areas. |
| Typography | Registered font families, role sizes and weights | Supported recipes define line height, tracking, wrapping and responsive conditions without assuming unregistered token types. |
| Color and contrast | Role colors for actions, selection, text, borders and status | Labels, icons and state attributes convey meaning; measure actual composited-surface contrast separately. |
| Layout and alignment | Registered spatial roles, including maximum content and panel widths | DOM reading order, layout transitions, scroll ownership and Portal structure |
| Spacing and grouping | Internal gaps, padding, group spacing and approved density mappings | Maintain label, fieldset, legend and describedby relationships; window width alone does not change density. |
| Surface and depth | Surface colors, radii, borders and supported color/dimension material leaves | Blur and shadow recipes, stacking, auxiliary-panel versus modal behavior and opaque fallbacks |
| Interaction and feedback | Visual roles for focus, selection, progress, success, warnings and errors | Keyboard operation, focus movement, asynchronous transitions, execution blocking, input preservation and recovery |

Only Primitive owns literals. Preserve adjacent Brand→Primitive, Semantic→Brand and Component→Semantic references.

Distinguish token definitions, structural conditions in DOM/CSS recipes and compiled final literals.

Keep motion recipes in a read-only catalog separate from component and block installation items, with browser search and details in the existing KLIC Interface Library #motion view. The read API, CLI, MCP and WebMCP use one canonical catalog. The scope is all 884 user-supplied source patterns in 67 categories, grouped within the existing KLIC category/item navigation. Remove the previous simplified 280-item catalog and its dedicated routes and aliases; do not retain them as compatibility entries. Preserve source id + pattern identity, source engine, choreography, timing, paths, layers, SVG/inline/WAAPI alpha, and original notices including Copyright © 2026 acc0mplish. All rights reserved. and the supplied license. Never label this source material KLIC-authored. Adapt appearance through existing four-layer KLIC token paths for color, fonts, surfaces, borders, radius and spacing. Canvas uses the same palette and font tokens; scope demo CSS to each item. Use one owned runtime for previews and JavaScript/React delivery; do not claim CSS alone reproduces Canvas playback. KLIC adaptations use the blue/navy/neutral palette and reduced-motion, replay and cleanup contracts; verify real playback in light/dark and mobile before release. The npm package remains separate from the homepage: describe candidate exports only after checking the published manifest, and do not infer release contents from current source.

## Allowed preset scope

A preset combines approved settings of an existing API. It is not a fifth token layer.

Use an explicit allowlist of size, variant, density, layout and other settings supported by the actual component API.

- Labels, descriptions and business data
- Value, selection, validation and request state
- Event handlers, recovery actions and permissions
- Raw style values, unregistered CSS variables and arbitrary token overrides

Component defaults → selected preset → permitted explicit settings. Pass business data, state and permissions separately.

Validate allowed keys, enums and combinations; diagnose unknown values. Distinguish type declarations from actual DOM and behavior verification.

## Conflict resolution order

- Preserve information, operability and accessibility first: Preserve essential information, state meaning, input, focus and operation paths. Dimension numbers do not override other required contracts.
- Reflow structure and reading order: Adjust wrapping, columns, action groups and panel arrangement first. Use local scrolling only for areas whose meaning requires two dimensions.
- Adjust spacing and surfaces within approved bounds: Respect the selected density and text scale while adjusting spacing and decoration within approved recipes. Limited space alone does not justify automatic compact mode or smaller text.
- Record remaining constraints and verification: If defaults cannot resolve a constraint, record scope, alternatives, impact, FR/AT references and actual verification. Do not skip token layers or conceal failed checks with exception approval.

sources/checks identify supporting references, not certification. Record actual product-environment results in the existing FR/AT evidence.

## Application and verification

Read the shared criteria, item DESIGN.md and actual source first. Assign token, DOM, CSS recipe and state responsibilities for each rule, then apply the conditions your product needs.

Compare revision in the policy and item contract. release identifies a registry publication; do not combine paginated results from different publications.

Use the latest CLI and local registry and restart stdio sessions. Reload the page to register WebMCP again. source prints raw code. Read DESIGN.md for source bundles or README.md for theme kits together with KLIC-DESIGN-SYSTEM.json.

## Selective adoption of references

Treat external documents and drafts as proposals. Check current KLIC problems, implementation and contracts, adopt only necessary rules, and record scope and reasons for deferral or rejection.

Do not present product names, example APIs or references from a draft as facts about KLIC. Connect adopted rules to actual tokens, DOM, CSS recipes, state handling and verification evidence.

## Scope to review together when making changes

Use a reported problem to assess impact across related usage paths. Changing only the named screen or tool does not complete that review.

- Implementation sources, tokens, components, types and schemas
- DOCS, web guides, developer documentation and examples
- MCP, CLI, WebMCP and API descriptions, inputs and responses
- AI prompts, llms.txt, source exports and theme exports
- Regression checks, builds, production publication and actual responses

After changing the canonical policy, regenerate affected guides, examples, tools, prompts and exports together and verify a matching revision. Explain unaffected paths and distinguish observed results from conditions that remain unverified.

## Actual token references
- klic.component.block.color.surface → var(--klic-component-block-color-surface)
- klic.component.block.color.panel → var(--klic-component-block-color-panel)
- klic.component.block.color.soft → var(--klic-component-block-color-soft)
- klic.component.block.color.selected → var(--klic-component-block-color-selected)

## Scope and verification
- KLIC shares seven design dimensions and four token layers, but applies them differently: components shape individual controls, blocks compose workflows, and motion defines transitions over time. Public npm: klic-design@0.0.3. Source candidate klic-design@0.0.4 is not published; klic-design@0.0.3 remains available.
- Do not present a browser switch as server authorization.
- Do not present a file demonstration as a production database connection.
- Examples demonstrate local behavior with sample data. Product authentication, database and external APIs require separate implementation.
- If you cannot access a reference, state that limitation and ask for the downloaded DESIGN.md or contract.
- Check the actual framework, dependencies and per-file licenses. Do not infer a native Vue implementation or accessibility certification.
- Separate the implementation plan, reused blocks, token mapping, unimplemented work and verification steps.
Markdown ↓
Give reference URLs to an AI that can read them. If it cannot access the sources, attach downloaded DESIGN.md and contract files.
From an idea to an implementation plan

01
Explore an example
Inspect the behavior and scope of a screen similar to yours.
02
Share your brief with your AI
Explain the desired result with blocks, tokens and do / don’t rules.
03
Review and adopt the source
Check dependencies, licenses and missing server work before integrating.
Your next screen.Start with a foundation.

What are you building?

Actual examples in your brief

Copy it and start building

From an idea to an implementation plan

Explore an example

Share your brief with your AI

Review and adopt the source

Your next screen.
Start with a foundation.
