@flowstack-ui/agent-tools 0.1.0-bootstrap.0

package/public/packages/brick/0.1.11/components/table.txt

@@ -0,0 +1,183 @@
+# Table
+
+Source: @flowstack-ui/brick@0.1.11
+Kind: component
+ID: table
+
+# Table agent guide
+
+## Purpose
+
+Present finished static row-and-column relationships with native table semantics while Atom owns the semantic parts and sort metadata.
+
+## Use when
+
+- People need to compare values across meaningful columns in pricing, reports, invoices, inventories, audit results, or compact summaries.
+
+## Choose something else when
+
+- The region needs arrow-key cell navigation, row selection, editing, resizing, or another interactive composite model. Use Data Grid or an application-owned data tool.
+- The content is a sequence without meaningful column relationships or a label/value definition structure. Use List, Grid, Stack, or a semantic definition-list composition.
+- The narrow layout must convert rows into unrelated cards and no longer preserves column comparison. Use An application-owned alternate view with an explicit responsive policy.
+
+## Required composition
+
+- Compose optional Container > Root > Caption, Header, Body, and optional Footer; place Row inside each section and Head or Cell inside Row according to native table content rules.
+- Use Head with scope="row" for body row labels and keep the default column scope for header cells; use id and headers for complex associations.
+- Author Container explicitly when honest comparison needs horizontal overflow, and set the public minimum-inline-size token to the smallest width that preserves the column relationships.
+- When Table moves vertically, put the visible border and radius on the stable labelled Scroll Area viewport, use Table variant=line inside it, and keep persistent naming outside the moving viewport with aria-labelledby.
+- Put an independently named Button and optional decorative SortIndicator inside the active Head when the application owns sorting.
+
+## Rules
+
+- **MUST:** Preserve native table anatomy and meaningful row and column headers; do not rebuild tabular comparison with generic Grid, Stack, div, or ARIA role substitutes.
+- **MUST:** Keep Table static and readable; do not add row focus, whole-row activation, selection, arrow-key cell navigation, data mapping, filtering, pagination, editing, or virtualization to Table.
+- **MUST:** Author Table.Container or a separately labelled Scroll Area when wide comparison needs overflow; Root never inserts a wrapper and Table never hides columns or converts them into cards.
+- **MUST:** At narrow widths, preserve header-to-cell relationships, complete material values, and an understandable comparison path rather than merely stacking unrelated plan or record cards.
+- **MUST:** For bounded vertical scrolling, let the stable Scroll Area viewport own the visible border and radius; do not use a moving Table outline as the scroll-frame boundary.
+- **MUST:** Let the application sort data and pass sortDirection only to the active header; SortIndicator is decorative and never supplies the control, name, or behavior.
+- **MUST:** Load styles.css or core.css plus table.css.
+
+## Common mistakes
+
+- **Avoid:** Using generic layout components for a pricing matrix because custom positioning feels easier. **Instead:** Use Table's native Head and Cell relationships, then customize the closed recipes and public Table variables for the product-specific comparison.
+- **Avoid:** Hiding material columns on mobile or visually cloning labels into card rows. **Instead:** Contain honest horizontal overflow or provide a separately authored application view; do not destroy or fake the native column relationships.
+- **Avoid:** Making rows hoverable or clickable without a complete interaction owner. **Instead:** Keep rows structural and place independently named Brick links or buttons inside the appropriate cells.
+- **Avoid:** Using Table variant=outline as the visible frame inside a vertically scrolling viewport. **Instead:** Paint the stable Scroll Area viewport with Surface, use Table variant=line inside it, and connect a persistent external label with aria-labelledby.
+- **Avoid:** Using a visible recommendation color as the only explanation for a preferred pricing column. **Instead:** Keep the plan label and recommendation reason readable in ordinary text, then use Table paint only as supporting emphasis.
+
+## Validation checklist
+
+- Check caption or surrounding naming, header scope, cell associations, source order, plan or record labels, and independently named controls.
+- Check Container overflow, the authored minimum comparison width, stable viewport corners during vertical scrolling, sticky header boundaries when used, 320 CSS pixels, zoom, long content, RTL, and no page-level horizontal overflow.
+- Check light and dark themes, forced colors, row and column boundaries, recommendation meaning without color, focus visibility for interactive descendants, and CSS delivery.
+- Check that sorting, selection, filtering, pagination, data services, and responsive alternate-view policy remain application owned.
+
+## Related guidance
+
+- `@flowstack-ui/atom/agents/table`
+- `data-grid`
+- `tree-grid`
+- `scroll-area`
+- `button`
+- `badge`
+- `icon`
+- `text`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "table",
+  "name": "Table",
+  "package": "@flowstack-ui/brick",
+  "layer": "brick",
+  "kind": "component",
+  "purpose": "Present finished static row-and-column relationships with native table semantics while Atom owns the semantic parts and sort metadata.",
+  "useWhen": [
+    "People need to compare values across meaningful columns in pricing, reports, invoices, inventories, audit results, or compact summaries."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "The region needs arrow-key cell navigation, row selection, editing, resizing, or another interactive composite model.",
+      "useInstead": "Data Grid or an application-owned data tool"
+    },
+    {
+      "condition": "The content is a sequence without meaningful column relationships or a label/value definition structure.",
+      "useInstead": "List, Grid, Stack, or a semantic definition-list composition"
+    },
+    {
+      "condition": "The narrow layout must convert rows into unrelated cards and no longer preserves column comparison.",
+      "useInstead": "An application-owned alternate view with an explicit responsive policy"
+    }
+  ],
+  "composition": [
+    "Compose optional Container > Root > Caption, Header, Body, and optional Footer; place Row inside each section and Head or Cell inside Row according to native table content rules.",
+    "Use Head with scope=\"row\" for body row labels and keep the default column scope for header cells; use id and headers for complex associations.",
+    "Author Container explicitly when honest comparison needs horizontal overflow, and set the public minimum-inline-size token to the smallest width that preserves the column relationships.",
+    "When Table moves vertically, put the visible border and radius on the stable labelled Scroll Area viewport, use Table variant=line inside it, and keep persistent naming outside the moving viewport with aria-labelledby.",
+    "Put an independently named Button and optional decorative SortIndicator inside the active Head when the application owns sorting."
+  ],
+  "rules": [
+    {
+      "id": "table-native-relationships",
+      "level": "must",
+      "statement": "Preserve native table anatomy and meaningful row and column headers; do not rebuild tabular comparison with generic Grid, Stack, div, or ARIA role substitutes."
+    },
+    {
+      "id": "table-static-boundary",
+      "level": "must",
+      "statement": "Keep Table static and readable; do not add row focus, whole-row activation, selection, arrow-key cell navigation, data mapping, filtering, pagination, editing, or virtualization to Table."
+    },
+    {
+      "id": "table-explicit-overflow",
+      "level": "must",
+      "statement": "Author Table.Container or a separately labelled Scroll Area when wide comparison needs overflow; Root never inserts a wrapper and Table never hides columns or converts them into cards."
+    },
+    {
+      "id": "table-responsive-comparison",
+      "level": "must",
+      "statement": "At narrow widths, preserve header-to-cell relationships, complete material values, and an understandable comparison path rather than merely stacking unrelated plan or record cards."
+    },
+    {
+      "id": "table-vertical-scroll-boundary",
+      "level": "must",
+      "statement": "For bounded vertical scrolling, let the stable Scroll Area viewport own the visible border and radius; do not use a moving Table outline as the scroll-frame boundary."
+    },
+    {
+      "id": "table-sort-ownership",
+      "level": "must",
+      "statement": "Let the application sort data and pass sortDirection only to the active header; SortIndicator is decorative and never supplies the control, name, or behavior."
+    },
+    {
+      "id": "table-css",
+      "level": "must",
+      "statement": "Load styles.css or core.css plus table.css."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using generic layout components for a pricing matrix because custom positioning feels easier.",
+      "correction": "Use Table's native Head and Cell relationships, then customize the closed recipes and public Table variables for the product-specific comparison."
+    },
+    {
+      "mistake": "Hiding material columns on mobile or visually cloning labels into card rows.",
+      "correction": "Contain honest horizontal overflow or provide a separately authored application view; do not destroy or fake the native column relationships."
+    },
+    {
+      "mistake": "Making rows hoverable or clickable without a complete interaction owner.",
+      "correction": "Keep rows structural and place independently named Brick links or buttons inside the appropriate cells."
+    },
+    {
+      "mistake": "Using Table variant=outline as the visible frame inside a vertically scrolling viewport.",
+      "correction": "Paint the stable Scroll Area viewport with Surface, use Table variant=line inside it, and connect a persistent external label with aria-labelledby."
+    },
+    {
+      "mistake": "Using a visible recommendation color as the only explanation for a preferred pricing column.",
+      "correction": "Keep the plan label and recommendation reason readable in ordinary text, then use Table paint only as supporting emphasis."
+    }
+  ],
+  "validation": [
+    "Check caption or surrounding naming, header scope, cell associations, source order, plan or record labels, and independently named controls.",
+    "Check Container overflow, the authored minimum comparison width, stable viewport corners during vertical scrolling, sticky header boundaries when used, 320 CSS pixels, zoom, long content, RTL, and no page-level horizontal overflow.",
+    "Check light and dark themes, forced colors, row and column boundaries, recommendation meaning without color, focus visibility for interactive descendants, and CSS delivery.",
+    "Check that sorting, selection, filtering, pagination, data services, and responsive alternate-view policy remain application owned."
+  ],
+  "related": [
+    {
+      "kind": "package",
+      "package": "@flowstack-ui/atom",
+      "id": "table",
+      "versionPolicy": "installed-exact"
+    },
+    "data-grid",
+    "tree-grid",
+    "scroll-area",
+    "button",
+    "badge",
+    "icon",
+    "text"
+  ]
+}
+```

package/public/packages/brick/0.1.11/components/tabs.txt

@@ -0,0 +1,136 @@
+# Tabs
+
+Source: @flowstack-ui/brick@0.1.11
+Kind: component
+ID: tabs
+
+# Tabs agent guide
+
+## Purpose
+
+Style related in-page panel switching while Atom owns tab semantics, selection, roving focus, and indicator geometry.
+
+## Use when
+
+- A small set of related panels shares one page and one panel is normally active.
+
+## Choose something else when
+
+- Choices navigate to routes or multiple sections should remain open. Use Link/NavList or Accordion.
+
+## Required composition
+
+- Compose Trigger and optional Indicator inside List with matching Content values inside Root; lay out panel content with Brick components.
+- Keep the default panel inset for ordinary copy; use Content inset=none for edge-to-edge media or nested surfaces rather than overriding component CSS.
+- When a page-header control row visually continues the tab divider, keep unrelated controls outside List and let the surrounding Brick layout own the continuing decorative Divider.
+- Use List triggerRadius=none when line tabs need square underline geometry; the option applies to every variant and changes paint only.
+- When vertical tab semantics stay correct but mobile needs full-width content, use responsive Root layout stacked to side; do not change semantic orientation with CSS.
+- When the same vertical selector needs a compact mobile grid, use responsive List columns (for example, initial 2 and lg 1) rather than application selectors; keyboard orientation remains vertical.
+- When a solid or soft List is nested inside a clipping parent that owns the outer corners, use List radius=none rather than overriding Tabs selectors; add triggerRadius=default only when individual Trigger surfaces should remain rounded.
+- Keep the shipped solid and soft List inset at or above the complete focus-ring reach; do not reduce it inside a clipping Card or Surface.
+
+## Rules
+
+- **MUST:** Use Tabs only for related in-page panels, not to imitate a site navigation underline.
+- **MUST:** Define a deliberate narrow-width overflow or wrapping policy without clipping triggers or indicator focus.
+- **MUST:** Treat List columns as visual placement only; keep DOM order and the semantic orientation that matches the intended arrow keys.
+- **MUST:** Treat List radius and Trigger radius as independent visual geometry only; neither may alter inset, selection, focus, orientation, columns, or keyboard behavior.
+- **MUST:** For line Tabs, keep active label and icon paint on primary text and reserve accent paint for the selected edge or authored metadata such as Badge.
+- **MUST:** Load styles.css or core.css plus tabs.css.
+
+## Common mistakes
+
+- **Avoid:** Using Tabs for routes, putting sorting or actions inside List to extend its divider, clipping focus/indicator edges, or mismatching Trigger and Content values. **Instead:** Use navigation links for routes, keep unrelated controls outside the tablist, continue shared decorative edges with the surrounding Brick layout, and keep complete paired tab anatomy.
+
+## Validation checklist
+
+- Check automatic/manual activation, arrows, Home/End, Enter/Space, disabled, controlled, keep-mounted, overflow, complete focus rings at every List edge and inside clipping parents, themes, zoom, and RTL.
+- Confirm CSS is loaded.
+
+## Related guidance
+
+- `accordion`
+- `navigation-menu`
+- `bottom-navigation`
+- `scroll-area`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "tabs",
+  "name": "Tabs",
+  "package": "@flowstack-ui/brick",
+  "layer": "brick",
+  "kind": "component",
+  "purpose": "Style related in-page panel switching while Atom owns tab semantics, selection, roving focus, and indicator geometry.",
+  "useWhen": [
+    "A small set of related panels shares one page and one panel is normally active."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "Choices navigate to routes or multiple sections should remain open.",
+      "useInstead": "Link/NavList or Accordion"
+    }
+  ],
+  "composition": [
+    "Compose Trigger and optional Indicator inside List with matching Content values inside Root; lay out panel content with Brick components.",
+    "Keep the default panel inset for ordinary copy; use Content inset=none for edge-to-edge media or nested surfaces rather than overriding component CSS.",
+    "When a page-header control row visually continues the tab divider, keep unrelated controls outside List and let the surrounding Brick layout own the continuing decorative Divider.",
+    "Use List triggerRadius=none when line tabs need square underline geometry; the option applies to every variant and changes paint only.",
+    "When vertical tab semantics stay correct but mobile needs full-width content, use responsive Root layout stacked to side; do not change semantic orientation with CSS.",
+    "When the same vertical selector needs a compact mobile grid, use responsive List columns (for example, initial 2 and lg 1) rather than application selectors; keyboard orientation remains vertical.",
+    "When a solid or soft List is nested inside a clipping parent that owns the outer corners, use List radius=none rather than overriding Tabs selectors; add triggerRadius=default only when individual Trigger surfaces should remain rounded.",
+    "Keep the shipped solid and soft List inset at or above the complete focus-ring reach; do not reduce it inside a clipping Card or Surface."
+  ],
+  "rules": [
+    {
+      "id": "tabs-related-panels",
+      "level": "must",
+      "statement": "Use Tabs only for related in-page panels, not to imitate a site navigation underline."
+    },
+    {
+      "id": "tabs-overflow",
+      "level": "must",
+      "statement": "Define a deliberate narrow-width overflow or wrapping policy without clipping triggers or indicator focus."
+    },
+    {
+      "id": "tabs-columns-semantics",
+      "level": "must",
+      "statement": "Treat List columns as visual placement only; keep DOM order and the semantic orientation that matches the intended arrow keys."
+    },
+    {
+      "id": "tabs-radius-visual-only",
+      "level": "must",
+      "statement": "Treat List radius and Trigger radius as independent visual geometry only; neither may alter inset, selection, focus, orientation, columns, or keyboard behavior."
+    },
+    {
+      "id": "tabs-line-selection-paint",
+      "level": "must",
+      "statement": "For line Tabs, keep active label and icon paint on primary text and reserve accent paint for the selected edge or authored metadata such as Badge."
+    },
+    {
+      "id": "tabs-css",
+      "level": "must",
+      "statement": "Load styles.css or core.css plus tabs.css."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using Tabs for routes, putting sorting or actions inside List to extend its divider, clipping focus/indicator edges, or mismatching Trigger and Content values.",
+      "correction": "Use navigation links for routes, keep unrelated controls outside the tablist, continue shared decorative edges with the surrounding Brick layout, and keep complete paired tab anatomy."
+    }
+  ],
+  "validation": [
+    "Check automatic/manual activation, arrows, Home/End, Enter/Space, disabled, controlled, keep-mounted, overflow, complete focus rings at every List edge and inside clipping parents, themes, zoom, and RTL.",
+    "Confirm CSS is loaded."
+  ],
+  "related": [
+    "accordion",
+    "navigation-menu",
+    "bottom-navigation",
+    "scroll-area"
+  ]
+}
+```

