# Bootstrap Guidelines

## Goal

Fill in the initial project specifications in `.trellis/spec/` with real Kingdee development conventions. This gives future AI tasks the context they need to write code that matches your project's patterns.

## What Has Been Set Up

- `.trellis/` — workflow engine, task system, Python scripts
- `.kcode/` — KCode platform integration for Trellis workflow
- `.trellis/spec/backend/` — initial spec skeleton ready to be filled
- `.trellis/spec/project/` — project context template
- `.trellis/spec/guides/` — cross-layer thinking guides

## What to Do

1. Review the files in `.trellis/spec/backend/` — they are marked "To fill" where content is needed
2. For each file, determine the actual conventions used in this project:
   - Which base classes are used and how
   - Naming conventions
   - Error handling patterns
   - Testing practices
   - API design conventions
3. Fill in the spec files with real content — be specific, include code examples where helpful
4. If this project has existing rules (in `CLAUDE.md`, `.cursorrules`, or other configs), import them into the relevant spec files
5. When done, archive this task:
   ```bash
   python3 ./.trellis/scripts/task.py finish
   python3 ./.trellis/scripts/task.py archive 00-bootstrap-guidelines
   ```

## Remember

- Specs document actual conventions, not aspirational ideals
- Prefer specific rules with examples over abstract principles
- Each spec file covers one topic — keep them focused
- Specs grow over time; `trellis-update-spec` skill adds new knowledge after each task