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

package/public/packages/atom/0.24.0/components/drag-drop.txt

@@ -0,0 +1,141 @@
+# DragDrop
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: drag-drop
+
+# DragDrop agent guide
+
+## Purpose
+
+Provide headless same-document drag lifecycle, pointer and keyboard input, target resolution, cancellation, and accessible announcements for components that define their own movement rules.
+
+## Use when
+
+- Building a reusable collection component whose items move between explicit same-document targets and whose product-specific rules cannot be represented by Reorder.
+
+## Choose something else when
+
+- The user is only arranging a single linear list. Use Reorder.
+- The task is automatic data sorting, native file transfer, freeform canvas placement, or movement between tree parents. Use the relevant collection, file, canvas, or tree-specific behavior.
+
+## Required composition
+
+- Place Draggable and DropTarget parts within Root; nest Handle inside each Draggable and provide a human label for every source and target.
+- Provide localized Root instructions and message functions, and convert onDragEnd details into application or adapter state only after a valid release.
+- Add a visible simple-pointer alternative appropriate to the surrounding interface; generic dragging alone does not satisfy that requirement.
+
+## Rules
+
+- **MUST:** Use an explicitly labelled native Handle and preserve its focus across keyed item movement.
+- **MUST:** Commit pointer movement only on release over a valid target; pointer cancellation, Escape, and invalid release must preserve application order.
+- **MUST:** Provide a visible non-dragging simple-pointer operation for every movement job.
+- **MUST:** Use stable application identities for source and target values; never use a changing visual index as identity.
+- **SHOULD:** Prefer a collection-specific adapter such as Reorder, DataGrid, Tree, or Kanban over exposing generic drag events directly in finished application UI.
+
+## Common mistakes
+
+- **Avoid:** Using DragDrop directly for a normal sortable list or treating data sort order as manual item order. **Instead:** Use Reorder for one-dimensional manual arrangement and keep query sorting separate.
+- **Avoid:** Depending on drag gestures or keyboard movement as the only alternatives. **Instead:** Add visible one-activation movement controls or another contextual simple-pointer alternative.
+- **Avoid:** Mutating application objects during pointer movement. **Instead:** Render transient data attributes during movement and update controlled application state only from a completed drop.
+
+## Validation checklist
+
+- Verify mouse, pen, touch-delay, keyboard, Escape, pointer cancellation, invalid release, and focus continuity.
+- Verify localized instructions and announcements use human labels and one-based positions.
+- Verify disabled/read-only sources and targets, vertical/horizontal direction, RTL, zoom, and a visible simple-pointer alternative.
+- Verify values remain stable while the surrounding collection reorders or updates.
+
+## Related guidance
+
+- `reorder`
+- `collection`
+- `data-grid`
+- `tree`
+- `file-upload`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "drag-drop",
+  "name": "DragDrop",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Provide headless same-document drag lifecycle, pointer and keyboard input, target resolution, cancellation, and accessible announcements for components that define their own movement rules.",
+  "useWhen": [
+    "Building a reusable collection component whose items move between explicit same-document targets and whose product-specific rules cannot be represented by Reorder."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "The user is only arranging a single linear list.",
+      "useInstead": "Reorder"
+    },
+    {
+      "condition": "The task is automatic data sorting, native file transfer, freeform canvas placement, or movement between tree parents.",
+      "useInstead": "the relevant collection, file, canvas, or tree-specific behavior"
+    }
+  ],
+  "composition": [
+    "Place Draggable and DropTarget parts within Root; nest Handle inside each Draggable and provide a human label for every source and target.",
+    "Provide localized Root instructions and message functions, and convert onDragEnd details into application or adapter state only after a valid release.",
+    "Add a visible simple-pointer alternative appropriate to the surrounding interface; generic dragging alone does not satisfy that requirement."
+  ],
+  "rules": [
+    {
+      "id": "drag-drop-explicit-handle",
+      "level": "must",
+      "statement": "Use an explicitly labelled native Handle and preserve its focus across keyed item movement."
+    },
+    {
+      "id": "drag-drop-release-cancel",
+      "level": "must",
+      "statement": "Commit pointer movement only on release over a valid target; pointer cancellation, Escape, and invalid release must preserve application order."
+    },
+    {
+      "id": "drag-drop-alternative",
+      "level": "must",
+      "statement": "Provide a visible non-dragging simple-pointer operation for every movement job."
+    },
+    {
+      "id": "drag-drop-stable-identity",
+      "level": "must",
+      "statement": "Use stable application identities for source and target values; never use a changing visual index as identity."
+    },
+    {
+      "id": "drag-drop-context-boundary",
+      "level": "should",
+      "statement": "Prefer a collection-specific adapter such as Reorder, DataGrid, Tree, or Kanban over exposing generic drag events directly in finished application UI."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using DragDrop directly for a normal sortable list or treating data sort order as manual item order.",
+      "correction": "Use Reorder for one-dimensional manual arrangement and keep query sorting separate."
+    },
+    {
+      "mistake": "Depending on drag gestures or keyboard movement as the only alternatives.",
+      "correction": "Add visible one-activation movement controls or another contextual simple-pointer alternative."
+    },
+    {
+      "mistake": "Mutating application objects during pointer movement.",
+      "correction": "Render transient data attributes during movement and update controlled application state only from a completed drop."
+    }
+  ],
+  "validation": [
+    "Verify mouse, pen, touch-delay, keyboard, Escape, pointer cancellation, invalid release, and focus continuity.",
+    "Verify localized instructions and announcements use human labels and one-based positions.",
+    "Verify disabled/read-only sources and targets, vertical/horizontal direction, RTL, zoom, and a visible simple-pointer alternative.",
+    "Verify values remain stable while the surrounding collection reorders or updates."
+  ],
+  "related": [
+    "reorder",
+    "collection",
+    "data-grid",
+    "tree",
+    "file-upload"
+  ]
+}
+```

package/public/packages/atom/0.24.0/components/drawer.txt

@@ -0,0 +1,96 @@
+# Drawer
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: drawer
+
+# Drawer agent guide
+
+## Purpose
+
+Provide modal side-sheet behavior, focus management, dismissal, portal composition, and edge-placement metadata.
+
+## Use when
+
+- A modal task or navigation panel enters from an edge and background content must be unavailable while open.
+
+## Choose something else when
+
+- The panel is centered, non-modal, or permanently part of page layout. Use Dialog or an inline panel.
+
+## Required composition
+
+- Compose Trigger and Portal containing Overlay and Content; place Title, Description, and Close inside Content and supply the labeling parts the content requires.
+
+## Rules
+
+- **MUST:** Use Drawer-owned focus trap, focus restoration, scroll lock, Escape, backdrop, and portal behavior instead of rebuilding them.
+- **MUST:** Give Content an accessible name with Title or an explicit labeling relationship.
+
+## Common mistakes
+
+- **Avoid:** Using Drawer only for its edge appearance while leaving background controls interactive. **Instead:** Use Drawer for modal behavior or use a normal inline region when interaction should remain available.
+
+## Validation checklist
+
+- Test trigger focus, initial focus, Tab containment, Escape and backdrop dismissal, Close, scroll lock, and focus return.
+- Confirm nested portals remain within the modal contract.
+
+## Related guidance
+
+- `dialog`
+- `sidebar`
+- `navigation-menu`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "drawer",
+  "name": "Drawer",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Provide modal side-sheet behavior, focus management, dismissal, portal composition, and edge-placement metadata.",
+  "useWhen": [
+    "A modal task or navigation panel enters from an edge and background content must be unavailable while open."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "The panel is centered, non-modal, or permanently part of page layout.",
+      "useInstead": "Dialog or an inline panel"
+    }
+  ],
+  "composition": [
+    "Compose Trigger and Portal containing Overlay and Content; place Title, Description, and Close inside Content and supply the labeling parts the content requires."
+  ],
+  "rules": [
+    {
+      "id": "drawer-modal-contract",
+      "level": "must",
+      "statement": "Use Drawer-owned focus trap, focus restoration, scroll lock, Escape, backdrop, and portal behavior instead of rebuilding them."
+    },
+    {
+      "id": "drawer-labeling",
+      "level": "must",
+      "statement": "Give Content an accessible name with Title or an explicit labeling relationship."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using Drawer only for its edge appearance while leaving background controls interactive.",
+      "correction": "Use Drawer for modal behavior or use a normal inline region when interaction should remain available."
+    }
+  ],
+  "validation": [
+    "Test trigger focus, initial focus, Tab containment, Escape and backdrop dismissal, Close, scroll lock, and focus return.",
+    "Confirm nested portals remain within the modal contract."
+  ],
+  "related": [
+    "dialog",
+    "sidebar",
+    "navigation-menu"
+  ]
+}
+```

