FallenSigh
8fdf944555
- sync_rtl/common/: skid_buffer, pipeline_reg, defines (valid/ready) - sync_rtl/mod_add/: modular adder example with Verilator C++ TB - test_framework/: Python-driven Verilator compile/sim/compare pipeline - test_framework/modules/mod_add/: 50-vector test plan, full鏈路 PASS - .trellis/spec/: RTL and test_framework conventions documented
39 lines
1.2 KiB
Markdown
39 lines
1.2 KiB
Markdown
# Backend Development Guidelines
|
|
|
|
> Best practices for backend development in this project.
|
|
|
|
---
|
|
|
|
## Overview
|
|
|
|
This directory contains guidelines for backend development. Fill in each file with your project's specific conventions.
|
|
|
|
---
|
|
|
|
## Guidelines Index
|
|
|
|
| Guide | Description | Status |
|
|
|-------|-------------|--------|
|
|
| [Directory Structure](./directory-structure.md) | Module organization and file layout | To fill |
|
|
| [Database Guidelines](./database-guidelines.md) | ORM patterns, queries, migrations | To fill |
|
|
| [Error Handling](./error-handling.md) | Error types, handling strategies | To fill |
|
|
| [Quality Guidelines](./quality-guidelines.md) | Code standards, forbidden patterns | To fill |
|
|
| [Logging Guidelines](./logging-guidelines.md) | Structured logging, log levels | To fill |
|
|
|
|
---
|
|
|
|
## How to Fill These Guidelines
|
|
|
|
For each guideline file:
|
|
|
|
1. Document your project's **actual conventions** (not ideals)
|
|
2. Include **code examples** from your codebase
|
|
3. List **forbidden patterns** and why
|
|
4. Add **common mistakes** your team has made
|
|
|
|
The goal is to help AI assistants and new team members understand how YOUR project works.
|
|
|
|
---
|
|
|
|
**Language**: All documentation should be written in **English**.
|