261006_01_DOC: UI 레지스트리 참조 문서 및 에이전트 스킬 정비

This commit is contained in:
2026-10-06 10:19:15 +09:00
parent 8e873714b6
commit 7c4dba52ef
18 changed files with 427 additions and 75 deletions

View File

@@ -1,24 +1,18 @@
## KriUiRegistry Repository Rules
# KriUiRegistry Project Instruction Router
### Repository Role and Sources
## Required Project References
- This repository is the internal shadcn registry named `kri`, published from `https://ui-registry.kric.com`.
- `registry.json`, `registry/components/registry.json`, and the files under `registry/` are source inputs. `dist/r` is generated output and must not be edited directly.
- Treat registry item names, targets, dependencies, registry dependencies, component props, behavior, styling tokens, and the public registry URL as consumer-facing contracts.
- Preserve shadcn registry schema compatibility and keep every item self-contained enough for the shadcn CLI to install it into a consumer project.
Before each related task, read the current contents of every matching reference below, even if it was read earlier in the session.
### Component and Metadata Rules
| Task scope | Required reference |
|---|---|
| Any substantive analysis, planning, implementation, debugging, review, or documentation work in this repository | `.agent/references/repository-rules.md` |
- Prefer accessible shadcn/Radix composition and the registry's existing component patterns before introducing a new abstraction.
- Keep project-specific business rules, API clients, routes, credentials, and environment assumptions out of registry components.
- Use portable design tokens and styles. Do not introduce project-only `content-text-*` classes or imports from `@kri/common/ui`; the repository verifier rejects them.
- Declare all package dependencies and registry dependencies accurately. Keep item file targets stable unless an approved migration covers consumers.
- Preserve loading, empty, error, disabled, keyboard, focus, and screen-reader behavior when changing an interactive component.
- Avoid embedding generated files or consumer-local configuration in registry source items.
If a task spans multiple scopes, read every matching reference. Do not assume remembered content is current.
### Verification and Release Boundary
## Harness Workflow
- Use the committed lockfile and run `npm run build`, followed by `npm run verify`, for registry changes.
- Inspect the generated item JSON when changing files, dependencies, item names, or targets.
- Update `.agent/consumer.md` and human documentation in the same approved change when installation or component-selection behavior changes.
- Registry publication, deployment, version changes, and consumer-repository updates require separate explicit approval.
- `AGENTS.md` and `CLAUDE.md` are generated outputs. Never edit them directly.
- Edit `.agent/project.md` only when routing changes. Store durable project detail in `.agent/references/`.
- A reference-only content change does not require recomposition when its route is unchanged. Run harness verification to validate routing and UTF-8.
- Recompose and verify after changing `.agent/project.md`, `.agent/profile.yml`, or another composed instruction source.