flisk-resource
Add one service to an existing Flisk project with `flisk resource <name> --type frontend|backend|worker|agent|mcp --stack <stack>`, or wrap an existing Dockerfile or image with `--type bring-your-own`
SKILL.md.claude/skills/flisk-resource/SKILL.md
GitHubFlisk resource
Create services with the CLI so each one gets a valid service.json and the right runtime contract. Do not hand-write container manifests.
Workflow
- Choose the type:
frontend(website),backend(HTTP API),worker(background jobs),agent(its own/health,/ready, andx-session-idrouting),mcp(tools server),database(the project's Postgres: aservice.jsononly, which services name independsOn), orbring-your-own(an existing Dockerfile with--dockerfile, or an image with--image). - Create it:
flisk resource <name> --type <type> --stack <stack>. Use--language <id>only when the user names a language (bunis the default). - For an existing service, use
--register-existinginstead of generating templates. - Check the result with
flisk doctorand read the newservice.json. - Start it with
flisk up <stack>(see the flisk-up skill).
Guardrails
- Use kebab-case names.
- A database migration belongs in its own
migratorresource, not in an API start script. - Ask before creating resources in a stack the user did not name.