wangsli/hyb-oa
1
0
派生 0
代码 工单 合并请求 工作流 8 软件包 项目 发布 百科 活动

治理 Trellis spec 占位噪音与规则口径（05-29-spec-governance-cleanup）

浏览代码
这个提交包含在：
wangsli
2026-05-29 09:56:22 +08:00
父节点 cdd56bc5df
当前提交 c192c77c7a
共修改 22 个文件，包含 306 行新增和 610 行删除
下载 Patch 文件 下载 Diff 文件 展开所有文件 折叠所有文件
.trellis/spec/backend/database-guidelines.md
-51
查看文件
@@ -1,51 +0,0 @@
# Database Guidelines
> Database patterns and conventions for this project.
---
## Overview
<!--
Document your project's database conventions here.
Questions to answer:
- What ORM/query library do you use?
- How are migrations managed?
- What are the naming conventions for tables/columns?
- How do you handle transactions?
-->
(To be filled by the team)
---
## Query Patterns
<!-- How should queries be written? Batch operations? -->
(To be filled by the team)
---
## Migrations
<!-- How to create and run migrations -->
(To be filled by the team)
---
## Naming Conventions
<!-- Table names, column names, index names -->
(To be filled by the team)
---
## Common Mistakes
<!-- Database-related mistakes your team has made -->
(To be filled by the team)
.trellis/spec/backend/directory-structure.md
-54
查看文件
@@ -1,54 +0,0 @@
# Directory Structure
> How backend code is organized in this project.
---
## Overview
<!--
Document your project's backend directory structure here.
Questions to answer:
- How are modules/packages organized?
- Where does business logic live?
- Where are API endpoints defined?
- How are utilities and helpers organized?
-->
(To be filled by the team)
---
## Directory Layout
```
<!-- Replace with your actual structure -->
src/
├── ...
└── ...
```
---
## Module Organization
<!-- How should new features/modules 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)
.trellis/spec/backend/error-handling.md
-51
查看文件
@@ -1,51 +0,0 @@
# Error Handling
> How errors are handled in this project.
---
## Overview
<!--
Document your project's error handling conventions here.
Questions to answer:
- What error types do you define?
- How are errors propagated?
- How are errors logged?
- How are errors returned to clients?
-->
(To be filled by the team)
---
## Error Types
<!-- Custom error classes/types -->
(To be filled by the team)
---
## Error Handling Patterns
<!-- Try-catch patterns, error propagation -->
(To be filled by the team)
---
## API Error Responses
<!-- Standard error response format -->
(To be filled by the team)
---
## Common Mistakes
<!-- Error handling mistakes your team has made -->
(To be filled by the team)
.trellis/spec/backend/index.md
+11 -15
查看文件
@@ -1,30 +1,26 @@
# Backend Development Guidelines
# Backend Spec Redirect
---
## Overview
hyb-oa backend work uses Fastify, Prisma and PostgreSQL under `server/`.
The project-specific backend rules live in `../hyb-oa/backend-fastify-prisma.md`;
the files in this directory are Trellis default scaffolding and may be expanded
only when a later task needs deeper backend conventions.
hyb-oa backend work uses Fastify, Prisma and PostgreSQL under `server/`. The
active backend rules live in `../hyb-oa/backend-fastify-prisma.md`.
---
This directory intentionally contains no separate backend guideline files. The
old default scaffold files were removed because placeholder specs are noise for
future agents.
## Guidelines Index
## Read
| Guide | Description | Status |
|-------|-------------|--------|
| [hyb-oa Backend Rules](../hyb-oa/backend-fastify-prisma.md) | Current project backend rules | Current |
| [Directory Structure](./directory-structure.md) | Module organization and file layout | Scaffold |
| [Database Guidelines](./database-guidelines.md) | ORM patterns, queries, migrations | Scaffold |
| [Error Handling](./error-handling.md) | Error types, handling strategies | Scaffold |
| [Quality Guidelines](./quality-guidelines.md) | Code standards, forbidden patterns | Scaffold |
| [Logging Guidelines](./logging-guidelines.md) | Structured logging, log levels | Scaffold |
---
## Language
## Rule
Project rules are Chinese-first where they are user-facing. Short English files
generated by Trellis may remain when they are tool-facing scaffolding.
Add a new backend spec file only when a later Trellis task discovers concrete,
source-backed backend conventions that do not belong in the project-level
backend spec.
.trellis/spec/backend/logging-guidelines.md
-51
查看文件
@@ -1,51 +0,0 @@
# 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)
.trellis/spec/backend/quality-guidelines.md
-51
查看文件
@@ -1,51 +0,0 @@
# 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)