# Knowledge Base Index

<!--
AGENT INSTRUCTIONS:
- Scan this file FIRST when looking for existing knowledge
- Use descriptions to assess relevance before loading full docs
- Update this index when adding or modifying knowledge docs
- Always use real dates, never leave as YYYY-MM-DD
-->

## Quick Reference

| Category  | Count | Last Updated |
| --------- | ----- | ------------ |
| Decisions | 0     | -            |
| Features  | 0     | -            |
| Notes     | 0     | -            |
| Product   | 2     | -            |

---

## Decisions (ADRs)

Architecture Decision Records — why we made key technical choices.

| ID  | Title                     | Status | Date |
| --- | ------------------------- | ------ | ---- |
| -   | No decisions recorded yet | -      | -    |

<!-- Example:
| 001 | Use Convex for Backend | Accepted | 2026-01-15 |
  -> Explains why we chose Convex over traditional REST API
-->

---

## Features

Documentation for complex features that need more than a spec.

| Feature | Description         | Last Updated |
| ------- | ------------------- | ------------ |
| -       | No feature docs yet | -            |

<!-- Example:
| auth-system | Complete auth flow documentation | 2026-02-01 |
  -> OAuth setup, session handling, role-based access
-->

---

## Notes

Technical discoveries, gotchas, learnings.

| Topic | Description  | Added |
| ----- | ------------ | ----- |
| -     | No notes yet | -     |

<!-- Example:
| api-rate-limits | Third-party API quirks and workarounds | 2026-01-20 |
  -> Stripe webhook retries, Figma API limits, etc.
-->

---

## Product

User research and product documentation.

| Document      | Description          | Last Updated |
| ------------- | -------------------- | ------------ |
| personas.md   | Target user profiles | -            |
| user-flows.md | Key user journeys    | -            |

---

## How to Add Knowledge

1. Choose the category: decision, feature, note, or product
2. Copy the template from `templates/<category>.md`
3. Fill in the frontmatter (title, created date, related issues)
4. Write the content following the template structure
5. Add an entry to this index with a concise description
6. Use the `/knowledge` command for a guided flow