[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS76N4V0ERBECZC83X2EF6":3,"skill-same:01M7CS76N4V0ERBECZC83X2EF6":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CS76N4V0ERBECZC83X2EF6","flutter-atomic-components",null,"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","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Fflutter-atomic-components\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: flutter-atomic-components\ncategory: architecture\ndescription: 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\ntech_stack: Flutter\n---\n# Flutter Atomic Components\n\n## Overview\n\nThe 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.\n\n**Core principle:** Reuse before you build. Before writing any button\u002Fcard\u002Fchip\u002Finput\u002Flist-row, search the component library — hand-rolling a duplicate is a review-blocking defect.\n\n## The Levels\n\n| Level | What | Flutter example |\n|-------|------|-----------------|\n| **Atom** | Smallest reusable UI, no app logic | `AppButton`, `AppTextField`, `StatusChip`, `Avatar` |\n| **Molecule** | A few atoms forming a unit | `TaskCard` (title + chip + avatar), `SearchBar` |\n| **Organism** | Section built from molecules\u002Fatoms | `TaskList`, `BoardColumn`, `AppBarWithActions` |\n| **Screen** | Route wiring organisms to state | `TaskBoardScreen` |\n\nLibrary lives under `lib\u002Fui\u002Fcore\u002F{atoms,molecules,organisms}` — the official Flutter architecture layout — alongside `lib\u002Fui\u002Ffeatures\u002F\u003Cfeature>\u002F` for screen-specific composition; follow the app's existing layout if it differs (e.g. a flat `lib\u002Fui\u002Fatoms`).\n\n## INVENTORY.md\n\n`lib\u002Fui\u002Fcore\u002FINVENTORY.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.\n\n## Rules\n\n- **Before creating a component, check INVENTORY.md \u002F grep the library.** If an atom exists, use it. If it almost fits, extend it backward-compatibly — don't fork a near-duplicate.\n- **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.\n- **Atoms take data + callbacks, never talk to services.** `AppButton({required this.label, required this.onPressed})`. State\u002Fdata flows from the screen down.\n- **Atoms carry no outer margin of their own** — spacing between atoms is the parent's job (a `Row`\u002F`Column` with `spacing:`, or explicit `SizedBox`\u002Fpadding at the call site), so the same atom composes correctly in every context without fighting a built-in margin.\n- **Style through the theme** (see flutter-widget-architecture) so every instance of an atom looks identical.\n- **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.\n\n## Worked Example\n\nTask: \"add a priority badge to task cards.\" Wrong: add a `Container` with a colored label inline in `TaskCard`. Right:\n1. Check `INVENTORY.md` \u002F grep atoms → no `PriorityBadge`, but there is a `StatusChip` atom. Priority is distinct enough → add a `PriorityBadge` atom next to it, themed the same way.\n2. Compose it into the `TaskCard` molecule.\n3. Both the badge atom and the card get a widget test.\n4. Add the `PriorityBadge` line to `INVENTORY.md` in the same commit.\n\nNow every screen showing a task card gets the badge for free, consistently.\n\n## Common Mistakes\n\n- Inline `Container`\u002F`Text` styling that reinvents an existing atom.\n- A component with a network\u002Fservice call inside → not a component.\n- New component dumped at the wrong level (an organism where an atom belongs).\n- Breaking a shared atom's constructor without updating callers.\n- A new component added to the library with no `INVENTORY.md` line.\n- An atom with a built-in outer margin, so it looks right in one layout and wrong in the next.\n\n## Red Flags\n\n- Two screens render visually identical buttons built differently.\n- A \"widget\" imports a repository or http client.\n- Copy-pasted styled `Container`s across screens.\n- `lib\u002Fui\u002Fcore\u002F` (or the repo's component folder) with no `INVENTORY.md`.\n","# Flutter Atomic Components\n\n## Overview\n\nThe 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.\n\n**Core principle:** Reuse before you build. Before writing any button\u002Fcard\u002Fchip\u002Finput\u002Flist-row, search the component library — hand-rolling a duplicate is a review-blocking defect.\n\n## The Levels\n\n| Level | What | Flutter example |\n|-------|------|-----------------|\n| **Atom** | Smallest reusable UI, no app logic | `AppButton`, `AppTextField`, `StatusChip`, `Avatar` |\n| **Molecule** | A few atoms forming a unit | `TaskCard` (title + chip + avatar), `SearchBar` |\n| **Organism** | Section built from molecules\u002Fatoms | `TaskList`, `BoardColumn`, `AppBarWithActions` |\n| **Screen** | Route wiring organisms to state | `TaskBoardScreen` |\n\nLibrary lives under `lib\u002Fui\u002Fcore\u002F{atoms,molecules,organisms}` — the official Flutter architecture layout — alongside `lib\u002Fui\u002Ffeatures\u002F\u003Cfeature>\u002F` for screen-specific composition; follow the app's existing layout if it differs (e.g. a flat `lib\u002Fui\u002Fatoms`).\n\n## INVENTORY.md\n\n`lib\u002Fui\u002Fcore\u002FINVENTORY.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.\n\n## Rules\n\n- **Before creating a component, check INVENTORY.md \u002F grep the library.** If an atom exists, use it. If it almost fits, extend it backward-compatibly — don't fork a near-duplicate.\n- **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.\n- **Atoms take data + callbacks, never talk to services.** `AppButton({required this.label, required this.onPressed})`. State\u002Fdata flows from the screen down.\n- **Atoms carry no outer margin of their own** — spacing between atoms is the parent's job (a `Row`\u002F`Column` with `spacing:`, or explicit `SizedBox`\u002Fpadding at the call site), so the same atom composes correctly in every context without fighting a built-in margin.\n- **Style through the theme** (see flutter-widget-architecture) so every instance of an atom looks identical.\n- **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.\n\n## Worked Example\n\nTask: \"add a priority badge to task cards.\" Wrong: add a `Container` with a colored label inline in `TaskCard`. Right:\n1. Check `INVENTORY.md` \u002F grep atoms → no `PriorityBadge`, but there is a `StatusChip` atom. Priority is distinct enough → add a `PriorityBadge` atom next to it, themed the same way.\n2. Compose it into the `TaskCard` molecule.\n3. Both the badge atom and the card get a widget test.\n4. Add the `PriorityBadge` line to `INVENTORY.md` in the same commit.\n\nNow every screen showing a task card gets the badge for free, consistently.\n\n## Common Mistakes\n\n- Inline `Container`\u002F`Text` styling that reinvents an existing atom.\n- A component with a network\u002Fservice call inside → not a component.\n- New component dumped at the wrong level (an organism where an atom belongs).\n- Breaking a shared atom's constructor without updating callers.\n- A new component added to the library with no `INVENTORY.md` line.\n- An atom with a built-in outer margin, so it looks right in one layout and wrong in the next.\n\n## Red Flags\n\n- Two screens render visually identical buttons built differently.\n- A \"widget\" imports a repository or http client.\n- Copy-pasted styled `Container`s across screens.\n- `lib\u002Fui\u002Fcore\u002F` (or the repo's component folder) with no `INVENTORY.md`.\n",{"name":5,"category":24,"tech_stack":25,"description":7},"architecture","Flutter","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Fflutter-atomic-components",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill flutter-atomic-components",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill flutter-atomic-components",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill flutter-atomic-components","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Fflutter-atomic-components\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]