trellis-he 0.6.0-beta.17

package/dist/templates/markdown/spec/backend/index.md.txt

@@ -0,0 +1,38 @@
+# 后端开发规范
+
+> 本项目后端开发的最佳实践与约定。
+
+---
+
+## 概览
+
+这个目录用于存放后端开发规范。请结合项目现状，把每个文件补充为你们团队真实使用的约定。
+
+---
+
+## 规范索引
+
+| 规范 | 说明 | 状态 |
+|------|------|------|
+| [目录结构](./directory-structure.md) | 模块组织与文件布局 | 待补充 |
+| [数据库规范](./database-guidelines.md) | ORM 模式、查询方式、迁移约定 | 待补充 |
+| [错误处理](./error-handling.md) | 错误类型与处理策略 | 待补充 |
+| [质量规范](./quality-guidelines.md) | 代码标准与禁用模式 | 待补充 |
+| [日志规范](./logging-guidelines.md) | 结构化日志与日志级别 | 待补充 |
+
+---
+
+## 如何补充这些规范
+
+对于每个规范文件：
+
+1. 记录项目里**实际存在的约定**，而不是理想状态。
+2. 引用来自代码库的**真实代码示例**。
+3. 写明团队明确避免的**禁用模式**及原因。
+4. 补充团队曾踩过的**常见错误**。
+
+目标是帮助 AI 助手和新团队成员理解这个项目**实际上是如何运作的**。
+
+---
+
+**语言要求**：所有文档默认使用**中文**编写。

package/dist/templates/markdown/spec/backend/logging-guidelines.md.txt

@@ -0,0 +1,51 @@
+# Logging Guidelines
+
+> How logging is done in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's logging conventions here.
+
+Questions to answer:
+- What logging library do you use?
+- What are the log levels and when to use each?
+- What should be logged?
+- What should NOT be logged (PII, secrets)?
+-->
+
+(To be filled by the team)
+
+---
+
+## Log Levels
+
+<!-- When to use each level: debug, info, warn, error -->
+
+(To be filled by the team)
+
+---
+
+## Structured Logging
+
+<!-- Log format, required fields -->
+
+(To be filled by the team)
+
+---
+
+## What to Log
+
+<!-- Important events to log -->
+
+(To be filled by the team)
+
+---
+
+## What NOT to Log
+
+<!-- Sensitive data, PII, secrets -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/backend/quality-guidelines.md.txt

@@ -0,0 +1,51 @@
+# Quality Guidelines
+
+> Code quality standards for backend development.
+
+---
+
+## Overview
+
+<!--
+Document your project's quality standards here.
+
+Questions to answer:
+- What patterns are forbidden?
+- What linting rules do you enforce?
+- What are your testing requirements?
+- What code review standards apply?
+-->
+
+(To be filled by the team)
+
+---
+
+## Forbidden Patterns
+
+<!-- Patterns that should never be used and why -->
+
+(To be filled by the team)
+
+---
+
+## Required Patterns
+
+<!-- Patterns that must always be used -->
+
+(To be filled by the team)
+
+---
+
+## Testing Requirements
+
+<!-- What level of testing is expected -->
+
+(To be filled by the team)
+
+---
+
+## Code Review Checklist
+
+<!-- What reviewers should check -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/frontend/component-guidelines.md.txt

@@ -0,0 +1,59 @@
+# Component Guidelines
+
+> How components are built in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's component conventions here.
+
+Questions to answer:
+- What component patterns do you use?
+- How are props defined?
+- How do you handle composition?
+- What accessibility standards apply?
+-->
+
+(To be filled by the team)
+
+---
+
+## Component Structure
+
+<!-- Standard structure of a component file -->
+
+(To be filled by the team)
+
+---
+
+## Props Conventions
+
+<!-- How props should be defined and typed -->
+
+(To be filled by the team)
+
+---
+
+## Styling Patterns
+
+<!-- How styles are applied (CSS modules, styled-components, Tailwind, etc.) -->
+
+(To be filled by the team)
+
+---
+
+## Accessibility
+
+<!-- A11y requirements and patterns -->
+
+(To be filled by the team)
+
+---
+
+## Common Mistakes
+
+<!-- Component-related mistakes your team has made -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/frontend/directory-structure.md.txt

@@ -0,0 +1,54 @@
+# Directory Structure
+
+> How frontend code is organized in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's frontend directory structure here.
+
+Questions to answer:
+- Where do components live?
+- How are features/modules organized?
+- Where are shared utilities?
+- How are assets organized?
+-->
+
+(To be filled by the team)
+
+---
+
+## Directory Layout
+
+```
+<!-- Replace with your actual structure -->
+src/
+├── ...
+└── ...
+```
+
+---
+
+## Module Organization
+
+<!-- How should new features be organized? -->
+
+(To be filled by the team)
+
+---
+
+## Naming Conventions
+
+<!-- File and folder naming rules -->
+
+(To be filled by the team)
+
+---
+
+## Examples
+
+<!-- Link to well-organized modules as examples -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/frontend/hook-guidelines.md.txt

