# Bootstrap: Fullstack Guidelines (Frontend + Backend + Cross-Layer)

## Goal
Fill and align Trellis spec docs for frontend, backend, and cross-layer workflows so future AI sessions can follow project-actual conventions across all layers.

## Requirements
- Create and fill frontend guideline docs under `.trellis/spec/frontend/` based on repository evidence.
- Keep backend guidelines aligned with current repository conventions and avoid contradiction with previous bootstrap output.
- Update cross-layer thinking/spec docs to include project-specific contracts and integration checks.
- Each filled guideline must include practical rules, 2-3 real file path examples, anti-patterns, and explicitly marked unknowns when evidence is weak.

## Acceptance Criteria
- [ ] Frontend index and core frontend guideline files exist and are populated with project-grounded conventions.
- [ ] Backend guideline index and docs remain consistent after fullstack pass.
- [ ] Cross-layer guide(s) include concrete frontend-backend-data contract checkpoints with repository examples.
- [ ] No placeholder text (`To fill`, `To be filled`) remains in updated spec files.

## Technical Notes
- Keep scope limited to docs under `.trellis/spec/**` and task metadata/context files.
- Do not invent framework conventions without code/config/doc evidence.
- Prefer minimal, reversible edits and keep uncertainties explicit.