纳入 personal-dev/OpenSpec 配置、管理端与教育 Demo 界面调整、工作人员 JWT 默认 7 天,以及参考资料与代理文档更新。 Co-authored-by: Cursor <cursoragent@cursor.com>
35 lines
1.2 KiB
YAML
35 lines
1.2 KiB
YAML
schema: spec-driven
|
|
|
|
context: |
|
|
Language: zh
|
|
All artifacts must be written in zh.
|
|
Keep OpenSpec structural headings and SHALL/MUST keywords in English.
|
|
|
|
Project: 甘肃省房地产价格评估行业协会网站升级改造.
|
|
Systems: portal/ (Nuxt 4), admin/ (Vue 3 + Element Plus), server/ (Python REST), edu/ (not started).
|
|
Scope authority: docs/合同 (annotated) > docs/分析 > docs/理解 > docs/需求 > docs/可研.
|
|
Do not invent column schemas, APIs, or pages before the dedicated column brief exists.
|
|
Personal-dev planning artifacts live under openspec/changes/<change>/; issue tickets keep request, acceptance, and links only.
|
|
|
|
# Per-artifact rules (optional)
|
|
# Add custom rules for specific artifacts.
|
|
# Example:
|
|
# rules:
|
|
# proposal:
|
|
# - Keep proposals under 500 words
|
|
# - Always include a "Non-goals" section
|
|
# tasks:
|
|
# - Break tasks into chunks of max 2 hours
|
|
|
|
# Per-operation guidance (optional)
|
|
# Add advisory guidance for how apply and archive work should be conducted.
|
|
# This is separate from artifact rules above.
|
|
# Example:
|
|
# operations:
|
|
# apply:
|
|
# guidance:
|
|
# - Keep test summaries concise
|
|
# archive:
|
|
# guidance:
|
|
# - Summarize the archive outcome before finishing
|