AGENTS.md
+4 −3
https://raw.githubusercontent.com/flisk-sh/flisk/HEAD/AGENTS.md
− Flisk runs a local development inner loop for microservices and multi-agent systems on Docker and Tilt. It discovers services from manifests, generates necessary local configurations (Vite, TSConfig, Compose), and orchestrates live-reloading environments. It is designed for fast local development; it does not emit Kubernetes manifests by default and does not replace production cluster orchestrators like Helm, Kustomize, Flux, or Argo.− - Local-only by default: Do not add Deployment or cluster manifest generators without an agreed export scope. Keep cluster deployment policy with the user's Kubernetes workflow.− - Clean test artifacts before linting: Running tests with coverage creates `cli/test-results/` and `cli/coverage/`, which cause Biome checks to fail. Remove these directories before running `biome check .`.+ Flisk runs a local development inner loop for microservices and multi-agent systems. Services that declare a `command` run as local processes with no Docker; container stacks run on Docker and Tilt. It discovers services from manifests, generates necessary local configurations (Vite, TSConfig, Compose), and orchestrates live-reloading environments. It is designed for fast local development; it does not emit Kubernetes manifests by default and does not replace production cluster orchestrators lik+ - Local-only by default: Do not add Deployment or cluster manifest generators without an agreed export scope. Keep cluster deployment policy with the user's Kubernetes workflow. The one agreed export scope: `flisk export render`, `flisk export wrangler` and `flisk export compose` (opt-in) may generate `render.yaml`, `wrangler.toml` and a standalone `docker-compose.yml` (bring-your-own resources, runs without Flisk) from `service.json`. They write files only: they never deploy, never create DNS r+ - The one-command demo is P1: `npx @flisk-sh/flisk demo` is the first thing a new user runs, so a regression in it outranks every other task. Its CI suite is `tests/e2e/journeys/demo` (check "🎬 Demo command, run twice"). It runs the demo twice, because the second run meets the first run's Docker volumes, and runs it with Docker not running (cases N1-N3), where the demo must fall back to the two-service app as local processes (`cli/src/utils/native-demo.ts`, `cli/templates/demo-native/`). Native + - Clean test artifacts before linting: Running tests with coverage creates cli/test-results/ and cli/coverage/, which cause Biome checks to fail. Remove these directories before running `biome check .`.