stk is a strict Python framework for AI coding agents. Every session lands in the same architecture, passes the same gate, and proves the app still works in a real browser, so what agents build stays reliable, secure, and easy to change.
Build me an app on stk. Read stkit.dev/start.md and follow it step by step. The app: [describe your app]
Any framework will let an agent write code. The trouble is everything after: knowing what the app actually is, where a change belongs, what just broke, and whether the page renders at all. That part is stk.
the whole loop, with real output →Instead of guessing from files, the agent asks. stk doctor answers whether the app can start, and every line that isn't a tick carries the command that fixes it. stk inspect reports routes, models and config as JSON, with auth read from the real guard chain.
$ stk doctor ✓ migrations at heads (d7e01db94a41, stk_0008) ✓ admin user 1 admin(s) ! browser chromium not installed → uv run playwright install chromium $ stk inspect routes --json # condensed GET,POST /tf-setup auth security.two_factor_setup GET /login open security.login
stk new writes a feature as an extension inside your app, with its model, views, template, seed rows and an applied migration, and hands back the URL. The agent never edits a framework file, so upgrading stk is a version bump.
$ stk new invoice + created acme/invoice/models.py + created acme/seed.py with sample invoice rows + added invoice to the extensions in acme/app.py + migration generated and applied for invoice Open: http://localhost:5000/invoices/
stk verify runs lint, the framework's own checks, and a migration drift test against a throwaway database. Each failure prints the command that clears it, in --json too, so the agent applies the fix instead of inventing one. A check that could not run fails.
$ stk verify ✗ migration-drift add_column: invoice due_date → uv run stk db revision -m "describe change" && uv run stk db upgrade ✓ checks
stk smoke opens every page in Chromium, light and dark, on a throwaway database filled by your seed.py, and saves a screenshot of each. A page that answered 200 but never rendered fails. So does invisible text, a raw id or undefined on screen, and a check that could not run.
PASSED /invoices/ HTTP: 200 screenshot: .stk/smoke/invoices.png PASSED /invoices/ dark HTTP: 200 screenshot: .stk/smoke/invoices-dark.png
Every new app ships with the rules an agent would otherwise learn by breaking things: a CLAUDE.md (also read as AGENTS.md), five skills for blueprints, APIs, migrations, deploys, and lessons, and a CI workflow that runs the tests, the verify gate, and a real browser on every push.
CLAUDE.md → AGENTS.md .claude/skills/ stk-api stk-blueprint stk-deploy stk-lessons stk-migrate .github/workflows/checks.yml tests · stk verify · stk smoke
All in stk itself, all invisible to a green test suite and a clean console. The hound found them anyway. Each one is now a check that can’t pass quietly again.
Auth, jobs, migrations: the expensive-to-get-wrong parts are already built, tested, and boring on purpose. They live in the framework, not in generated code. Dependencies are Python only, and your users stay in your own database.
Your agent installs stk, writes the app with fresh secrets, creates the admin user, and proves it green with doctor, verify, and a real-browser smoke test before it builds anything. The steps it follows are public, so you can read them first.
Build me an app on stk. Read stkit.dev/start.md and follow it step by step. The app: [describe your app]
Ship it with the built-in deploy script (Caddy with automatic TLS, a firewall, fail2ban, key-only SSH), with Docker Compose, or as plain ASGI behind your own proxy. deploy docs
A read-only MCP server answers from the same pages as docs.stkit.dev, with three tools: search_docs, get_page, and get_command. No sign-in.
Evidence intelligence for defensible investigations. AI proposes claims pinned to the exact line, frame or region they came from, people decide with a passkey, and findings export as a signed package anyone can verify offline.
Open-source, self-hosted invoicing for freelancers and small businesses. No document limits.
An AI research assistant for human rights investigators. Deterministic collection lanes, content credentials, an archived citation trail and a hashed report. AI finds leads. Humans establish facts.