package/public/packages/atom/0.24.0/components/dropdown-menu.txt

@@ -0,0 +1,112 @@
+# DropdownMenu
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: dropdown-menu
+
+# DropdownMenu agent guide
+
+## Purpose
+
+Open a compact command or settings menu from a visible button with menu popup semantics, input-aware initial focus, and the shared Menu contract.
+
+## Use when
+
+- A visible button should reveal a short list of commands, independent settings, exclusive settings, or nested commands.
+
+## Choose something else when
+
+- Commands belong to a contextual gesture, several persistent application menu headings, a form value, or ordinary site navigation. Use ContextMenu, Menubar, Select, or NavList.
+
+## Required composition
+
+- Compose Root with a visibly named Trigger and Content. Add Portal and Arrow only when needed; fill Content with uniquely valued Item parts and the shared Menu Group, Label, CheckboxItem, RadioGroup with RadioItem, Separator, or paired Sub anatomy as the command model requires.
+
+## Rules
+
+- **MUST:** Use a visible, accessible Trigger that describes the menu; preserve its button, popup, expanded, controls, disabled, and custom-element keyboard semantics.
+- **MUST:** Preserve input-aware opening: pointer or ordinary activation opens through the owned policy, ArrowDown and activation keys enter at the first item, and ArrowUp enters at the last item.
+- **MUST:** Follow Menu's item roles, unique values, real focus, typeahead, disabled navigation, closeOnSelect, submenu, outside-dismissal, modal, portal, and focus-restoration contracts.
+- **MUST:** When Trigger or retained Menu parts use asChild or render, merge Atom props, refs, handlers, ARIA, and children instead of replacing them.
+
+## Common mistakes
+
+- **Avoid:** Using an unlabeled icon trigger, putting ordinary navigation or a form select into DropdownMenu, or adding custom key and document dismissal handlers. **Instead:** Give Trigger a complete accessible name, select the correct semantic component, and rely on the shared Menu behavior.
+
+## Validation checklist
+
+- Verify Trigger naming and semantics, click, tap, Enter, Space, ArrowDown, and ArrowUp opening, initial item focus, controlled state, disabled behavior, Tab exit, Escape, outside dismissal, and focus return.
+- Verify command, checkbox, radio, group, indicator, separator, and submenu behavior; typeahead; close policies; modal and parent-modal ownership; LTR and RTL; portals; and collision positioning.
+
+## Related guidance
+
+- `menu`
+- `context-menu`
+- `menubar`
+- `select`
+- `nav-list`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "dropdown-menu",
+  "name": "DropdownMenu",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Open a compact command or settings menu from a visible button with menu popup semantics, input-aware initial focus, and the shared Menu contract.",
+  "useWhen": [
+    "A visible button should reveal a short list of commands, independent settings, exclusive settings, or nested commands."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "Commands belong to a contextual gesture, several persistent application menu headings, a form value, or ordinary site navigation.",
+      "useInstead": "ContextMenu, Menubar, Select, or NavList"
+    }
+  ],
+  "composition": [
+    "Compose Root with a visibly named Trigger and Content. Add Portal and Arrow only when needed; fill Content with uniquely valued Item parts and the shared Menu Group, Label, CheckboxItem, RadioGroup with RadioItem, Separator, or paired Sub anatomy as the command model requires."
+  ],
+  "rules": [
+    {
+      "id": "dropdown-visible-trigger",
+      "level": "must",
+      "statement": "Use a visible, accessible Trigger that describes the menu; preserve its button, popup, expanded, controls, disabled, and custom-element keyboard semantics."
+    },
+    {
+      "id": "dropdown-input-focus",
+      "level": "must",
+      "statement": "Preserve input-aware opening: pointer or ordinary activation opens through the owned policy, ArrowDown and activation keys enter at the first item, and ArrowUp enters at the last item."
+    },
+    {
+      "id": "dropdown-menu-contract",
+      "level": "must",
+      "statement": "Follow Menu's item roles, unique values, real focus, typeahead, disabled navigation, closeOnSelect, submenu, outside-dismissal, modal, portal, and focus-restoration contracts."
+    },
+    {
+      "id": "dropdown-composition-merge",
+      "level": "must",
+      "statement": "When Trigger or retained Menu parts use asChild or render, merge Atom props, refs, handlers, ARIA, and children instead of replacing them."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using an unlabeled icon trigger, putting ordinary navigation or a form select into DropdownMenu, or adding custom key and document dismissal handlers.",
+      "correction": "Give Trigger a complete accessible name, select the correct semantic component, and rely on the shared Menu behavior."
+    }
+  ],
+  "validation": [
+    "Verify Trigger naming and semantics, click, tap, Enter, Space, ArrowDown, and ArrowUp opening, initial item focus, controlled state, disabled behavior, Tab exit, Escape, outside dismissal, and focus return.",
+    "Verify command, checkbox, radio, group, indicator, separator, and submenu behavior; typeahead; close policies; modal and parent-modal ownership; LTR and RTL; portals; and collision positioning."
+  ],
+  "related": [
+    "menu",
+    "context-menu",
+    "menubar",
+    "select",
+    "nav-list"
+  ]
+}
+```

package/public/packages/atom/0.24.0/components/feed.txt

@@ -0,0 +1,132 @@
+# Feed
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: feed
+
+# Feed agent guide
+
+## Purpose
+
+Provide a named ARIA feed of focusable articles with article-to-article keyboard movement, loading state, logical position and size metadata, and safe integration with dynamic or virtualized streams.
+
+## Use when
+
+- A changing, paged, infinite, or virtualized stream of articles needs keyboard movement article by article while people read.
+
+## Choose something else when
+
+- The content is a static set that needs only ordinary list semantics, or items are selectable options or commands rather than articles. Use List or the matching interactive collection primitive.
+- Only visual infinite scrolling is needed and article keyboard navigation or feed semantics are not appropriate. Use the semantic collection that matches the content, optionally composed with Virtualizer.
+
+## Required composition
+
+- Give Root an accessible name and truthful busy and setSize state, then render one Item per article with a useful internal heading, stable identity, and accurate one-based position or zero-based index. Compose Virtualizer only when scale justifies windowing and preserve the logical feed contract.
+
+## Rules
+
+- **MUST:** Give Root an accessible name and preserve feed and direct article relationships; give every Item meaningful article content and a useful heading or accessible name.
+- **MUST:** Expose accurate one-based positions and the total logical set size, using unknown only when the total truly cannot be known and not merely because a rendered window is partial.
+- **MUST:** Set busy while articles are being added or replaced and clear it only after the DOM and position metadata represent the completed update.
+- **MUST:** Preserve PageUp and PageDown article movement, Control or Command Home and End movement outside the feed, focus of the target article, nearest scrolling, and consumer preventDefault cancellation.
+- **MUST:** Keep each Item focusable by default while allowing focusable descendants, and ensure navigation identifies the containing direct article when focus starts inside it.
+- **MUST:** When windowing, keep the current and keyboard target articles mounted or materialize them before focus moves, retain stable keys and logical positions, and remember that Virtualizer supplies measurement rather than feed semantics or loading.
+
+## Common mistakes
+
+- **Avoid:** Using Feed as a visual synonym for any list or reporting the rendered window length as aria-setsize. **Instead:** Use Feed only for article streams and report the logical full set size or genuinely unknown size.
+- **Avoid:** Unmounting the focused article during virtualization or setting busy for the entire lifetime of an infinite stream. **Instead:** Preserve or deliberately move focus before unmounting and scope busy to each concrete DOM mutation.
+
+## Validation checklist
+
+- Verify Root naming, direct article roles, meaningful article headings, stable identities, accurate logical positions and known or unknown total size, and busy transitions during mutations.
+- Exercise PageUp and PageDown from Items and their descendants, Control and Command Home and End to outside targets, first and last boundaries, nearest scrolling, and consumer preventDefault cancellation.
+- Verify native prop, tabIndex, asChild, render, ref, and server/client entrypoint behavior without losing feed or article semantics.
+- For paged or virtualized feeds, verify stable keys and full logical metadata and ensure the focused and next navigation target articles exist before focus moves.
+
+## Related guidance
+
+- `list`
+- `virtualizer`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "feed",
+  "name": "Feed",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Provide a named ARIA feed of focusable articles with article-to-article keyboard movement, loading state, logical position and size metadata, and safe integration with dynamic or virtualized streams.",
+  "useWhen": [
+    "A changing, paged, infinite, or virtualized stream of articles needs keyboard movement article by article while people read."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "The content is a static set that needs only ordinary list semantics, or items are selectable options or commands rather than articles.",
+      "useInstead": "List or the matching interactive collection primitive"
+    },
+    {
+      "condition": "Only visual infinite scrolling is needed and article keyboard navigation or feed semantics are not appropriate.",
+      "useInstead": "the semantic collection that matches the content, optionally composed with Virtualizer"
+    }
+  ],
+  "composition": [
+    "Give Root an accessible name and truthful busy and setSize state, then render one Item per article with a useful internal heading, stable identity, and accurate one-based position or zero-based index. Compose Virtualizer only when scale justifies windowing and preserve the logical feed contract."
+  ],
+  "rules": [
+    {
+      "id": "feed-name-articles",
+      "level": "must",
+      "statement": "Give Root an accessible name and preserve feed and direct article relationships; give every Item meaningful article content and a useful heading or accessible name."
+    },
+    {
+      "id": "feed-position-size",
+      "level": "must",
+      "statement": "Expose accurate one-based positions and the total logical set size, using unknown only when the total truly cannot be known and not merely because a rendered window is partial."
+    },
+    {
+      "id": "feed-busy",
+      "level": "must",
+      "statement": "Set busy while articles are being added or replaced and clear it only after the DOM and position metadata represent the completed update."
+    },
+    {
+      "id": "feed-keyboard",
+      "level": "must",
+      "statement": "Preserve PageUp and PageDown article movement, Control or Command Home and End movement outside the feed, focus of the target article, nearest scrolling, and consumer preventDefault cancellation."
+    },
+    {
+      "id": "feed-focus-content",
+      "level": "must",
+      "statement": "Keep each Item focusable by default while allowing focusable descendants, and ensure navigation identifies the containing direct article when focus starts inside it."
+    },
+    {
+      "id": "feed-virtualization",
+      "level": "must",
+      "statement": "When windowing, keep the current and keyboard target articles mounted or materialize them before focus moves, retain stable keys and logical positions, and remember that Virtualizer supplies measurement rather than feed semantics or loading."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using Feed as a visual synonym for any list or reporting the rendered window length as aria-setsize.",
+      "correction": "Use Feed only for article streams and report the logical full set size or genuinely unknown size."
+    },
+    {
+      "mistake": "Unmounting the focused article during virtualization or setting busy for the entire lifetime of an infinite stream.",
+      "correction": "Preserve or deliberately move focus before unmounting and scope busy to each concrete DOM mutation."
+    }
+  ],
+  "validation": [
+    "Verify Root naming, direct article roles, meaningful article headings, stable identities, accurate logical positions and known or unknown total size, and busy transitions during mutations.",
+    "Exercise PageUp and PageDown from Items and their descendants, Control and Command Home and End to outside targets, first and last boundaries, nearest scrolling, and consumer preventDefault cancellation.",
+    "Verify native prop, tabIndex, asChild, render, ref, and server/client entrypoint behavior without losing feed or article semantics.",
+    "For paged or virtualized feeds, verify stable keys and full logical metadata and ensure the focused and next navigation target articles exist before focus moves."
+  ],
+  "related": [
+    "list",
+    "virtualizer"
+  ]
+}
+```

