48 lines
2.5 KiB
Markdown
48 lines
2.5 KiB
Markdown
# Archery Event Docs Workspace Instructions
|
|
|
|
## Project Scope
|
|
- This repository is a **documentation workspace** for the 射箭赛事平台, not an application codebase.
|
|
- Default output language is **Chinese**. Keep existing Chinese filenames, headings, terminology, and punctuation style.
|
|
- Do not invent build steps, frameworks, or runtime details unless the relevant docs already define them.
|
|
|
|
## Recommended Context Order
|
|
Before editing, read the smallest set of relevant docs in this order:
|
|
1. `README.md` for the project overview and recommended reading path.
|
|
2. `01-基础与总览/` for business terms, roles, and core flows.
|
|
3. The matching feature area:
|
|
- `02-用户侧流程/`
|
|
- `03-商户侧流程/`
|
|
- `04-平台治理流程/`
|
|
- `06-微信小程序说明/`
|
|
- `07-商户后台说明/`
|
|
- `08-管理后台说明/`
|
|
- `09-后台API说明/`
|
|
4. `10-项目执行/` and `11-项目验收/` when the task involves delivery, acceptance, or agent task breakdown.
|
|
|
|
## Documentation Conventions
|
|
- Reuse the existing Markdown style: clear section headings, tables, bullets, and explicit document links.
|
|
- Prefer **linking to existing docs instead of duplicating long content**.
|
|
- Keep `待确认`、`待补充`、`草案` markers when business rules are still unresolved; do not silently guess missing rules.
|
|
- When introducing a new business term, update `01-基础与总览/业务名词表.md`.
|
|
- When a rule changes, sync the related process doc, status doc, and API or page-field docs together.
|
|
|
|
## Source-of-Truth References
|
|
Use these files as anchors before making larger changes:
|
|
- `README.md`
|
|
- `01-基础与总览/业务名词表.md`
|
|
- `05-通用基础/角色与权限矩阵.md`
|
|
- `05-通用基础/系统架构总览.md`
|
|
- `09-后台API说明/领域模块划分.md`
|
|
- `09-后台API说明/接口清单规划.md`
|
|
- `10-项目执行/Agent任务派发模板.md`
|
|
|
|
## Task and Template Guidance
|
|
- For new implementation or拆解任务, follow `10-项目执行/Agent任务派发模板.md`.
|
|
- For page-level specs, reuse `06-微信小程序说明/页面字段级说明模板.md`.
|
|
- For API details, reuse `09-后台API说明/字段级接口清单模板.md`.
|
|
- Prefer one clear module or subtask at a time, with explicit input docs, output expectations, and acceptance criteria.
|
|
|
|
## Validation
|
|
- There are currently **no build, test, or lint commands** in this repository.
|
|
- Validate changes by checking Markdown structure, file links, terminology consistency, and cross-document alignment.
|