Project

Python project using FastAPI.

Setup

• Python environment: conda test12
• Entry point: python app.py

Install Dependencies

/opt/miniconda3/envs/test12/bin/pip install -r requirements.txt

Run

/opt/miniconda3/envs/test12/bin/python app.py

Kiro Steering Rules

Steering files live in .kiro/steering/ and provide persistent guidance to Kiro across all interactions. There are three files configured:

always.md (inclusion: always)

Loaded into every Kiro interaction automatically. Contains general project rules:

• No hardcoded fallback values in exception handlers — treat them as dangerous and misleading.
• reqs / REQS is shorthand for requirements.txt.
• .ant files are personal admin notes, not Java-related.
• Python prompts must be stored in prompts/*.txt, never inline in Python code.
• FastAPI entry point is app.py, run via python app.py.
• Use the randum library (PyPI, Docs) for generating random data like cities.
• No new .md/.txt files for documentation — update README.md instead.
• Acronyms: SS = Screenshots, reqs/REQS = requirements.txt.

python-environment.md (inclusion: always)

Loaded into every interaction. Ensures the correct Python environment is used:

• Python: /opt/miniconda3/envs/test12/bin/python
• Pip: /opt/miniconda3/envs/test12/bin/pip
• CLI tools (alembic, uvicorn, etc.) must use the conda test12 env path.
• System Python (~/.local/bin/python) is off-limits — it's uv-managed and rejects installs.

ui-guidelines.md (inclusion: manual)

Only loaded when explicitly referenced via #ui-guidelines in chat. Contains frontend/UI rules:

• Use modals instead of JavaScript alert() dialogs for popups — better UX, styling, and accessibility.
• Use top-right toaster notifications instead of alerts for user feedback (success, error, warning, info). Auto-dismiss in 3–5 seconds with a manual close option.

kimport.md (inclusion: always)

Defines the "KImport" workflow — importing a feature from a /sample reference folder into the existing project:

• Import only functional logic (routes, models, utilities, business logic) — never the styling or theme.
• Do not introduce a new framework or change the existing framework pattern.
• Adapt imported code to match the project's current UI theme, conventions, and code style.
• The /sample folder is reference-only and gets deleted after KImport is complete.
• Process: read the feature in /sample → extract functional logic → integrate into existing project structure → preserve existing styling and framework choices.