Using it with AI agents
After you install, every supported agent has two skills:
| Skill | What it does |
|---|---|
flutter-kickstart | Asks the setup questions, generates the app, adds features, sets up the AI layer |
flutter-figma-to-flutter | Turns a Figma frame into widgets that use the app's theme tokens and widgets |
- Claude Code
- Cursor
- Windsurf
- Antigravity
- Codex
- Gemini CLI
- GitHub Copilot
Things you can ask
- "Create a new Flutter app called Acme Wallet for com.acme."
- "Add an orders feature that loads
/v1/orders." (inside a generated app) - "Implement this Figma frame: <link>" (needs a Figma MCP server)
- "Set up the AI rules for this app." (for an app Flutter Kickstart created earlier)
What the agent does
- Asks the setup questions one at a time.
- Reads your answers back and waits for a yes.
- Runs the same generator as
fks create. - Tells you what was created, and what still needs a human (secrets, signing, translations).
Because the agent runs a script instead of writing the project by hand, every agent produces the same app.
Which path the agent picks
| Situation | What happens |
|---|---|
| New app | Setup questions, then the generator |
| Add a feature to an app Flutter Kickstart created | tool/kickstart/add_feature.py inside the app |
| App was created before, AI files missing or old | setup_ai.py --root <app> refreshes them |
| App not created by Flutter Kickstart | The agent does not run the generator over it. It follows that app's own conventions. |
Agents without skill support
Point the agent at the skill file directly:
Read
~/.flutter-kickstart/skills/flutter-kickstart/SKILL.mdand follow it.
After the app exists
The generated app carries its own AGENTS.md and project skills, so your agent keeps following the rules without the global skill. See AI layer.