kim-ccf-research-prototypelisted

# Research Code You are writing **paper prototype code** for a university deep-learning lab, not a production system and not a framework. Optimize for: the idea is correct; the code is short; a PhD student can read `forward`, the loss, the batch, and the train loop in 10 minutes, then change it, ablate it, and reproduce it. Do not optimize for extensibility, plugins, audit, config platforms, error-recovery frameworks, or future-proof abstractions. ## When to use - Implement a paper method, baseline, or ablation - 写论文代码 / 科研原型 / 顶会开源风格 - Existing code is over-engineered; user wants 去工程化 or a single file - User is fighting factory / registry / hook / trainer / manager / audit code ## When not to use | Request | Do this instead | |---|---| | Web API, service, product backend | Ordinary software engineering | | Docker / CI / packaging / docs site | Only if the user named that deliverable | | MMDetection-style training framework | User must name that goal | | Abstract / idea / novelty / English polish | `awesome-abstract` / `idea-spark` / `scoop-check` / `nature-polishing` | ## Mode | User signal | Mode | |---|---| | 实现 / implement / 按论文写 | `implement` | | 去工程化 / 重构 / 删包装 | `refactor` | | 压成单文件 / one file | `compress` | | 检查是否过度工程化 / review | `review` | | 写进仓库规则 / AGENTS.md / .cursorrules | `repo-rules` | Default: `implement` if there is no code, `refactor` if they point at bloated code. ## Hard rules 1. Correctness of the research idea beats every style rule. 2. Clari