Kiro tech.md Steering File

The .kiro/steering/tech.md file defines the full tech stack, library choices, and coding conventions for the project. It prevents Bolt from introducing unexpected libraries or violating established patterns across sessions.

Syntax

bolt-new

# Tech Stack

## Frontend
- [Framework + version]
- [CSS approach]
- [State management]
- [Routing]
- [Icon library — specify ONE]

## Backend / Database
- [Database and client library]
- [Auth approach]
- [Environment variable access pattern]

## Conventions
- [Naming rule 1]
- [File organization rule]
- [Pattern to always follow]
- [Pattern to never use]

Example

bolt-new

# Tech Stack

## Frontend
- React 18 + TypeScript (strict mode enabled)
- Tailwind CSS — utility classes only, no CSS files
- TanStack Query v5 for all server state
- React Router v6 for navigation
- Lucide React for icons (no other icon libraries)

## Backend
- Supabase for database and authentication
- @supabase/supabase-js client
- Environment: import.meta.env (Vite)

## Conventions
- Components: PascalCase, one per file
- Hooks: camelCase, prefixed with "use"
- All API calls in /src/services/, never in components
- Never use inline styles
- Never add new npm packages without specifying them in a prompt first