fjaeckel

The OpenAPI-first workflow for this repo. Use whenever adding, removing, or changing an HTTP endpoint, request/response field, status code, query parameter, or auth requirement — and before touching anything under internal/api/generated/ or…

Database schema changes in this repo — creating golang-migrate migration pairs, naming and numbering rules, the reversible-down requirement, the test-DB init script, and repository/model follow-up. Use whenever adding a table, column, index, or constraint.

How to write and run tests in this repo — unit vs integration vs e2e, the build tags and env vars each tier needs, running a single test, and the pre-commit gate. Use before writing a test, running the suite, or claiming work is done.

Keeping everything a user owns inside the JSON export, the JSON import and cloud backups. Use whenever adding a table that accumulates user rows, adding a field to one, or touching GET /exports/json, POST /imports/json or internal/service/cloudbackup — and…

House comment style — every comment is terse and states only the WHAT, never the WHY. Rationale, history, and justification live in git commit messages and in docs/, not in source. Load before writing any comment, when touching code that contains comments,…

Keeping the admin console in step with every feature — which of the /admin endpoints (stats, config, maintenance, audit log) a new featureset has to show up in, and what to change to put it there. Use when adding or removing a feature, adding an env-var…

Instrumenting a feature and keeping Prometheus metrics, docs/METRICS.md, the Grafana dashboards in docs/metrics/dashboards/ and the alert rules in step with each other. Use when adding, renaming or removing a metric, adding a background job, external…

Security-review one feature or change in this repo — auth/ownership, injection, crypto and secrets, SSRF and external I/O, resource limits. Use when auditing a feature before or after implementation, reviewing a branch for security impact, or when asked for a…

Regenerate the marketing feature images and demo clips used by ninerlog.com and the ninerlog deployment README — light+dark stills and WebM/GIF animations rendered from the app against the "famous women in aviation" story fixtures. Load when asked to refresh…

How NinerLog talks to its backend — regenerating the typed client from the OpenAPI spec, writing TanStack Query hooks, cache invalidation, and the auth/token-refresh machinery. Load when adding or changing an API-backed hook, consuming a new endpoint,…

House comment style — every comment is terse and states only the WHAT, never the WHY. Rationale, history, and justification live in git commit messages and documentation, not in source. Load before writing any comment, when touching code that contains…

NinerLog's Tailwind v4 design system — color tokens, component classes, dark mode, typography, and mobile-first layout rules. Load before writing or restyling any JSX/CSS, adding a UI primitive, changing a brand or status color, or reviewing markup for visual…

MANDATORY for every change that alters rendered UI in NinerLog — capture before/after screenshots with the harness in scripts/screenshots and look at them. Load and run before touching any JSX, CSS, Tailwind class, translation string, icon, or layout, and…

Keeping the admin console (src/pages/admin/AdminPage.tsx) rendering everything the API exposes — stat tiles, config rows, maintenance actions, audit entries, new tabs. Use after regenerating src/api/schema.ts, when the API adds a field to AdminStats or…

How NinerLog frontend tests are written and run — Vitest + React Testing Library unit tests, Playwright E2E against a real API with MailPit, and the Docker test stack. Load when writing a test, debugging a failing or flaky test, or running the pre-push gate.

Recipe for adding a new route/page to the NinerLog frontend — lazy loading, auth guard, app-shell navigation, and forms. Load when creating a new screen, adding a route to App.tsx, adding a nav entry, or building a form with React Hook Form + Zod.

How the README's screenshots and demo GIF work — theme-aware picture pairs hotlinked from ninerlog.com — and how to regenerate or extend them. Load when changing README images, adding a screenshot for a new feature, or updating the feature list.

How the feature screenshots, demo videos and their light/dark variants are wired into ninerlog.com — the markup patterns, the naming contract with images/, and how to regenerate the media from the frontend repo. Load when touching feature images on any page,…