Python 235 FILES 4 FINDINGS

HOW FLASK
ACTUALLY WORKS

The Python micro framework for building web applications. Conventions, patterns, and architecture extracted from the pallets/flask repository by sourcebook.

VIEW_REPO north_east

QUICK_REF:

Routing: Flask routes Testing: pytest. Test utilities in: tests/test_helpers.py.

WHAT_MATTERS

→
Uses Flask routes for routing — follow this pattern, don't add REST routes directly

KEY_FINDINGS

Tests live in a separate test/ directory, mirroring src/ structure. New tests go there, not next to source files.

HIGH

Uses __init__.py as barrel exports. Import from the package, not from internal modules.

HIGH

6 non-empty __init__.py files

Tests use pytest. Test utilities in: tests/test_helpers.py.

HIGH

21 test files

+ 1 MORE FINDINGS (MEDIUM CONFIDENCE)

API endpoints use Flask routes. Follow this pattern for new routes.

MED

5 files use Flask routes

smart_toy USING_AI_TOOLS

→don't guess routing patterns — check first
→follow existing patterns listed in quick reference

CLAUDE.MD expand_more

# CLAUDE.md

This file provides guidance to Claude Code when working with this codebase.
Generated by [sourcebook](https://github.com/maroondlabs/sourcebook). Review and edit — the best context comes from human + machine together.

## Quick Reference

- **routing:** API endpoints use Flask routes
- **testing:** Tests use pytest. Test utilities in: tests/test_helpers.py.

## Critical Constraints

## Stack

Flask

## Project Structure

- `tests/` — Tests
- `docs/` — Documentation

## Conventions & Patterns

- **Testing:** Tests live in a separate test/ directory, mirroring src/ structure. New tests go there, not next to source files.
- **Python conventions:** Uses __init__.py as barrel exports. Import from the package, not from internal modules.
- **Dominant patterns:** Tests use pytest. Test utilities in: tests/test_helpers.py.

## Additional Context

- **Dominant patterns:** API endpoints use Flask routes. Follow this pattern for new routes.

## Before Making Changes

- **Follow existing patterns.** This project has established conventions (listed above). Match them instead of introducing new approaches.
- **Respect constraints.** Review the Critical Constraints section before making structural changes.

If the sourcebook MCP server is available (`sourcebook serve`), verify before acting:
- `get_blast_radius` — check what breaks if you edit a hub file
- `query_conventions` — confirm the right pattern before adding new code
- `get_pressing_questions` — get a briefing before editing an unfamiliar file

## What to Add Manually

The most valuable context is what only you know. Add:

- Architectural decisions and why they were made
- Past incidents that shaped current conventions
- Deprecated patterns to avoid in new code
- Domain-specific rules or terminology
- Environment setup beyond what .env.example shows

GENERATED IN ~3 SECONDS WITH

npx sourcebook init

VIEW ON GITHUB star

FROM_THE_BLOG

Why AI agents fail on real codebases arrow_forward Why auto-generated context makes agents worse arrow_forward

RELATED_REPOS

FASTAPI DJANGO PYDANTIC

HOW FLASKACTUALLY WORKS

WHAT_MATTERS

KEY_FINDINGS

npx sourcebook init

FROM_THE_BLOG

RELATED_REPOS

HOW FLASK
ACTUALLY WORKS