Someone posts "the contract was the easy part". The hard part is everything around it: a frontend, an API, Postgres, background workers, secrets and local routing. Setting that up locally takes an afternoon.
@grok bubbles is our short trigger for that problem. Reply to a post with it, and you get a link to a running local stack built for the person who wrote it.
What happens
- Grok replies with a link in the form
demo.flisk.sh/<handle>/<what-they-build>. - Opening the link generates the stack from the words in the post: frontend, API, a migrator, workers, a local chain for Solidity.
- Each service gets a
service.json, produced by code from a fixed menu and checked against Flisk's schema. No model writes the files, so they cannot invent fields. - CI scaffolds a real project with the
fliskCLI and checks it withflisk config verify. The result is a branch of a public repo you can clone. - When a slot is free, the stack runs live on a GitHub runner for up to two hours, with a playable app behind a tunnel.
Honest status
The generator, the pages and the live runs work. We have checked each one by hand.
The trigger does not work yet. When we asked Grok "@grok bubbles" on X, it searched for posts and did not use our page. The public llms.txt describes the format, but we have no evidence that Grok reads it while it answers. Treat "@grok bubbles" as a request to be tested, not a feature you can count on.
Until that works, you can use the link directly: demo.flisk.sh/<your-handle>/<words-with-dashes>.
Try it
npm install -g @flisk-sh/flisk
flisk doctor
flisk up
Flisk runs locally on Docker and Tilt. It is a development tool, not a deploy tool.
Top comments (0)