Add Flutter Docusaurus Locale
matthiasn/lotti
Add, complete, or audit a locale across a Flutter application's ARB catalogs and a localized Docusaurus manual, including generated localization code, locale selectors, native platform declarations…
A skill your agent uses when adding or reusing Flutter UI - organize widgets as atoms, molecules, and organisms in a shared library and never hand-roll a component that already exists
Install Flutter Atomic Components
$ npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install makifbaysal/tasktrooper flutter-atomic-components --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/agents/mobile-developer/skills/flutter-atomic-components .claude/skills/flutter-atomic-components && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "flutter-atomic-components" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/mobile-developer/skills/flutter-atomic-components into .claude/skills/flutter-atomic-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-atomic-components", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/mobile-developer/skills/flutter-atomic-componentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install makifbaysal/tasktrooper flutter-atomic-components --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .agents/skills && cp -r skills-src/catalog/agents/mobile-developer/skills/flutter-atomic-components .agents/skills/flutter-atomic-components && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "flutter-atomic-components" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/mobile-developer/skills/flutter-atomic-components into .agents/skills/flutter-atomic-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-atomic-components", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install makifbaysal/tasktrooper flutter-atomic-components --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/catalog/agents/mobile-developer/skills/flutter-atomic-components .cursor/skills/flutter-atomic-components && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "flutter-atomic-components" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/mobile-developer/skills/flutter-atomic-components into .cursor/skills/flutter-atomic-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-atomic-components", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/makifbaysal/tasktrooper.git --path catalog/agents/mobile-developer/skills/flutter-atomic-components--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install makifbaysal/tasktrooper flutter-atomic-components --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/catalog/agents/mobile-developer/skills/flutter-atomic-components .gemini/skills/flutter-atomic-components && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "flutter-atomic-components" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/mobile-developer/skills/flutter-atomic-components into .gemini/skills/flutter-atomic-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-atomic-components", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install makifbaysal/tasktrooper flutter-atomic-componentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .github/skills && cp -r skills-src/catalog/agents/mobile-developer/skills/flutter-atomic-components .github/skills/flutter-atomic-components && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "flutter-atomic-components" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/mobile-developer/skills/flutter-atomic-components into .github/skills/flutter-atomic-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-atomic-components", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install makifbaysal/tasktrooper flutter-atomic-components --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/catalog/agents/mobile-developer/skills/flutter-atomic-components .opencode/skills/flutter-atomic-components && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "flutter-atomic-components" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/mobile-developer/skills/flutter-atomic-components into .opencode/skills/flutter-atomic-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-atomic-components", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
flutter-atomic-components- GitHub stars
- 109
- Token cost
- ~1.1k tokens
- SKILL.md length
- 544 words
- Files
- 1
- Skills in repo
- 99
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when adding or reusing Flutter UI - organize widgets as atoms, molecules, and organisms in a shared library and never hand-roll a component that already exists
- Works in 4 steps: Check INVENTORY.md / grep atoms → no… → Compose it into the TaskCard molecule. → Both the badge atom and the card get a… → …
- Reusing Flutter UI - organize widgets as atoms
- SKILL.md covers Overview, The Levels, INVENTORY.md and Rules, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Flutter Atomic Components is an agent skill from makifbaysal/tasktrooper. Use when adding or reusing Flutter UI - organize widgets as atoms, molecules, and organisms in a shared library and never hand-roll a component that already exists
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Mobile, covering Cross-platform mobile apps. It works with Flutter. The repository describes itself as: Local-first agent platform: board + role agents + agent CLI runs (Claude Code, Cursor, Antigravity, OpenCode) or local and API models (Ollama, LM Studio), all on your own Mac. The licence is Apache-2.0.
When your agent uses it
- Reusing Flutter UI - organize widgets as atoms
- Organisms in a shared library and never hand-roll a component that already exists
Example prompts
- “/flutter-atomic-components”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Check INVENTORY.md / grep atoms → no PriorityBadge, but there is a StatusChip atom. Priority is distinct enough → add a PriorityBadge atom…
- Compose it into the TaskCard molecule.
- Both the badge atom and the card get a widget test.
- Add the PriorityBadge line to INVENTORY.md in the same commit.
What it can do on your machine
Read from SKILL.md and the folder at commit 09f6258. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Flutter Atomic Components loads about 1.1k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 544 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from makifbaysal/tasktrooper at commit 09f6258, republished under its Apache-2.0 licence (© makifbaysal). 544 words, ~1,055 tokens.
Download SKILL.mdSave it as
.claude/skills/flutter-atomic-components/SKILL.md (or your agent's skills folder).- name
- flutter-atomic-components
- description
- Use when adding or reusing Flutter UI - organize widgets as atoms, molecules, and organisms in a shared library and never hand-roll a component that already exists
- category
- architecture
- tech_stack
- Flutter
Flutter Atomic Components
Overview
The same atomic-design discipline the web app follows applies to Flutter: build a shared component library organized by level and compose screens from it. This keeps the app visually consistent and makes screens small.
Core principle: Reuse before you build. Before writing any button/card/chip/input/list-row, search the component library — hand-rolling a duplicate is a review-blocking defect.
The Levels
| Level | What | Flutter example |
|---|---|---|
| Atom | Smallest reusable UI, no app logic | AppButton, AppTextField, StatusChip, Avatar |
| Molecule | A few atoms forming a unit | TaskCard (title + chip + avatar), SearchBar |
| Organism | Section built from molecules/atoms | TaskList, BoardColumn, AppBarWithActions |
| Screen | Route wiring organisms to state | TaskBoardScreen |
Library lives under lib/ui/core/{atoms,molecules,organisms} — the official Flutter architecture layout — alongside lib/ui/features/<feature>/ for screen-specific composition; follow the app's existing layout if it differs (e.g. a flat lib/ui/atoms).
INVENTORY.md
lib/ui/core/INVENTORY.md: header One line per component: level · name · purpose · variants, one bullet per component, added in the same commit that creates or meaningfully changes it. Check it before building anything — it's faster than grepping the tree and it's the thing the next task's agent will actually read. If the repo has no component library or theme yet, load mobile-design-system-foundation first.
Rules
- Before creating a component, check INVENTORY.md / grep the library. If an atom exists, use it. If it almost fits, extend it backward-compatibly — don't fork a near-duplicate.
- Place new components at the correct level. A button is an atom; a card composed of atoms is a molecule. A "component" that fetches data is not a component — split the presentation out.
- Atoms take data + callbacks, never talk to services.
AppButton({required this.label, required this.onPressed}). State/data flows from the screen down. - Atoms carry no outer margin of their own — spacing between atoms is the parent's job (a
Row/Columnwithspacing:, or explicitSizedBox/padding at the call site), so the same atom composes correctly in every context without fighting a built-in margin. - Style through the theme (see flutter-widget-architecture) so every instance of an atom looks identical.
- Changing a shared atom: grep every call site first; keep the change backward-compatible or update all callers in the same task. The build must stay green.
Show full SKILL.md (196 more words)Show less
Worked Example
Task: "add a priority badge to task cards." Wrong: add a Container with a colored label inline in TaskCard. Right:
- Check
INVENTORY.md/ grep atoms → noPriorityBadge, but there is aStatusChipatom. Priority is distinct enough → add aPriorityBadgeatom next to it, themed the same way. - Compose it into the
TaskCardmolecule. - Both the badge atom and the card get a widget test.
- Add the
PriorityBadgeline toINVENTORY.mdin the same commit.
Now every screen showing a task card gets the badge for free, consistently.
Common Mistakes
- Inline
Container/Textstyling that reinvents an existing atom. - A component with a network/service call inside → not a component.
- New component dumped at the wrong level (an organism where an atom belongs).
- Breaking a shared atom's constructor without updating callers.
- A new component added to the library with no
INVENTORY.mdline. - An atom with a built-in outer margin, so it looks right in one layout and wrong in the next.
Red Flags
- Two screens render visually identical buttons built differently.
- A "widget" imports a repository or http client.
- Copy-pasted styled
Containers across screens. lib/ui/core/(or the repo's component folder) with noINVENTORY.md.
© makifbaysal, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in catalog/agents/mobile-developer/skills/flutter-atomic-components of makifbaysal/tasktrooper.
Open the folder on GitHubat commit 09f6258
Compare with similar skills
Flutter Atomic Components next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Flutter Atomic Components this skillmakifbaysal/tasktrooper | 109 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Flutter Docusaurus Localematthiasn/lotti | 1.2k | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Tm Launcher DesignFar-Se/tabame | 372 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Mobile App UI Designceorkm/mobile-app-ui-design | 400 | — | ~2k | Automated safety check: Pass | None | |
| Marionette Flutter Drive Appleancodepl/marionette_mcp | 473 | — | ~11k | Automated safety check: Pass | Apache-2.0 | |
| Flutter ScreenshotJustLookAtNow/pt_mate | 503 | — | ~511 | Automated safety check: Pass | MIT |
Similar skills
Tm Launcher Design
Far-Se/tabame
Create or revise Tabame's Flutter launcher designs: frames, search bars, result rows, palettes, typography, and action dialogs.
Mobile App UI Design
ceorkm/mobile-app-ui-design
Design high-quality mobile app UI/UX screens, flows, and components.
Marionette Flutter Drive App
leancodepl/marionette_mcp
Set up and drive a running Flutter app (debug or profile) with Marionette — an AI agent's hands and eyes for the app.
Flutter Screenshot
JustLookAtNow/pt_mate
Capture and show two Flutter UI screenshots for this project: one landscape/large-screen preview and one portrait/mobile preview, without using Flutter Web.
Flutter Init
bear2u/my-skills
A skill your agent uses when user wants to create a new Flutter project (Todo/Habit/Note/Expense/Custom domain) with Clean Architecture, Riverpod 3.0, Drift, and modern Flutter stack
More from makifbaysal/tasktrooper
All 99 skills in this repoAPI Contract Testing
makifbaysal/tasktrooper
A skill your agent uses when a task adds or changes an HTTP endpoint, its request/response shape, status codes, auth or error format - the request matrix, curl templates and what counts as a…
Acceptance Criteria Gwt
makifbaysal/tasktrooper
A skill your agent uses when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases
Accessibility Check
makifbaysal/tasktrooper
A skill your agent uses when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
Analiz Gate
makifbaysal/tasktrooper
A skill your agent uses when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation
Analiz HTML Report
makifbaysal/tasktrooper
A skill your agent uses when you write or revise the analiz deliverable - the ONE self-contained HTML report (spec and plan as sections) a human reviews passage by passage
Analiz Human Review Gate
makifbaysal/tasktrooper
A skill your agent uses when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analizreview column
Related
Works with
Categories
Questions about Flutter Atomic Components
What does Flutter Atomic Components do?
A skill your agent uses when adding or reusing Flutter UI - organize widgets as atoms, molecules, and organisms in a shared library and never hand-roll a component that already exists. Flutter Atomic Components is an agent skill from makifbaysal/tasktrooper.
When should I use Flutter Atomic Components?
Flutter Atomic Components fits situations like: reusing Flutter UI - organize widgets as atoms; organisms in a shared library and never hand-roll a component that already exists.
How do I install Flutter Atomic Components in Claude Code?
Run `npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a claude-code`. Or copy the skill folder (catalog/agents/mobile-developer/skills/flutter-atomic-components in makifbaysal/tasktrooper) into .claude/skills/flutter-atomic-components in your project. Claude Code loads it when a task matches its description.
How do I install Flutter Atomic Components in Codex?
Run `npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a codex`. Or copy the skill folder (catalog/agents/mobile-developer/skills/flutter-atomic-components in makifbaysal/tasktrooper) into .agents/skills/flutter-atomic-components in your project. Codex loads it when a task matches its description.
Can I use Flutter Atomic Components in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add makifbaysal/tasktrooper --skill flutter-atomic-components -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flutter-atomic-components, .gemini/skills/flutter-atomic-components, .github/skills/flutter-atomic-components and .opencode/skills/flutter-atomic-components in your project.
What does Flutter Atomic Components need to run?
SKILL.md names no scripts, command-line tools or credentials: Flutter Atomic Components is instructions for the agent only.
Does Flutter Atomic Components access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Flutter Atomic Components safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Flutter Atomic Components use?
Flutter Atomic Components is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Flutter Atomic Components use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Flutter Atomic Components?
Skills that share tags, products or a category with Flutter Atomic Components: Add Flutter Docusaurus Locale (matthiasn/lotti, 1.2k stars), Tm Launcher Design (Far-Se/tabame, 372 stars), Mobile App UI Design (ceorkm/mobile-app-ui-design, 400 stars) and Marionette Flutter Drive App (leancodepl/marionette_mcp, 473 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Flutter Atomic Components?
makifbaysal (a GitHub user) maintains it in makifbaysal/tasktrooper, which has 109 GitHub stars. The repository holds 99 skills in this directory. The repository was last updated on October 7, 2026.
Source: makifbaysal/tasktrooper on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.