flutter-fix-layout-issues
Skill8 starsChanged 7 days agoMITView on GitHub
Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.
6 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- zhouycheng/skillsword for word, first seen Oct 13, 2026
- cuonnd/Claude_skillsword for word, first seen Oct 13, 2026
- enrique-lozano/Monekinword for word, first seen Oct 9, 2026
- flutter/skillsword for word, first seen Oct 8, 2026
- deretame/Breezeedited, first seen Oct 8, 2026
- hjdspace/SpaceCodeword for word, first seen Jul 21, 2026
Other versions6 projects use a version of this.
Word for word · 5
- flutter/skills★ 3.2k100% same
- enrique-lozano/Monekin★ 268100% same
- hjdspace/SpaceCode★ 4100% same
- zhouycheng/skills★ 1100% same
- cuonnd/Claude_skills★ 0100% same
Edited · 1
- deretame/Breeze★ 3k100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- Control CenterAGENTS.md
- clean-ddd-hexagonalSkill
- design-taste-frontendSkill
- flutter-add-integration-testSkill
- flutter-add-widget-previewSkill
- flutter-add-widget-testSkill
- flutter-apply-architecture-best-practicesSkill
- flutter-build-responsive-layoutSkill
- flutter-implement-json-serializationSkill
- flutter-setup-declarative-routingSkill
- flutter-setup-localizationSkill
- flutter-use-http-packageSkill
- full-output-enforcementSkill
- gpt-tasteSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- impeccableSkill
- minimalist-uiSkill
- redesign-existing-projectsSkill
- security-reviewSkill
- seo-aeo-best-practicesSkill
- seo-auditSkill
- translate-manualSkill
- unslop-textSkill
- version-bumpSkill
- impeccableSkill
The file
Files
Resolving Flutter Layout Errors
Contents
- Constraint Violation Diagnostics
- Layout Error Resolution Workflow
- Examples
Constraint Violation Diagnostics
Flutter layout operates on a strict rule: Constraints go down. Sizes go up. Parent sets position. Layout errors occur when this negotiation fails, typically due to unbounded constraints or unconstrained children.
Diagnose layout failures using the following error signatures:
- "Vertical viewport was given unbounded height": Triggered when a scrollable widget (
ListView,GridView) is placed inside an unconstrained vertical parent (Column). The parent provides infinite height, and the child attempts to expand infinitely. - "An InputDecorator...cannot have an unbounded width": Triggered when a
TextFieldorTextFormFieldis placed inside an unconstrained horizontal parent (Row). The text field attempts to determine its width based on infinite available space. - "RenderFlex overflowed": Triggered when a child of a
RoworColumnrequests a size larger than the parent's allocated constraints. Visually indicated by yellow and black warning stripes. - "Incorrect use of ParentData widget": Triggered when a
ParentDataWidgetis not a direct descendant of its required ancestor. (e.g.,Expandedoutside aFlex,Positionedoutside aStack). - "RenderBox was not laid out": A cascading side-effect error. Ignore this and look further up the stack trace for the primary constraint violation (usually an unbounded height/width error).
Layout Error Resolution Workflow
Copy and use this checklist to systematically resolve layout constraint violations.
Task Progress
- Run the application in debug mode to capture the exact layout exception in the console.
- Identify the primary error message (ignore cascading "RenderBox was not laid out" errors).
- Apply the conditional fix based on the specific error type:
- If "Vertical viewport was given unbounded height": Wrap the scrollable child (
ListView,GridView) in anExpandedwidget to consume remaining space, or wrap it in aSizedBoxto provide an absolute height constraint. - If "An InputDecorator...cannot have an unbounded width": Wrap the
TextFieldorTextFormFieldin anExpandedorFlexiblewidget. - If "RenderFlex overflowed": Constrain the overflowing child by wrapping it in an
Expandedwidget (to force it to fit) or aFlexiblewidget (to allow it to be smaller than the allocated space). - If "Incorrect use of ParentData widget": Move the
ParentDataWidgetto be a direct child of its required parent. EnsureExpanded/Flexibleare direct children ofRow/Column/Flex. EnsurePositionedis a direct child ofStack.
- If "Vertical viewport was given unbounded height": Wrap the scrollable child (
- Execute Flutter hot reload.
- Run validator -> review errors -> fix: Inspect the UI to verify the red/grey error screen or yellow/black overflow stripes are resolved. If new layout errors appear, repeat the workflow.
Examples
Fixing Unbounded Height (ListView in Column)
Input (Error State):
// Throws "Vertical viewport was given unbounded height"
Column(
children: <Widget>[
const Text('Header'),
ListView(
children: const <Widget>[
ListTile(title: Text('Item 1')),
ListTile(title: Text('Item 2')),
],
),
],
)Output (Resolved State):
// Wrap ListView in Expanded to constrain its height to the remaining Column space
Column(
children: <Widget>[
const Text('Header'),
Expanded(
child: ListView(
children: const <Widget>[
ListTile(title: Text('Item 1')),
ListTile(title: Text('Item 2')),
],
),
),
],
)Fixing Unbounded Width (TextField in Row)
Input (Error State):
// Throws "An InputDecorator...cannot have an unbounded width"
Row(
children: [
const Icon(Icons.search),
TextField(),
],
)Output (Resolved State):
// Wrap TextField in Expanded to constrain its width to the remaining Row space
Row(
children: [
const Icon(Icons.search),
Expanded(
child: TextField(),
),
],
)Fixing RenderFlex Overflow
Input (Error State):
// Throws "A RenderFlex overflowed by X pixels on the right"
Row(
children: [
const Icon(Icons.info),
const Text('This is a very long text string that will definitely overflow the available screen width and cause a RenderFlex error.'),
],
)Output (Resolved State):
// Wrap the Text widget in Expanded to force it to wrap within the available constraints
Row(
children: [
const Icon(Icons.info),
Expanded(
child: const Text('This is a very long text string that will definitely overflow the available screen width and cause a RenderFlex error.'),
),
],
)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.

