rule-architectlisted

# rule-architect Generate an advanced, runtime-neutral rule set: one slim `AI_RULES.md` index + on-demand `docs/*.md` rule files. Runtime-specific entry files both resolve to the same neutral index. ## Output Language Generated rule files follow the project, not this document: 1. Existing `AI_RULES.md` / legacy rule index / `docs/*.md` / `README` in the project → match their language. 2. No existing docs → match the language the user is writing in. 3. Still ambiguous → English. Apply one language consistently across `AI_RULES.md`, portable entry pointers, and every `docs/*.md` in the same run — a half-English, half-Korean rule set is a defect. Structural tokens stay fixed regardless of language: `MUST` / `NEVER` / `PREFER`, `why:`, the ❌/✅ markers, UPPERCASE file names, and the `<!-- generated by rule-architect -->` marker. Report to the user in their language. Core principle: **rules record only what code cannot tell you.** An agent can run `ls` and read `requirements.txt` by itself; it cannot guess that a model must be registered in two places, or that env must load before config import. Always-loaded context (`AI_RULES.md`) stays minimal; detail lives in `docs/` and loads only when the topic comes up. ## Output Contract The deliverable is EXACTLY this shape. Not one big file. Not unlinked docs. ### AI_RULES.md (≤60 lines) — runtime-neutral index In order: 1. Project one-liner (what it is, 1–2 lines). 2. **Core Rules** — ≤10 bullets. Only top non-derivable constr