Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ChunkyTofuStudios/flutter-skills --skill design-polishgit clone --depth 1 https://github.com/ChunkyTofuStudios/flutter-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/chunkytofustudios/flutter-skills/design-polish)<a href="https://agentmods.dev/skills/chunkytofustudios/flutter-skills/design-polish"><img src="https://agentmods.dev/badge/skills/chunkytofustudios/flutter-skills/design-polish/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/chunkytofustudios/flutter-skills/design-polish"><img src="https://agentmods.dev/badge/skills/chunkytofustudios/flutter-skills/design-polish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00204 | $0.03490 |
| Opus 5 | $0.00102 | $0.01745 |
| Sonnet 5 | $0.00041 | $0.00698 |
| Haiku 4.5 | $0.00020 | $0.00349 |
Grade A, and why
design-polish scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design polish (Flutter)
You polish screens in a Flutter mobile app — improving visual hierarchy, readability, and section clarity so a user instantly knows how to use the app. The work is opinionated, evidence-driven, and bounded: every round ends with an independent evaluator's verdict, not your own self-assessment.
Setup
If the user didn't specify screens, ask:
- "Which screens should I polish? Provide route names (e.g.
/settings,/profile) or component file paths underlib/."
The app must be running on an Android emulator. Use the android-emulator skill — every screenshot, tap, swipe, and accessibility-tree dump in this workflow goes through it:
scripts/emu.sh health # confirm device, AVD, foreground app
scripts/emu.sh boot # if not running
scripts/emu.sh run # build & install in background
scripts/emu.sh wait-run # block until attached
Establish design tone
Do this once before touching any screen. Skipping it is the single biggest source of inconsistency — your changes will look right in isolation and wrong next to the rest of the app.
- Find a reference screen. Try in this order:
- The user named a polished screen ("settings looks great, polish the rest to match"). Use that.
- The home page:
MaterialApp.home,initialRoute, or the first tab of aBottomNavigationBarinlib/main.dartor the router config (GoRouter, AutoRoute, etc.). - Files named
home_page.dart,home_screen.dart,dashboard.dart.
- Read its source. Open the screen's widget file plus everything it imports from
lib/theme/,lib/widgets/, and any customThemeExtensions. NoteColorScheme,TextTheme, spacing constants, radius values, and any shared layout primitives. - Screenshot it on the emulator. Navigate with
tap-labelif needed, thenscripts/emu.sh screenshotand read the printed path. Scroll and capture each state. - Write the design tone in 3–5 specific bullets. What makes this app's screens feel like this app and not a generic Material default. Pick the axes that actually distinguish the reference screen — describe what's there, not what you wish were there:
- Mood — e.g. calm/restrained, playful/energetic, bold/arcade, soft/cozy, retro, neon.
- Fonts — which families and weights, where each is applied. Lock the list.
- Color — the full
ColorSchemestory: restrained palette vs. expressive, flat vs. gradient, saturation level, semantic tokens, anyThemeExtensions. - Surfaces — card backgrounds, borders, corner radius, elevation/shadow, blur.
- Hierarchy lever — how the app signals importance: weight, color, spacing, border, accent, illustration, or a mix.
- Motion — none, subtle Material defaults, or expressive (custom curves, hero transitions, Lottie/Rive).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 210 lines · 204 tokens per session scan A 9273255ef417
design-polish is a skill published in the GitHub repository ChunkyTofuStudios/flutter-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 204 tokens to every session and 3,490 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.