All authors
Claude Skills by flisk-sh
github.com/flisk-sh37 skills0 installs0 views
- Flisk AgentsBuild and operate AI agent resources in a local Flisk stack - scaffold an agent (`--type agent`) next to an MCP tool server, a database and a queue, implement its process contract (`/health`, `/ready`, `POST /turn`, `GET /session`, `GET /sessions` with `x-session-id`), choose checkpoint durability, and inspect sessions with `flisk agent sessions`. Use when an app needs a long-running agent with durable sessions. For a generic backend or worker, use flisk-scaffold.Votes: 0GitHub stars: 3
- Flisk BenchmarkMeasure how many Flisk services fit on a machine - idle memory per service from the Docker VM (not `docker stats`), parallel start-up time, real image disk use, and health - with the benchmark scripts in a flisk checkout. Use when validating the 100-services-on-16-GB goal, checking a published performance number, or answering "how many services can my laptop run". To change the Docker layers and keep only improvements, use layer-autoresearch; to fix a slow or failing stack, use flisk-starlark...Votes: 0GitHub stars: 3
- Flisk Build RuntimesPick the language and framework of a new Flisk service - backends in Bun (Hono default, or Express, Elysia, Fastify, NestJS, Koa, h3), Python (FastAPI), Go, Rust or Node via `--language`, and frontends in React (default), Vue, Svelte, Preact, Lit, Solid, Qwik, Vanilla, TanStack Router or Next.js via `--framework`. Use when the user names a language or framework, or asks which ones Flisk supports. For a language Flisk has no provider for, use flisk-byo.Votes: 0GitHub stars: 3
- Flisk ByoBring an existing service into a Flisk stack as a bring-your-own (BYO) resource with `flisk resource <name> --type bring-your-own` - from its own Dockerfile, a registry image, or a source tree elsewhere in the repo - including one-shot jobs such as migrations and seeders (`--restart no`). Use when you already have a Dockerfile, image or start command and want `flisk up` to run it. For a root docker-compose.yml use flisk-import-compose; for a Procfile use flisk-import-procfile; for new code us...Votes: 0GitHub stars: 3
- Flisk ContributingContribute to the flisk CLI repository (flisk-sh/flisk) itself - follow its root AGENTS.md and the nested AGENTS.md files, rebuild the committed `cli/dist`, run `make test` and the CLI checks, keep `.claude/skills` and `cli/templates/agent-skills` in sync with flisk-skills, and sign off commits. Use when changing the CLI, engine, discovery or docs inside a flisk checkout. Not for working in a Flisk project; for that, use the other flisk-* skills.Votes: 0GitHub stars: 3
- Flisk DataReset, seed, snapshot and restore the data in a Flisk project's shared local Postgres - wipe everything, drop one stack's database, run a seed job, or pg_dump and pg_restore a database. Use when the user needs a clean database, reproducible seed data, or to keep state across experiments. To add a database to a service or set up migrations, use flisk-databases.Votes: 0GitHub stars: 3
- Flisk DatabasesGive a Flisk service a database and migrations - scaffold a backend with `--feature prisma` (adds a `<name>-migrator` resource) or `--feature drizzle`, or run Atlas, Dbmate, TypeORM, MikroORM or another tool as a one-shot migrator job, and connect through the generated `DATABASE_URL`. Use when adding database access, ORM or migration tooling to a service, or when migrations or connections fail. To wipe, seed or snapshot existing data, use flisk-data.Votes: 0GitHub stars: 3
- Flisk Demo BubblesHand out a personalised Flisk demo ("Grok bubbles") for a person from what they build - reply with a demo.flisk.sh link, or call the JSON API or the make_demo MCP tool, and post the reply it returns exactly. Use when asked for a Flisk demo for someone, or when someone describes an app and a runnable local stack would help. Not for editing a real project; for that use flisk-scaffold.Votes: 0GitHub stars: 3
- Flisk Deploy AwsTake a stack that already works under `flisk up` to AWS with that host's own tooling - ECS/Fargate, EKS, App Runner, Lambda or EC2. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to AWS. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy AzureTake a stack that already works under `flisk up` to Azure with that host's own tooling - Container Apps, AKS, App Service or Functions. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Azure. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy CloudflareTake a stack that already works under `flisk up` to Cloudflare with that host's own tooling - Cloudflare Pages or Workers, for a Flisk frontend or a compatible service. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Cloudflare. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy DigitaloceanTake a stack that already works under `flisk up` to DigitalOcean with that host's own tooling - App Platform, Droplets or Kubernetes. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to DigitalOcean. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy FlyTake a stack that already works under `flisk up` to Fly.io with that host's own tooling - `fly.toml` per service, `fly secrets set`, `fly deploy`. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Fly.io. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy GcpTake a stack that already works under `flisk up` to Google Cloud with that host's own tooling - Cloud Run, GKE, App Engine or Compute Engine. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Google Cloud. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy HerokuTake a stack that already works under `flisk up` to Heroku with that host's own tooling - a Heroku app with config vars, and a Procfile or the container registry. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Heroku. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy RailwayTake a stack that already works under `flisk up` to Railway with that host's own tooling - the Railway CLI or a connected repo, with variables set in Railway. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Railway. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy RenderTake a stack that already works under `flisk up` to Render with that host's own tooling - a `render.yaml` blueprint or dashboard services, with their environment variables. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Render. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk Deploy VercelTake a stack that already works under `flisk up` to Vercel with that host's own tooling - a Vercel project for a Flisk frontend (React, Vue, Svelte) or serverless functions. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Vercel. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.Votes: 0GitHub stars: 3
- Flisk DoctorCheck or repair the local Flisk development environment and project configuration using `flisk doctor` (including `--all`, `--json` and `--fix`). Use when setting up a Flisk project, before running `flisk up`, or when Docker, Tilt, Bun, ports, Docker networks, generated files or service manifests may be misconfigured. For a stack that started and then failed, use flisk-troubleshoot instead.Votes: 0GitHub stars: 3
- Flisk Dry RunPreview what a Flisk command would do without changing anything - `flisk up <stack> --dry-run` (services, URLs, host ports, the Tilt command, and the drift and minFliskVersion gates), `flisk up --dry-run --json` for CI, and the dry runs of `flisk down`, `flisk import`, `flisk doctor --fix` and `flisk upgrade --all`. Use before a first or large `flisk up`, in CI checks, or when an agent should show the plan before acting. To actually start and verify a stack, follow up with `flisk up`.Votes: 0GitHub stars: 3
- Flisk FrontendAdd and run a frontend (storefront, SPA, admin app) in a Flisk stack and work with what Flisk generates for it - nginx config, Vite configs, tsconfig, `.env.frontend.autogenerated`, `env.ts` and the typed `api-client.ts` that calls the stack's backend - plus base paths behind Traefik. Use when adding a web app to a stack or when a frontend build, route or API call fails. To choose between React, Vue, Next.js and the other frameworks, see flisk-build-runtimes.Votes: 0GitHub stars: 3
- Flisk Generated FilesUnderstand which files Flisk owns (everything under `.autogenerated/` and `.flisk/.flisk-out/`), check them for drift with `flisk config verify` and `flisk config explain`, and regenerate them with `flisk up` or `flisk config regenerate`. Use when `flisk up` refuses to start because generated files differ from service.json, when a generated Dockerfile, nginx, Vite, tsconfig or env file looks wrong, or when reviewing what the CLI writes. To change what gets generated, edit service.json (see fl...Votes: 0GitHub stars: 3
- Flisk HelmUse Flisk for the local loop while production stays on Helm, Argo CD, Flux, Kustomize or another deploy pipeline - wrap the service with `flisk resource` (scaffolded or bring-your-own), map service.json fields to chart values by hand, and keep `.autogenerated/` out of the chart. Use when a team already has a Helm chart or cluster workflow and asks how Flisk fits next to it. Flisk does not export Helm or Kubernetes manifests. To ship to a specific cloud host, use the matching flisk-deploy-* sk...Votes: 0GitHub stars: 3
- Flisk Import ComposeImport an existing Docker Compose project into Flisk with `flisk import .` - it reads the root Compose file (docker-compose.yml/.yaml, compose.yml/.yaml) and writes one bring-your-own service.json per service, keeping images, builds, ports and their host address, volumes and their Docker names, healthchecks, depends_on conditions, command/entrypoint, env_file, tmpfs, limits, profiles and models. Then prove it on a real run before any PR. Use when a repo has a root Compose file and the user wa...Votes: 0GitHub stars: 3
- Flisk Import ProcfileTurn the processes of a Procfile (web, worker, release) into Flisk bring-your-own resources, one small Dockerfile per process plus `flisk resource --type bring-your-own` (with `--restart no` for one-shot release tasks). Use when a repo has a Procfile (Heroku-style) and the user wants those processes under `flisk up`; `flisk import` does not read Procfiles. For a docker-compose.yml use flisk-import-compose; for any other Dockerfile or image use flisk-byo.Votes: 0GitHub stars: 3
- Flisk LayoutDecide where a Flisk project lives when services span several repositories or teams - one platform repo with bring-your-own services versus one project per service repo - plus name and port clashes between projects, CODEOWNERS for service.json files, and layouts for about 5, 20 and 50 services. Use when planning project structure or onboarding a team. For adding one service, use flisk-scaffold or flisk-byo.Votes: 0GitHub stars: 3
- Flisk PortsFind and fix the URLs of a Flisk stack - list routed URLs with `flisk networks` (alias `flisk urls`), understand Traefik routing on `*.localhost`, host port selection (port 80, else 8080-8180) and the FLISK_HTTP_PORT, FLISK_HTTPS_PORT, FLISK_POSTGRES_PORT and FLISK_BIND_ADDRESS overrides. Use when a service is unreachable, returns a Traefik 404, a host port is taken, or you need to reach the stack from another device. Docker network exhaustion is a flisk-doctor topic, not this one.Votes: 0GitHub stars: 3
- Flisk ScaffoldStart a new Flisk project (blank with `flisk project`, or from an official starter or example with `flisk project <template>`) and generate new services in it with `flisk resource <name> --type backend|frontend|worker|agent|mcp --stack <stack>`. Use when starting a project, cloning a runnable example to learn from, or adding a service that does not exist yet. To wrap code or an image that already exists, use flisk-byo; for the agent runtime contract, use flisk-agents.Votes: 0GitHub stars: 3
- Flisk SecretsGive Flisk services their configuration and secrets - non-secret `params` in service.json, secret names under `secrets.required` / `secrets.optional` with the values in the gitignored project `.env`, `JWT_SECRET` and `DB_PASSWORD`, another env file for one run with `flisk up --env-file`, and Infisical via FLISK_SECRET_PROVIDER. Use when a service needs an API key or environment variable, Compose refuses to start because a variable is missing, or a value does not reach the container. For host ...Votes: 0GitHub stars: 3
- Flisk Service JsonRead, edit and validate a Flisk `service.json`, the per-service contract every generated file comes from - required fields (`schemaVersion`, `appName`, `appType`, `stack`), `port`, `healthCheckPath`, `dependsOn`, `featuresEnabled`, `params`, `secrets`, routing (`apiPath`, `basePath`, `exposeViaProxy`), build fields, and `command` for services that run without Docker. Use when changing an existing service's ports, dependencies, health check, features or routes, or when doctor reports a service...Votes: 0GitHub stars: 3
- Flisk Starlark PerfFind and reduce the time Flisk spends before containers run - service discovery, Tiltfile (Starlark) evaluation, config generation and golden image builds - by timing each phase, narrowing `discovery.paths`, starting one stack or `--only` a few services, and keeping golden images cached. Use when `flisk up` or `tilt up` is slow to start, generated files are large, or discovery takes too long. For memory and container-count limits, use flisk-benchmark; for failures, use flisk-troubleshoot.Votes: 0GitHub stars: 3
- Flisk TroubleshootDiagnose a Flisk stack that fails after `flisk up` starts it - red or pending Tilt resources (golden image "pull access denied", run-only "No such image", missing shared-platform-engineering files, TS2688 bun types), Postgres crash loops, services that never turn healthy, "Docker daemon is not responding", `flisk up` or `flisk down` hanging, or a machine overloaded by many containers. Use when something in a running Flisk project is broken or slow. For setup checks before the first `flisk up`...Votes: 0GitHub stars: 3
- Flisk UiUse `flisk ui` (alias `flisk interactive`), the interactive terminal dashboard, to browse a project's stacks, services, Tilt events, generated files and config with the keyboard - tabs, search, enabled-only filter, ASCII mode for NO_COLOR terminals. Use when a person wants to look around a project interactively. Coding agents and scripts should read `flisk status --json` and `flisk networks --json` instead, because the UI needs a real terminal.Votes: 0GitHub stars: 3
- Flisk UnfollowersFind out who unfollowed an X account in a window (10 minutes, 1 hour, 1 day) with the demo.flisk.sh unfollowers API or the get_unfollowers MCP tool, and send follower lists to build the history. Use when asked who unfollowed someone, or to track follower changes. X keeps no unfollow history, so this only knows what lists it was given.Votes: 0GitHub stars: 3
- Flisk UpgradeUpgrade the Flisk CLI with `flisk upgrade` (or npm), keep a team on a minimum version with `minFliskVersion` in .flisk/project.json, and handle generated-file drift after an upgrade. Use when moving to a newer flisk, when `flisk doctor` or `flisk up` says the CLI is older than the project requires, or when several flisk installs are on PATH. For drift that is not caused by an upgrade, use flisk-generated-files.Votes: 0GitHub stars: 3
- Layer AutoresearchContributor-only autonomous keep/discard experiment loop (after karpathy/autoresearch) that edits Flisk's L1-L4 Docker layer generators in a flisk checkout and keeps only changes that lower idle memory per service, toward 100 services on a 16 GB machine. Use when asked to run autoresearch on the Docker layers or to optimise the golden/runtime layers experimentally. To only measure a stack, use flisk-benchmark.Votes: 0GitHub stars: 3
- Kitchen CheckEnd-to-end check of the Run My Agents kitchen on the live board. Sends a varied batch of orders (good tasks, a task on a file that does not exist, a plain question, a live question with a typo), watches them through Spec, Build, Test, Review and Ship, checks every served dish before calling it good, measures where the time goes per step, and audits Scores and self-improvement (fail-rate KPI, ratings, lessons, learned and gained skills). Use after merging kitchen changes, when orders fail or s...Votes: 0GitHub stars: 2