flutter-frontend-for-adk
Skill154 starsChanged 53 days agoBSD-3-ClauseView on GitHub
Orchestrates the discovery, mapping, design, and implementation of a premium Flutter-based frontend for an Agent Development Kit (ADK) agent written with Python.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 9 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Before starting, the developer or coding agent should locate ADK framework-level specifications using the following resources instead of …
- Very specific: line 22
Activate ADK Code Skill: Ensure that /google-agents-cli-adk-code is active in the current session.
- Distinctive: line 34
Action: Read references/agent_discovery.md for step-by-step discovery instructions.
- Very specific: line 35
Deliverable: Create the AGENT_INTERFACE_NOTES.md file in the root of the project.
- Distinctive: line 42
Action: Read references/frontend_usage.md for instructions on defining app behavior.
- Very specific: line 43
Deliverable: Create the FRONTEND_USAGE_NOTES.md file in the root of the project.
- Distinctive: line 50
Action: Read references/frontend_architecture.md for instructions on defining app architecture.
- Very specific: line 51
Deliverable: Create the FRONTEND_ARCHITECTURE_NOTES.md file in the root of the project.
- Distinctive: line 58
Action: Read references/frontend_design.md for styling and UI blueprints.
- Very specific: line 59
Deliverable: Create the FRONTEND_DESIGN_NOTES.md file in the root of the project.
- Distinctive: line 65
Create and program the Flutter client application within the workspace, implementing all designs and specifications.
- Distinctive: line 67
Read references/frontend_best_practices.md for specific implementation patterns and best practices.
- Very specific: line 69
Add the approved packages (provider, flutter_markdown, url_launcher, and http) to frontend/pubspec.yaml.
- Very specific: line 70
Write the manual serialization models, the AdkApiService (implementing standard REST and SSE HTTP streamed response parsers), the …
- Very specific: line 71
Verify code cleanliness and correctness by running flutter format, flutter analyze, and flutter test inside the frontend/ directory.
- Distinctive: line 82
If the project has a README.md in the root directory, update it to reference the new frontend, detail prerequisites (such as the Flutter …
- Very specific: line 83
Update the default frontend/README.md file to describe the frontend client, its structure, and how to launch both the agent and the client …
- Distinctive: line 84
Look for any additional pre-existing docs that might need to be updated and do so.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Building a Flutter Frontend for an ADK Agent
This skill orchestrates the end-to-end workflow of designing, specifying, and implementing a premium Flutter-based frontend for any Agent Development Kit (ADK) agent.
Prerequisites & External References
Before starting, the developer or coding agent should locate ADK framework-level specifications using the following resources instead of restating them in this skill:
- Activate ADK Code Skill: Ensure that
/google-agents-cli-adk-codeis active in the current session. Refer to its reference fileadk-python.mdto understand the coreEvent,EventActions, and state management models. - Fetch Official Docs: Retrieve the official documentation index by calling
curl https://adk.dev/llms.txtand search for pages related to client serving, networking, or the Python API server. - Inspect Local Code: To see exact Pydantic definitions and FastAPI endpoint details directly:
- Open and inspect the local server definition inside your python environment at
.venv/lib/python*/site-packages/google/adk/cli/adk_web_server.py. - Open and inspect the event schemas at
.venv/lib/python*/site-packages/google/adk/events/event.pyandevent_actions.py.
- Open and inspect the local server definition inside your python environment at
Follow the phases below sequentially. Do not skip ahead. You must complete and record the findings of each phase before beginning the next. When creating an implementation plan, add a blocking task for the "Review" step in each phase that has one and wait for the user to perform a review before beginning the next phase.
Phase 1: Workspace & Agent Discovery
Identify the core purpose of the agent in this repository, understand its sub-agent hierarchy, map its API endpoints, event streams, and human-in-the-loop triggers, and record this information.
- Action: Read references/agent_discovery.md for step-by-step discovery instructions.
- Deliverable: Create the AGENT_INTERFACE_NOTES.md file in the root of the project.
- Review: Summarize (in a paragraph or two) what you just learned for the user. Invite them to inspect
AGENT_DISCOVERY_NOTES.md, and do not proceed to Phase 2 until they indicate that you should do so.
Phase 2: Frontend Usage & Behavior
Define the high-level behavioral and functional requirements of the frontend: target platforms, screen specifications, feature details, and user experience flows.
- Action: Read references/frontend_usage.md for instructions on defining app behavior.
- Deliverable: Create the FRONTEND_USAGE_NOTES.md file in the root of the project.
- Review: Summarize (in a paragraph or two) what you just learned for the user. Invite them to inspect
FRONTEND_USAGE_NOTES.md, and do not proceed to Phase 3 until they indicate that you should do so.
Phase 3: Frontend Architecture
Define the structural patterns of the application, including core folder directory layouts, manual model serializations, and state management setups.
- Action: Read references/frontend_architecture.md for instructions on defining app architecture.
- Deliverable: Create the FRONTEND_ARCHITECTURE_NOTES.md file in the root of the project.
- Review: Summarize (in a paragraph or two) what you just learned for the user. Invite them to inspect
FRONTEND_ARCHITECTURE_NOTES.md, and do not proceed to Phase 4 until they indicate that you should do so.
Phase 4: Frontend Design & Layout
Design the visual structure, layout columns, styling guides, states, and micro-animations for the frontend application.
- Action: Read references/frontend_design.md for styling and UI blueprints.
- Deliverable: Create the FRONTEND_DESIGN_NOTES.md file in the root of the project.
- Review: Summarize (in a paragraph or two) what you just learned for the user. Invite them to inspect
FRONTEND_DESIGN_NOTES.md, and do not proceed to Phase 5 until they indicate that you should do so.
Phase 5: Scaffolding & Implementation
Create and program the Flutter client application within the workspace, implementing all designs and specifications.
- Action:
- Read references/frontend_best_practices.md for specific implementation patterns and best practices.
- Scaffold a fresh Flutter project inside a folder named
frontend/at the root of the workspace. Do not specify an org name unless instructed. Create the app to build for only those platforms specified by the user -- if you're not sure, ask. - Add the approved packages (
provider,flutter_markdown,url_launcher, andhttp) tofrontend/pubspec.yaml. - Write the manual serialization models, the
AdkApiService(implementing standard REST and SSE HTTP streamed response parsers), theAgentProviderstate notifier, and the responsive views/widgets followingFRONTEND_ARCHITECTURE_NOTES.mdandFRONTEND_DESIGN_NOTES.md. - Verify code cleanliness and correctness by running
flutter format,flutter analyze, andflutter testinside thefrontend/directory.
- Deliverable: A fully compiled and functional Flutter application located inside the
frontend/folder.
Phase 6: Workspace Integration & Documentation
Integrate the frontend into the workspace build flows, update version control settings, and document the client setup for developers.
- Action:
- Build Configuration: Examine the codebase to determine how a developer builds and runs the backend agent (e.g. searching for
Makefiletargets, task configurations inpyproject.tomllike Poe/Taskipy,package.jsonscripts, or customrun.sh/build.shscripts). Update these automation tools or files to provide simple commands for developers to build, test, and launch the new Flutter frontend. - VCS Ignore Setup: Update the project's version control ignore configurations to make sure they account for the new project and its artifacts. The Flutter frontend should have a nested
.gitignorefile that will account for most things. If the root.gitignorefile ignoreslib/, though, make sure to add an exclusion for Flutter'slibdirectory (!frontend/lib). - Documentation Update:
- If the project has a
README.mdin the root directory, update it to reference the new frontend, detail prerequisites (such as the Flutter SDK version), and outline startup instructions. - Update the default
frontend/README.mdfile to describe the frontend client, its structure, and how to launch both the agent and the client using the build configuration tools updated in step 1. - Look for any additional pre-existing docs that might need to be updated and do so.
- If the project has a
- Build Configuration: Examine the codebase to determine how a developer builds and runs the backend agent (e.g. searching for
- Deliverable: Updated workspace integration configurations, build scripts, and documentation files.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

