[HARD] Document all template default modifications before applying changes.
WHY: Template defaults serve as the baseline for all projects and undocumented changes create confusion and inconsistency across teams.
IMPACT: Without documentation, teams cannot understand why defaults deviate from standards, leading to maintenance issues and conflicting implementations.
[HARD] Create backups before executing template optimization workflows.
WHY: Template optimization involves structural changes that may be difficult to reverse without a clean restoration point.
IMPACT: Missing backups can result in permanent loss of user customizations, requiring manual reconstruction of project-specific configurations.
[HARD] Resolve all merge conflicts during template update workflows.
WHY: Unresolved conflicts create broken configurations that prevent proper template functionality.
IMPACT: Ignored conflicts lead to runtime errors, inconsistent behavior, and project instability requiring emergency fixes.
[SOFT] Maintain consistent template pattern usage throughout the project.
WHY: Mixing different template patterns creates cognitive overhead and makes the codebase harder to understand and maintain.
IMPACT: Inconsistent patterns reduce code predictability and increase onboarding time for new team members.
[HARD] Preserve complete customization history across all template updates.
WHY: Customization history provides an audit trail of project-specific decisions and enables rollback to previous states.
IMPACT: Lost history makes it impossible to understand why changes were made, preventing informed decisions about future modifications.
[HARD] Validate template functionality through testing before production deployment.
WHY: Untested templates may contain errors that only surface in production environments, causing system failures.
IMPACT: Production failures from untested templates result in downtime, data issues, and emergency rollbacks affecting users.
[SOFT] Design templates within reasonable complexity limits for maintainability.
WHY: Excessive template complexity makes them difficult to understand, modify, and debug when issues arise.
IMPACT: Overly complex templates slow down development velocity and increase the likelihood of errors during customization.
[HARD] Track template versions using the built-in version management system.
WHY: Version tracking enables understanding of template evolution, compatibility checking, and coordinated updates.
IMPACT: Without version tracking, teams cannot determine which template features are available or coordinate updates across projects safely.
[HARD] 应用变更前记录所有模板默认值修改。
原因：模板默认值是所有项目的基准，未记录的变更会导致团队间的混淆与不一致。
影响：若无文档，团队无法理解默认值为何偏离标准，进而引发维护问题与冲突性实现。
[HARD] 执行模板优化工作流前创建备份。
原因：模板优化涉及结构变更，若无干净的恢复点，可能难以回退。
影响：缺失备份可能导致用户自定义内容永久丢失，需要手动重建项目特定配置。
[HARD] 模板更新工作流中解决所有合并冲突。
原因：未解决的冲突会导致配置损坏，影响模板正常功能。
影响：忽略冲突会引发运行时错误、行为不一致及项目不稳定，需要紧急修复。
[SOFT] 项目全程保持模板模式使用的一致性。
原因：混合不同模板模式会增加认知负担，降低代码库的可理解性与可维护性。
影响：不一致的模式会降低代码可预测性，增加新成员的融入时间。
[HARD] 所有模板更新中保留完整的自定义历史记录。
原因：自定义历史记录提供了项目特定决策的审计轨迹，支持回退到之前的状态。
影响：丢失历史记录会导致无法理解变更原因，无法为未来修改提供依据。
[HARD] 生产部署前通过测试验证模板功能。
原因：未测试的模板可能包含仅在生产环境才会暴露的错误，导致系统故障。
影响：未测试模板引发的生产故障会导致停机、数据问题及影响用户的紧急回滚。
[SOFT] 设计模板时控制复杂度，确保可维护性。
原因：过度复杂的模板难以理解、修改与调试。
影响：过于复杂的模板会降低开发速度，增加自定义过程中的出错概率。
[HARD] 使用内置版本管理系统跟踪模板版本。
原因：版本跟踪有助于了解模板演进、兼容性检查及协调更新。
影响：若无版本跟踪，团队无法确定可用的模板功能，也无法安全地跨项目协调更新。