261006_01_ENH: Next.js 생성 템플릿에 에이전트 참조 구조 반영
This commit is contained in:
@@ -1,29 +1,18 @@
|
||||
## KriCreateNextApp Repository Rules
|
||||
# KriCreateNextApp Project Instruction Router
|
||||
|
||||
### Repository Role and Contracts
|
||||
## Required Project References
|
||||
|
||||
- This repository provides the Node.js 20 TypeScript CLI `@kri/create-next-app` and the template used to create KRI Next.js frontend applications.
|
||||
- Treat command names, flags, prompts, defaults, generated paths, dependency policy, template structure, and validation order as public contracts.
|
||||
- `src` is authoritative. `dist` is ignored build output and must not be edited or committed directly.
|
||||
- Keep the CLI implementation, help text, README, and templates synchronized whenever generated behavior changes.
|
||||
Before each related task, read the current contents of every matching reference below, even if it was read earlier in the session.
|
||||
|
||||
### Generated Frontend Invariants
|
||||
| Task scope | Required reference |
|
||||
|---|---|
|
||||
| Any substantive analysis, planning, implementation, debugging, review, or documentation work in this repository | `.agent/references/repository-rules.md` |
|
||||
|
||||
- Generated applications use TypeScript, React, Next.js, `@kri/common`, shadcn, and the KRI UI Registry contract declared by this repository profile.
|
||||
- Install `@kri/common@latest` and record the resolved dependency as an exact version using the existing npm workflow.
|
||||
- Prefer shadcn and approved KRI UI Registry components over new local primitives when a suitable component exists.
|
||||
- Do not introduce new frontend type or interface names ending in `Dto` or `DTO`.
|
||||
- Generate `.agent/profile.yml`, `.agent/project.md`, and harness line-ending policy for every project. Never copy a stale precomposed `AGENTS.md` into the template.
|
||||
If a task spans multiple scopes, read every matching reference. Do not assume remembered content is current.
|
||||
|
||||
### Harness Integration
|
||||
## Harness Workflow
|
||||
|
||||
- Generated projects default to `requested-project`; allow the supported explicit project-type override without changing the fixed `frontend` layer.
|
||||
- When the central harness is available, register the project in shared `workspace.yml` by default and run compose followed by verify. Allow an explicit local-registration override, and do not perform Git commits. Central-harness absence must not prevent project creation.
|
||||
- `AGENTS.md` and `CLAUDE.md` in this repository are harness-generated outputs. Never edit either file directly; edit `.agent` sources and recompose.
|
||||
- Do not commit user-specific absolute harness paths or credentials. Explicit paths are runtime inputs only.
|
||||
|
||||
### Verification and Publication
|
||||
|
||||
- Run `npm.cmd run typecheck` and `npm.cmd run build` on Windows for CLI changes.
|
||||
- Validate template changes by generating into a disposable directory without network installation first, then inspect unresolved placeholders, encoding, and harness composition.
|
||||
- Package publication, registry access, and network installation 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