@@ -0,0 +1,51 @@
+# Hook Guidelines
+
+> How hooks are used in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's hook conventions here.
+
+Questions to answer:
+- What custom hooks do you have?
+- How do you handle data fetching?
+- What are the naming conventions?
+- How do you share stateful logic?
+-->
+
+(To be filled by the team)
+
+---
+
+## Custom Hook Patterns
+
+<!-- How to create and structure custom hooks -->
+
+(To be filled by the team)
+
+---
+
+## Data Fetching
+
+<!-- How data fetching is handled (React Query, SWR, etc.) -->
+
+(To be filled by the team)
+
+---
+
+## Naming Conventions
+
+<!-- Hook naming rules (use*, etc.) -->
+
+(To be filled by the team)
+
+---
+
+## Common Mistakes
+
+<!-- Hook-related mistakes your team has made -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/frontend/index.md.txt

@@ -0,0 +1,39 @@
+# 前端开发规范
+
+> 本项目前端开发的最佳实践与约定。
+
+---
+
+## 概览
+
+这个目录用于存放前端开发规范。请结合项目现状，把每个文件补充为你们团队真实使用的约定。
+
+---
+
+## 规范索引
+
+| 规范 | 说明 | 状态 |
+|------|------|------|
+| [目录结构](./directory-structure.md) | 模块组织与文件布局 | 待补充 |
+| [组件规范](./component-guidelines.md) | 组件模式、props 与组合方式 | 待补充 |
+| [Hook 规范](./hook-guidelines.md) | 自定义 Hook 与数据获取模式 | 待补充 |
+| [状态管理](./state-management.md) | 本地状态、全局状态、服务端状态 | 待补充 |
+| [质量规范](./quality-guidelines.md) | 代码标准与禁用模式 | 待补充 |
+| [类型安全](./type-safety.md) | 类型模式与校验约定 | 待补充 |
+
+---
+
+## 如何补充这些规范
+
+对于每个规范文件：
+
+1. 记录项目里**实际存在的约定**，而不是理想状态。
+2. 引用来自代码库的**真实代码示例**。
+3. 写明团队明确避免的**禁用模式**及原因。
+4. 补充团队曾踩过的**常见错误**。
+
+目标是帮助 AI 助手和新团队成员理解这个项目**实际上是如何运作的**。
+
+---
+
+**语言要求**：所有文档默认使用**中文**编写。

package/dist/templates/markdown/spec/frontend/quality-guidelines.md.txt

@@ -0,0 +1,51 @@
+# Quality Guidelines
+
+> Code quality standards for frontend development.
+
+---
+
+## Overview
+
+<!--
+Document your project's quality standards here.
+
+Questions to answer:
+- What patterns are forbidden?
+- What linting rules do you enforce?
+- What are your testing requirements?
+- What code review standards apply?
+-->
+
+(To be filled by the team)
+
+---
+
+## Forbidden Patterns
+
+<!-- Patterns that should never be used and why -->
+
+(To be filled by the team)
+
+---
+
+## Required Patterns
+
+<!-- Patterns that must always be used -->
+
+(To be filled by the team)
+
+---
+
+## Testing Requirements
+
+<!-- What level of testing is expected -->
+
+(To be filled by the team)
+
+---
+
+## Code Review Checklist
+
+<!-- What reviewers should check -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/frontend/state-management.md.txt

@@ -0,0 +1,51 @@
+# State Management
+
+> How state is managed in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's state management conventions here.
+
+Questions to answer:
+- What state management solution do you use?
+- How is local vs global state decided?
+- How do you handle server state?
+- What are the patterns for derived state?
+-->
+
+(To be filled by the team)
+
+---
+
+## State Categories
+
+<!-- Local state, global state, server state, URL state -->
+
+(To be filled by the team)
+
+---
+
+## When to Use Global State
+
+<!-- Criteria for promoting state to global -->
+
+(To be filled by the team)
+
+---
+
+## Server State
+
+<!-- How server data is cached and synchronized -->
+
+(To be filled by the team)
+
+---
+
+## Common Mistakes
+
+<!-- State management mistakes your team has made -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/frontend/type-safety.md.txt

@@ -0,0 +1,51 @@
+# Type Safety
+
+> Type safety patterns in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's type safety conventions here.
+
+Questions to answer:
+- What type system do you use?
+- How are types organized?
+- What validation library do you use?
+- How do you handle type inference?
+-->
+
+(To be filled by the team)
+
+---
+
+## Type Organization
+
+<!-- Where types are defined, shared types vs local types -->
+
+(To be filled by the team)
+
+---
+
+## Validation
+
+<!-- Runtime validation patterns (Zod, Yup, io-ts, etc.) -->
+
+(To be filled by the team)
+
+---
+
+## Common Patterns
+
+<!-- Type utilities, generics, type guards -->
+
+(To be filled by the team)
+
+---
+
+## Forbidden Patterns
+
+<!-- any, type assertions, etc. -->
+
+(To be filled by the team)