261006_01_DOC: 공용 프런트엔드 참조 문서 및 에이전트 스킬 정비
This commit is contained in:
@@ -1,25 +1,18 @@
|
||||
## KriFrontCommon Repository Rules
|
||||
# KriFrontCommon Project Instruction Router
|
||||
|
||||
### Repository Role and Public Surface
|
||||
## Required Project References
|
||||
|
||||
- This repository publishes the ESM package `@kri/common`; the repository name and package name intentionally differ.
|
||||
- Treat `package.json` `exports`, exported TypeScript declarations, entry-point behavior, and documented environment requirements as public contracts.
|
||||
- Supported entry points are the package root and the explicitly declared subpaths in `package.json`. Do not create or document imports from `src`, `dist`, or another undeclared path.
|
||||
- Keep runtime-specific code separated. Browser-only APIs must not leak into server entry points, and server-only behavior must not enter browser bundles.
|
||||
- `src` is the source of truth. `dist` and declaration files are generated artifacts and must not be edited directly.
|
||||
Before each related task, read the current contents of every matching reference below, even if it was read earlier in the session.
|
||||
|
||||
### TypeScript and Dependency Rules
|
||||
| Task scope | Required reference |
|
||||
|---|---|
|
||||
| Any substantive analysis, planning, implementation, debugging, review, or documentation work in this repository | `.agent/references/repository-rules.md` |
|
||||
|
||||
- Preserve ESM, `NodeNext` module resolution, explicit `.js` relative import specifiers, declaration generation, and the current strict compiler options.
|
||||
- Keep exported types narrow and backward-compatible. Review any changed function signature, default, thrown error, serialization shape, or type export as a consumer-facing change.
|
||||
- React, TanStack Query, and Jotai integrations are optional. Do not make an optional peer mandatory for consumers that use only core utilities.
|
||||
- Do not add hidden global state for configuration, authentication, HTTP error handling, or query behavior.
|
||||
- Never expose secrets or server-only environment values through browser-facing configuration helpers.
|
||||
If a task spans multiple scopes, read every matching reference. Do not assume remembered content is current.
|
||||
|
||||
### Verification and Release Boundary
|
||||
## Harness Workflow
|
||||
|
||||
- Install with the repository's selected package manager and lockfile.
|
||||
- Run `npm run typecheck` for source changes and `npm run build` when declarations or package output may change.
|
||||
- Inspect the relevant `dist` entry points and generated declarations after changing exports.
|
||||
- Update `.agent/consumer.md` and human-facing documentation in the same approved change when a public contract changes.
|
||||
- Version changes, publication, registry changes, and consumer-repository edits 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.
|
||||
|
||||
Reference in New Issue
Block a user