Repository Structure

You are a helpful development assistant who is assisting the user in the creation of a project. 

{Project details}

Note: all paths are relative to the root of this repository.

## Repository Structure

This repository adheres to a precise filestructure so that you can find information you require reliably.

### Spec

In addition to the details about the project provided above, you should refer to the development spec which is an overarching description of the project's stack and spec. You can find these at spec

- If there is only starter.md, this is the latest spec 
- If there are multiple spec files, use the one with the latest version number iteratively 
- If unsure ask the user to clarify which spec document reflects the latest and most up to date reflection of the project 

## Context

It is important to consider the user's context in addition to their technical requirements.

Contextual data about the user to inform your work in this repository is gathered at context (folder path). It may be one file (index.md) or in certain cases it may be chunked by subject.

IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.

## Speech-to-Text Awareness

The initial `prompt.md` file is typically captured via speech-to-text (STT) input. When processing this file or receiving additional voice input from the user, be aware of common STT transcription artifacts:

- **Homophones**: their/there/they're, to/too/two, your/you're, its/it's
- **Technical terms**: May be misheard or incorrectly transcribed (e.g., "Postgres" → "post grace", "OAuth" → "oh auth")
- **Missing punctuation**: Can affect meaning and sentence boundaries
- **Ambiguous phrasing**: Context may be needed to disambiguate intent

When you encounter unclear, contradictory, or suspiciously worded content:
1. Infer the likely intended meaning when obvious
2. Ask for clarification when ambiguous or critical to implementation
3. Don't assume the user made a logical error—consider STT as the source

This is particularly important when:
- Processing `prompt.md` via the `/build-repo` command
- Receiving updates via `/refine-spec` or `/add-context` commands
- The user provides technical specifications that seem inconsistent

## Development Phases

Track repository maturity through these phases:

- [ ] Repository initialized (cloned from template)
- [ ] Initial `prompt.md` created
- [ ] `/build-repo` executed successfully
- [ ] Spec and context reviewed and validated
- [ ] Development started
- [ ] First iteration complete

Use `/validate-setup` to check repository readiness at any time.