// Guidance for working on the Flask-based backend, NDB Datastore, and OpenAPI integrations in chromium-dashboard.
How to add a new field to a feature across the entire stack (Data, API, and Frontend).
Guidance for local verification of changes to ensure they pass CI checks (linting, type checking, testing, and building).
Guidance for working on the Lit-based frontend, Shoelace widgets, and client-side routing in chromium-dashboard.
Guidance for running, debugging, and updating Playwright end-to-end tests in chromium-dashboard.
| name | chromestatus-backend |
| description | Guidance for working on the Flask-based backend, NDB Datastore, and OpenAPI integrations in chromium-dashboard. |
This skill provides context and guidelines for developing the backend of the chromium-dashboard project.
api/: Contains Flask request handlers for various API endpoints.framework/: Core infrastructure, including basehandlers.py and utility functions.internals/: Business logic, search filters, and data processing.pages/: (LEGACY) Handlers for main application pages. Do not add new code here.openapi/: OpenAPI specification file (api.yaml).gen/py/chromestatus_openapi/: Auto-generated Python models from OpenAPI.openapi/api.yaml. Use make openapi-backend to regenerate models.basehandlers.py classes for consistent permission checking and response handling. Do not add new handlers to the legacy pages/ directory.internals/models.py. Ensure queries are optimized and use proper indexing (see index.yaml).*_test.py). Run them using npm test.api/ or pages/.