package/public/packages/brick/0.1.11/components/text.txt

@@ -0,0 +1,148 @@
+# Text
+
+Source: @flowstack-ui/brick@0.1.11
+Kind: component
+ID: text
+
+# Text agent guide
+
+## Purpose
+
+Apply Brick typography roles, tones, weight, alignment, wrapping, and deliberate transforms through flexible Text or named semantic text exports.
+
+## Use when
+
+- Interface copy needs Brick typography, including headings, paragraphs, short editorial eyebrows, captions, metadata, or inline text. Prefer Heading, Paragraph, Caption, and Eyebrow for their common roles; use Text for a different deliberate semantic/visual pairing.
+
+## Choose something else when
+
+- A component such as Button, Link, Field.Label, Card.Title, or Badge already owns the text role. Use that component's named text part.
+
+## Required composition
+
+- Choose the named semantic export when it fits. Heading requires an explicit level and keeps that level independent from its visual variant. Otherwise choose Text's semantic element first, then its closest visual variant and tone. Keep inline components that complete the same sentence inside that text owner, and use Stack only for separately meaningful text peers.
+
+## Rules
+
+- **MUST:** Do not choose heading or paragraph semantics solely from the desired font size. Use the display scale, responsive visual variant, or responsive logical alignment without changing the correct semantic level.
+- **MUST:** Author real names and titles with their correct casing. Use transform only for deliberate visual presentation; CSS capitalize is not language-aware title case and must not repair registry or product content.
+- **MUST:** Prefer Heading, Paragraph, Caption, or Eyebrow for ordinary roles; use Text when their fixed semantic host or restricted visual family does not fit.
+- **MUST:** Use Text for standalone styled interface copy instead of native spans plus duplicate typography CSS.
+- **MUST:** Preserve readable body sizing, line height, measure, contrast, and user font scaling.
+- **MUST:** Reserve variant=eyebrow for short labels that introduce a nearby heading; do not select it merely to make unrelated copy smaller. Use body text for explanatory sentences and Badge for passive status or category content.
+- **MUST:** Use tone=inherit when Text is intentionally composed inside a parent such as Badge that owns the foreground and contrast relationship.
+- **MUST:** Keep a Link or other inline component that completes one sentence inside the semantic Text paragraph and let it inherit the surrounding typography and natural wrapping.
+- **SHOULD:** Give separately meaningful inline peer labels compatible typography metrics and arrange them with HStack gap rather than literal spaces or manual positional offsets.
+- **MUST:** Load styles.css or core.css plus text.css.
+
+## Common mistakes
+
+- **Avoid:** Using five spans to build brand text, repeatedly spelling ordinary headings and paragraphs as Text plus as, using capitalize to repair authored titles, selecting all-caps eyebrow styling for paragraph descriptions, allowing nested Text to override a parent's foreground, splitting one sentence into layout siblings, or aligning independent peer labels with literal whitespace. **Instead:** Use the named semantic exports where they fit, author correct casing, reserve transforms and display treatments for their intended roles, inherit the owning foreground, keep one sentence in one text flow, and use HStack gap only between separate peers.
+
+## Validation checklist
+
+- Check heading order, semantics, responsive visual-recipe changes at Brick breakpoints, line length, wrapping, truncation, user font scaling, zoom, contrast, themes, and RTL.
+- Confirm named exports render one correct native host, Heading level follows document structure, transformed text preserves authored content in the DOM, inline sentence content remains inside its semantic owner, independent peer labels align without positional CSS, parent foreground ownership is not bypassed, and CSS is loaded.
+
+## Related guidance
+
+- `stack`
+- `link`
+- `card`
+- `field`
+- `badge`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "text",
+  "name": "Text",
+  "package": "@flowstack-ui/brick",
+  "layer": "brick",
+  "kind": "component",
+  "purpose": "Apply Brick typography roles, tones, weight, alignment, wrapping, and deliberate transforms through flexible Text or named semantic text exports.",
+  "useWhen": [
+    "Interface copy needs Brick typography, including headings, paragraphs, short editorial eyebrows, captions, metadata, or inline text. Prefer Heading, Paragraph, Caption, and Eyebrow for their common roles; use Text for a different deliberate semantic/visual pairing."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "A component such as Button, Link, Field.Label, Card.Title, or Badge already owns the text role.",
+      "useInstead": "that component's named text part"
+    }
+  ],
+  "composition": [
+    "Choose the named semantic export when it fits. Heading requires an explicit level and keeps that level independent from its visual variant. Otherwise choose Text's semantic element first, then its closest visual variant and tone. Keep inline components that complete the same sentence inside that text owner, and use Stack only for separately meaningful text peers."
+  ],
+  "rules": [
+    {
+      "id": "text-semantics",
+      "level": "must",
+      "statement": "Do not choose heading or paragraph semantics solely from the desired font size. Use the display scale, responsive visual variant, or responsive logical alignment without changing the correct semantic level."
+    },
+    {
+      "id": "text-authored-case",
+      "level": "must",
+      "statement": "Author real names and titles with their correct casing. Use transform only for deliberate visual presentation; CSS capitalize is not language-aware title case and must not repair registry or product content."
+    },
+    {
+      "id": "text-named-roles",
+      "level": "must",
+      "statement": "Prefer Heading, Paragraph, Caption, or Eyebrow for ordinary roles; use Text when their fixed semantic host or restricted visual family does not fit."
+    },
+    {
+      "id": "text-brick-first",
+      "level": "must",
+      "statement": "Use Text for standalone styled interface copy instead of native spans plus duplicate typography CSS."
+    },
+    {
+      "id": "text-readable",
+      "level": "must",
+      "statement": "Preserve readable body sizing, line height, measure, contrast, and user font scaling."
+    },
+    {
+      "id": "text-eyebrow",
+      "level": "must",
+      "statement": "Reserve variant=eyebrow for short labels that introduce a nearby heading; do not select it merely to make unrelated copy smaller. Use body text for explanatory sentences and Badge for passive status or category content."
+    },
+    {
+      "id": "text-inherit-parent-foreground",
+      "level": "must",
+      "statement": "Use tone=inherit when Text is intentionally composed inside a parent such as Badge that owns the foreground and contrast relationship."
+    },
+    {
+      "id": "text-inline-sentence",
+      "level": "must",
+      "statement": "Keep a Link or other inline component that completes one sentence inside the semantic Text paragraph and let it inherit the surrounding typography and natural wrapping."
+    },
+    {
+      "id": "text-inline-peers",
+      "level": "should",
+      "statement": "Give separately meaningful inline peer labels compatible typography metrics and arrange them with HStack gap rather than literal spaces or manual positional offsets."
+    },
+    {
+      "id": "text-css",
+      "level": "must",
+      "statement": "Load styles.css or core.css plus text.css."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using five spans to build brand text, repeatedly spelling ordinary headings and paragraphs as Text plus as, using capitalize to repair authored titles, selecting all-caps eyebrow styling for paragraph descriptions, allowing nested Text to override a parent's foreground, splitting one sentence into layout siblings, or aligning independent peer labels with literal whitespace.",
+      "correction": "Use the named semantic exports where they fit, author correct casing, reserve transforms and display treatments for their intended roles, inherit the owning foreground, keep one sentence in one text flow, and use HStack gap only between separate peers."
+    }
+  ],
+  "validation": [
+    "Check heading order, semantics, responsive visual-recipe changes at Brick breakpoints, line length, wrapping, truncation, user font scaling, zoom, contrast, themes, and RTL.",
+    "Confirm named exports render one correct native host, Heading level follows document structure, transformed text preserves authored content in the DOM, inline sentence content remains inside its semantic owner, independent peer labels align without positional CSS, parent foreground ownership is not bypassed, and CSS is loaded."
+  ],
+  "related": [
+    "stack",
+    "link",
+    "card",
+    "field",
+    "badge"
+  ]
+}
+```

package/public/packages/brick/0.1.11/components/textarea.txt

@@ -0,0 +1,101 @@
+# Textarea
+
+Source: @flowstack-ui/brick@0.1.11
+Kind: component
+ID: textarea
+
+# Textarea agent guide
+
+## Purpose
+
+Render finished native multi-line text entry with Brick sizing, states, resize policy, and Atom field integration.
+
+## Use when
+
+- The user enters sentences, paragraphs, notes, or other multi-line text.
+
+## Choose something else when
+
+- The expected value is short and single-line. Use Input.
+
+## Required composition
+
+- Place Textarea inside one Field.Root after Field.Label and add description or character guidance when useful.
+
+## Rules
+
+- **MUST:** Use a persistent accessible label.
+- **MUST:** Load styles.css or core.css plus textarea.css and field.css when composed with Field.
+
+## Common mistakes
+
+- **Avoid:** Using a single-line Input for long freeform content. **Instead:** Use Textarea and allow a usable multi-line measure.
+
+## Validation checklist
+
+- Inspect label, name, and messaging relationships.
+- Test multi-line entry, resize policy, narrow widths, invalid/disabled states, and contrast.
+
+## Related guidance
+
+- `@flowstack-ui/atom/agents/textarea`
+- `field`
+- `input`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "textarea",
+  "name": "Textarea",
+  "package": "@flowstack-ui/brick",
+  "layer": "brick",
+  "kind": "component",
+  "purpose": "Render finished native multi-line text entry with Brick sizing, states, resize policy, and Atom field integration.",
+  "useWhen": [
+    "The user enters sentences, paragraphs, notes, or other multi-line text."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "The expected value is short and single-line.",
+      "useInstead": "Input"
+    }
+  ],
+  "composition": [
+    "Place Textarea inside one Field.Root after Field.Label and add description or character guidance when useful."
+  ],
+  "rules": [
+    {
+      "id": "textarea-label",
+      "level": "must",
+      "statement": "Use a persistent accessible label."
+    },
+    {
+      "id": "textarea-css",
+      "level": "must",
+      "statement": "Load styles.css or core.css plus textarea.css and field.css when composed with Field."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using a single-line Input for long freeform content.",
+      "correction": "Use Textarea and allow a usable multi-line measure."
+    }
+  ],
+  "validation": [
+    "Inspect label, name, and messaging relationships.",
+    "Test multi-line entry, resize policy, narrow widths, invalid/disabled states, and contrast."
+  ],
+  "related": [
+    {
+      "kind": "package",
+      "package": "@flowstack-ui/atom",
+      "id": "textarea",
+      "versionPolicy": "installed-exact"
+    },
+    "field",
+    "input"
+  ]
+}
+```