package/public/packages/atom/0.24.0/components/field.txt

@@ -0,0 +1,108 @@
+# Field
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: field
+
+# Field agent guide
+
+## Purpose
+
+Wire one form control to its label, description, error, and shared required, disabled, read-only, and invalid state.
+
+## Use when
+
+- One control needs a visible label and may need help or error text.
+
+## Choose something else when
+
+- Several related controls share one group label. Use Fieldset containing one Field per control when needed.
+
+## Required composition
+
+- Compose Field.Root -> Field.Label -> one Field-aware control -> optional Field.Description -> optional Field.Error.
+
+## Rules
+
+- **MUST:** Associate one Field with one owned control.
+- **MUST:** Field.Label already renders the default required marker; do not add Field.RequiredIndicator inside it unless the default indicator is disabled.
+- **SHOULD:** Make error text explain how to correct the value.
+
+## Common mistakes
+
+- **Avoid:** Adding a manual asterisk or RequiredIndicator beside the default required Label. **Instead:** Set required on Field.Root and let Field.Label render its built-in marker, or disable that marker before composing a separate indicator.
+
+## Validation checklist
+
+- Inspect label-for and control-id relationships.
+- Confirm description and visible error IDs appear in aria-describedby.
+- Confirm exactly one required indicator is visible.
+
+## Related guidance
+
+- `form`
+- `fieldset`
+- `input`
+- `textarea`
+- `checkbox`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "field",
+  "name": "Field",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Wire one form control to its label, description, error, and shared required, disabled, read-only, and invalid state.",
+  "useWhen": [
+    "One control needs a visible label and may need help or error text."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "Several related controls share one group label.",
+      "useInstead": "Fieldset containing one Field per control when needed"
+    }
+  ],
+  "composition": [
+    "Compose Field.Root -> Field.Label -> one Field-aware control -> optional Field.Description -> optional Field.Error."
+  ],
+  "rules": [
+    {
+      "id": "field-one-control",
+      "level": "must",
+      "statement": "Associate one Field with one owned control."
+    },
+    {
+      "id": "field-required-marker",
+      "level": "must",
+      "statement": "Field.Label already renders the default required marker; do not add Field.RequiredIndicator inside it unless the default indicator is disabled."
+    },
+    {
+      "id": "field-errors-actionable",
+      "level": "should",
+      "statement": "Make error text explain how to correct the value."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Adding a manual asterisk or RequiredIndicator beside the default required Label.",
+      "correction": "Set required on Field.Root and let Field.Label render its built-in marker, or disable that marker before composing a separate indicator."
+    }
+  ],
+  "validation": [
+    "Inspect label-for and control-id relationships.",
+    "Confirm description and visible error IDs appear in aria-describedby.",
+    "Confirm exactly one required indicator is visible."
+  ],
+  "related": [
+    "form",
+    "fieldset",
+    "input",
+    "textarea",
+    "checkbox"
+  ]
+}
+```