Files
KON/.agent/project.md

33 lines
2.8 KiB
Markdown

## KON Repository Rules
### Repository Role and Twin-Project Relationship
- This is a legacy Classic ASP application maintained alongside `KON-KIWI`; the two repositories are near twins whose main differences are presentation and styling.
- Preserve current routes, includes, sessions, authentication, authorization, form fields, redirects, uploads, downloads, and MSSQL behavior while the application remains in service.
- Before changing shared-looking behavior, compare the corresponding KON-KIWI implementation and determine whether the change belongs in both repositories or only this one.
- Do not copy a change across the pair blindly. Preserve intentional branding, layout, CSS, asset, configuration, customer, and deployment differences.
- Keep maintenance and small approved feature work narrowly scoped. Do not modernize unrelated business areas or shared include trees as a side effect.
### Encoding and File Safety
- Treat Classic ASP, include, script, and configuration files as potentially CP949/EUC-KR with CRLF. Verify each touched file's encoding, BOM state, line endings, response code page, and charset behavior before and after editing.
- Never run a repository-wide UTF-8 conversion, formatter, or line-ending normalization. Inspect byte-level diffs and Korean comments, messages, labels, and data after every approved text change.
- Treat existing connection settings and operational configuration as sensitive legacy material. Do not echo their values into chat, logs, fixtures, generated documentation, or completion reports, and do not alter them without explicit task scope.
### Runtime and Repository Data
- `Project`, `log`, `ProjectUpload`, `uploadFile`, `WebProject`, `_ServerLog`, and `Files` retain only `.gitkeep`; do not add runtime contents from these directories to Git.
- `store` is intentionally versioned. Preserve its tracked contents and do not add it to ignore rules or remove it as cleanup without explicit approval.
- Do not modify uploaded files, generated projects, logs, or runtime artifacts during analysis or validation.
### Data and Migration Direction
- Trace include chains and shared DB helpers before changing SQL, authentication, authorization, sessions, uploads, or file handling.
- Parameterize new or changed values while preserving ADO parameter order, types, result shapes, transactions, null behavior, and ordering.
- The long-term direction is staged migration to a Spring Boot backend and Next.js/TypeScript frontend. For now, record relevant migration observations briefly and prioritize safe legacy maintenance.
### Harness and Verification
- `AGENTS.md` and `CLAUDE.md` are generated. Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files.
- Do not start IIS, connect to a real database, send external requests, or mutate production-like data during validation without separate approval.