From d7de178510f17e5a062607e7eb882b4da6c98353 Mon Sep 17 00:00:00 2001
From: rmojica-godaddy <rmojica@godaddy.com>
Date: Tue, 20 Oct 2026 10:37:06 -0500
Subject: [PATCH 1/4] feat(skills): add antares-builder consumer skill

---
 .agents/skills/antares-builder/SKILL.md       |  44 ++++
 .../antares-builder/references/charts.md      | 129 ++++++++++
 .../references/component-decision-tree.md     |  72 ++++++
 .../references/composition-patterns.md        | 224 ++++++++++++++++++
 .../references/layout-and-styling.md          |  53 +++++
 .../antares-builder/references/setup.md       |  47 ++++
 .claude/skills/antares-builder                |   1 +
 7 files changed, 570 insertions(+)
 create mode 100644 .agents/skills/antares-builder/SKILL.md
 create mode 100644 .agents/skills/antares-builder/references/charts.md
 create mode 100644 .agents/skills/antares-builder/references/component-decision-tree.md
 create mode 100644 .agents/skills/antares-builder/references/composition-patterns.md
 create mode 100644 .agents/skills/antares-builder/references/layout-and-styling.md
 create mode 100644 .agents/skills/antares-builder/references/setup.md
 create mode 120000 .claude/skills/antares-builder

diff --git a/.agents/skills/antares-builder/SKILL.md b/.agents/skills/antares-builder/SKILL.md
new file mode 100644
index 0000000000..9fdb4afdf0
--- /dev/null
+++ b/.agents/skills/antares-builder/SKILL.md
@@ -0,0 +1,44 @@
+---
+name: antares-builder
+description: Build, adapt, or review React interfaces with @godaddy/antares. Use for component selection and composition, forms, accessible interactions, responsive layouts, charts, and consumer setup. Do not use for authoring the Antares library itself.
+---
+
+# Antares Builder
+
+Build consumer UI with the public `@godaddy/antares` API. Choose the interaction before its appearance. Many components use React Aria Components (RAC); Antares's own exports, props and slots define the consumer contract.
+
+Follow the steps relevant to the request. Load only the reference sections needed for the selected feature.
+
+## Step 1 — Read the project context
+
+Inspect `package.json`, the lockfile, framework configuration and neighboring UI. Identify the Antares version, package manager, routing, form library, CSS conventions and locale. Preserve those conventions when adapting existing UI.
+
+Check the installed package's public exports/types before using an unfamiliar API. Follow [API and documentation discovery](references/setup.md#resolve-the-installed-api-and-documentation) for commands, official sources and mismatches; a consumer may not have the library's source checkout. Adapt these references to that installed API. For installation, imports, CSS failures or server/client boundaries, read the relevant setup sections.
+
+Use public root or subpath imports. Do not derive Antares APIs from another design system or import `#components/*`, `dist` files or transitive internals.
+
+## Step 2 — Choose the component by behavior
+
+Identify the action, value, navigation or information the user needs. Read the relevant branch of the [component decision tree](references/component-decision-tree.md) when choosing a component or comparing alternatives. If Antares has no matching export, use the application's established solution or semantic HTML and explain the gap.
+
+## Step 3 — Arrange and style the interface
+
+For page structure, responsive behavior, typography, icons or sizing, read [layout and styling](references/layout-and-styling.md). Prefer Antares's existing variants and layout primitives. Responsive changes use the application's CSS media/container queries; Antares has no breakpoint prop syntax or mandatory provider.
+
+## Step 4 — Compose the selected components
+
+Read the relevant [composition patterns](references/composition-patterns.md) for slots and state, collections, disclosures, tabs, overlays, files or feedback. For any chart implementation or customization, read [charts](references/charts.md). Include the required children and wire controlled callbacks. A RAC base provides behavior but does not render missing Antares parts.
+
+## Step 5 — Build complete forms
+
+For form UI, follow [fields and validation](references/composition-patterns.md#fields-and-validation), then the selection, date or file sections as needed. Field roots own validation and relationships; `Input` and `TextArea` are controls within them. Integrate with the application's submission and error handling rather than introducing a second form architecture.
+
+## Step 6 — Supply the accessibility the app owns
+
+Provide visible field labels, names for icon-only controls and collections, suitable heading levels and image alternatives. Preserve the selected component's keyboard model, focus indicator and DOM semantics. For dialogs, follow the title, dismissal and focus contracts in [modal layers](references/composition-patterns.md#modal-layers). Check locale/RTL when the feature depends on direction or date/number formatting.
+
+## Step 7 — Verify and deliver
+
+Use the consumer project's task runner for appropriate type, lint, build and meaningful interaction checks. Verify labels, validation, overlay focus/return, loading/empty states and narrow layouts for the changed feature. Advice-only requests need focused API inspection rather than unrelated tasks.
+
+For implementation, deliver runnable code with real imports and data flow, then briefly explain the component choices and any gap. For review, report actionable findings and minimal fixes.
diff --git a/.agents/skills/antares-builder/references/charts.md b/.agents/skills/antares-builder/references/charts.md
new file mode 100644
index 0000000000..9a32c9abc5
--- /dev/null
+++ b/.agents/skills/antares-builder/references/charts.md
@@ -0,0 +1,129 @@
+# Charts
+
+Read this for any chart implementation, conversion or customization. Check the installed chart props before adapting these patterns. Import `BarChart`, `LineChart`, `DonutChart` and `GaugeChart` from the package root or `@godaddy/antares/Chart`. `Chart` is a public subpath, not a generic chart component. Bar/Line/Donut use Visx; Gauge uses Antares SVG. Do not import internal legends, tooltips or Visx modules as Antares public API.
+
+## BarChart: categorical comparisons
+
+Pass a `series` array of `{ id, name, data }`. The default point shape is `{ x, y }`; custom point shapes need `xAccessor` and `yAccessor`. Multiple series produce grouped bars. Use stable series IDs across filtering/reordering.
+
+Vertical bars use X for categories and Y for values. Horizontal bars reverse that relationship: X must return the numeric value and Y the category. Changing only `orientation` while keeping vertical accessors is insufficient.
+
+```tsx
+import { BarChart } from '@godaddy/antares/Chart';
+
+type RegionalRevenuePoint = { region: string; revenue: number };
+
+export function RegionalRevenue() {
+  return (
+    <BarChart<RegionalRevenuePoint>
+      series={[{
+        id: 'revenue',
+        name: 'Revenue',
+        data: [{ region: 'North America', revenue: 12000 }, { region: 'Europe', revenue: 9000 }]
+      }]}
+      orientation="horizontal"
+      xAccessor={(point) => point.revenue}
+      yAccessor={(point) => point.region}
+      xAxisTitle="Revenue (USD)"
+      yAxisTitle="Region"
+      height={280}
+      aria-label="Revenue by region"
+      desc="North America: 12,000 US dollars. Europe: 9,000 US dollars."
+    />
+  );
+}
+```
+
+Use `xDomain`/`yDomain` for explicit category order or numeric bounds, matching the orientation. Keep comparison charts on consistent scales. Axis controls include labels, tick formatting, tick counts, baselines and gridlines. Series support palette `colorIndex`, per-category `categoryColors` and `opacity`; preserve meaningful labels alongside color.
+
+## LineChart: continuous and time trends
+
+Pass series with points in intended X order. Use `xType="time"` for Date values, `"linear"` for numeric X, or `"band"` for discrete labels. Custom data requires both accessors. Preserve missing observations as `y: null` rather than inventing zeros. Use `xTitle`/`yTitle`; these differ from BarChart's `xAxisTitle`/`yAxisTitle`.
+
+```tsx
+import { LineChart } from '@godaddy/antares/Chart';
+
+export function MonthlyRevenue() {
+  return (
+    <LineChart
+      series={[{
+        id: 'revenue',
+        name: 'Revenue',
+        data: [
+          { x: new Date(2026, 0, 1), y: 12000 },
+          { x: new Date(2026, 1, 1), y: null },
+          { x: new Date(2026, 2, 1), y: 15000 }
+        ]
+      }]}
+      xType="time"
+      xTitle="Month"
+      yTitle="Revenue (USD)"
+      height={280}
+      aria-label="Monthly revenue, January to March"
+      desc="January: 12,000 US dollars. February: unavailable. March: 15,000 US dollars."
+    />
+  );
+}
+```
+
+Check `xDomain`/`yDomain`, tick formatting/values and `xZero`/`yZero` when the scale matters. Zero is inappropriate for log/time scales. Series accept `colorIndex` and `variant="solid" | "dashed" | "dotted"`; do not copy BarChart's category color API onto lines.
+
+## DonutChart: parts of a whole
+
+Pass `data` containing `{ id, name, value }`, with numeric non-negative values, and a required center `label`; `subLabel` is optional. This is not the Bar/Line `series` API. Prefer a small set of categories that actually form a whole.
+
+```tsx
+import { DonutChart } from '@godaddy/antares/Chart';
+
+export function TrafficSources() {
+  return (
+    <DonutChart
+      data={[{ id: 'organic', name: 'Organic', value: 70 }, { id: 'direct', name: 'Direct', value: 30 }]}
+      label="100%"
+      subLabel="Traffic"
+      legend="bottom"
+      legendLabel="Source"
+      aria-label="Traffic sources: 70 percent organic, 30 percent direct"
+    />
+  );
+}
+```
+
+`legend` accepts `"bottom"` or `"right"`; `formatValue` formats slice values. Zero/negative slices are omitted from the ring. Handle an empty/all-zero total explicitly. `smallSliceThreshold` groups adjacent small slices in hover feedback; it does not aggregate or rewrite the application's dataset.
+
+## GaugeChart: one value on a known scale
+
+Provide numeric `value`, visible `label` and an accessible name. Continuous mode uses 0–100. Segmented mode uses 0–`segments`; `segments` must be a finite positive integer or the component throws. Values are clamped, so keep the displayed label consistent with the intended scale.
+
+```tsx
+import { GaugeChart } from '@godaddy/antares/Chart';
+
+export function HealthScore() {
+  return (
+    <GaugeChart
+      value={3}
+      segments={5}
+      label="3/5"
+      subLabel="Site health"
+      rangeLabel={{ min: '0', max: '5' }}
+      variant="warning"
+      aria-label="Site health score"
+      style={{ maxWidth: '16rem' }}
+    />
+  );
+}
+```
+
+Omit `segments` for continuous mode. Normalize a different measurement range in application code rather than inventing min/max props. `rangeLabel` requires both min/max display labels; it does not change the numeric scale. Use `labelType="text"` for a short textual center label. Gauge exposes meter semantics; task completion belongs to ProgressBar/CircularProgress.
+
+## Dimensions, legends and tooltips
+
+Bar/Line measure their container and accept numeric `width`/`height`; ensure usable non-zero dimensions before diagnosing absent data. They scroll when their minimum plot size exceeds available space, with behavior depending on orientation. Avoid adding a competing scroll/axis system. Donut/Gauge size from container width; constrain their parent or max width to suit the layout. Test the actual dashboard cell at narrow widths.
+
+Bar/Line use `legendPosition="top" | "bottom" | null`; the default shows a bottom legend for multiple series. Their `tooltipValueFormatter` receives a datum, not a numeric value alone. Custom `renderTooltip` payloads differ: use the public `BarChartTooltipRenderProps`/`BarChartTooltipSeries` or `LineChartTooltipRenderProps` types. Do not replace built-in tooltip behavior unless the product needs custom content.
+
+## Accessibility and data states
+
+Supply `aria-label` and meaningful series/category/unit labels. Bar/Line also accept `desc`. Make the essential values or takeaway available in nearby text or a semantic table when users need them; do not rely on pointer tooltips or color alone. Verify actual keyboard/assistive behavior instead of assuming every Visx graphic inherits RAC collection behavior. Use the application's locale for dates, numbers and currencies, and check RTL layouts when applicable.
+
+Handle loading, no data, single-point/single-slice data, missing values, long labels and large datasets according to the product. Validate finite values/accessors and domain coverage. Preserve missing versus zero semantics; avoid rendering an empty frame as if it were a valid result. Do not change the library's component internals to solve a consumer data-formatting issue.
diff --git a/.agents/skills/antares-builder/references/component-decision-tree.md b/.agents/skills/antares-builder/references/component-decision-tree.md
new file mode 100644
index 0000000000..f0ed4aab08
--- /dev/null
+++ b/.agents/skills/antares-builder/references/component-decision-tree.md
@@ -0,0 +1,72 @@
+# Component decision tree
+
+Use this when the user has not named a component, when alternatives overlap, or when replacing custom UI. Choose the interaction first. Follow the linked patterns for anatomy, state and required children.
+
+## 1. Is the user entering or selecting a value?
+
+For field composition, read [fields and validation](composition-patterns.md#fields-and-validation).
+
+- Short text, email, search or password → `TextField` with `Input`.
+- Multiline text → `TextField` with `TextArea`.
+- Exact number, currency or stepper → `NumberField`; bounded continuous adjustment → `RangeField`.
+- Independent boolean or agreement → `Checkbox`; related independent options → `CheckboxGroup`.
+- Immediate on/off setting → `Switch`; one answer among visible form options → `RadioGroup` with `Radio`.
+- Popup form selection → `Select`; an always-visible selectable collection → `ListBox`. For autocomplete/free-text filtering, see the API gaps below.
+- Compact exclusive view/mode → `SegmentedController`; contextual pressed actions such as Bold/Italic → `ToggleButtonGroup` with `ToggleButton`.
+- Selectable/removable pills → `ChipGroup`; a standalone pill action → `ChipButton`. See [collections](composition-patterns.md#collections-and-actions).
+- Date grid always visible → `Calendar` or `RangeCalendar`; compact field opening a grid → `DatePicker` or `DateRangePicker`. See [dates](composition-patterns.md#dates-and-locale).
+- Browse for files → `FileTrigger`; drag/drop target → `DropZone`. The app handles validation/upload. See [file input](composition-patterns.md#file-input).
+
+## 2. Is this an action or navigation?
+
+- Perform an action → `Button`; navigate with button styling → `LinkButton`.
+- Dismiss an overlay → `CloseButton`; enhance an existing visual child with press behavior → `Pressable`.
+- Choose a command from an action list → `MenuTrigger` with `Menu`; use a Popover for a general interactive form.
+- Static/linked content surface → `Card`; selectable/action card collection → `CardGroup`.
+
+Read [actions and slots](composition-patterns.md#actions-slots-and-state) or [collections](composition-patterns.md#collections-and-actions) for these structures. Ordinary inline links use semantic anchors or the application's router link.
+
+## 3. Is content revealed, switched or layered?
+
+- Reveal one section in place → `Collapsible`; coordinate related sections → `Accordion`.
+- Expand a rail/panel within page flow → `InlineDrawer`.
+- Replace peer panels in one view → `Tabs`.
+- Communicate wizard stages → `ProgressSteps` with `ProgressStep`.
+- Move through a dataset's pages → `Pagination`; decorative page omissions → `PaginationDots`.
+- Browse sequential gallery/feature panels → `Carousel`.
+
+See [disclosure and tabs](composition-patterns.md#disclosure-and-tabs) and [progress, pagination and feedback](composition-patterns.md#progress-pagination-and-feedback).
+
+For layered content, read [modal layers](composition-patterns.md#modal-layers):
+
+- Non-interactive hover/focus help → `TooltipTrigger` with `Tooltip`.
+- Anchored interactive content → `PopoverTrigger` with `Popover`.
+- Blocking centered task/confirmation → `ModalTrigger` with `Modal`.
+- Modal edge panel or bottom sheet → `DrawerTrigger` with `Drawer`.
+
+## 4. Is this information, feedback or data?
+
+- In-page live message → `Alert`; field validation → `FieldError` inside its field.
+- Static status/category → `Tag`; selection/removal belongs to Chip.
+- Operation progress → `ProgressBar` or compact `CircularProgress`; a numeric input belongs to RangeField.
+- Text-first KPI/trend → `MetricsLockup`.
+- Category comparison → `BarChart`; continuous/time trend → `LineChart`; few parts of a whole → `DonutChart`; one measure against a scale → `GaugeChart`.
+
+Read [charts](charts.md) for chart data/accessors, dimensions, axes, legends and accessibility; read [progress, pagination and feedback](composition-patterns.md#progress-pagination-and-feedback) for feedback and navigation contracts.
+
+For content presentation, read [layout and styling](layout-and-styling.md):
+
+- Body/secondary copy → `Text`/`Detail`; semantic title → `Heading`; coordinated eyebrow/title/body → `TextLockup`.
+- Person/entity identity → `Avatar`; image → `Image`; Antares SVG → `Icon`.
+
+## 5. How should it be arranged?
+
+Read [layout and styling](layout-and-styling.md) for composition and responsive rules.
+
+- One-dimensional row/column → `Flex`; two-dimensional placement → `Grid`; surface/semantic wrapper → `Box`.
+- Interior regions → `Header`, `Content`, `Footer`, `ButtonGroup`, `Group`, `CornerActions`.
+- Consistent adopted component size → optional `SizeProvider`.
+
+## API gaps
+
+Do not infer Antares exports such as `Combobox`, `Table`, `Toast`, `Skeleton`, `EmptyState`, `NativeSelect`, `Link`, `Breadcrumb`, `Sidebar` or `FileUpload` from other libraries. Check the installed export map first. When a required component is unavailable, use semantic HTML or the application's established solution. A separate RAC dependency is an option when its API and styling fit the requirement; it does not create an Antares export. For empty states, Antares typography, media, actions and layout can form a suitable composition.
diff --git a/.agents/skills/antares-builder/references/composition-patterns.md b/.agents/skills/antares-builder/references/composition-patterns.md
new file mode 100644
index 0000000000..b257ba6576
--- /dev/null
+++ b/.agents/skills/antares-builder/references/composition-patterns.md
@@ -0,0 +1,224 @@
+# Antares composition patterns
+
+Read only the sections relevant to the task. These shapes are verified against the package's component READMEs and examples. Use the consumer's installed types for detailed props and adapt data and handlers to the product. RAC conventions explain behavior but do not replace Antares's explicit children and slots.
+
+## Actions, slots and state
+
+`Button` uses RAC button behavior; `LinkButton` uses link behavior. `Pressable` adds press/focus/hover behavior to exactly one child that forwards its ref and DOM/ARIA props, without rendering a wrapper. Prefer the semantic Button/LinkButton when they fit. Name icon-only controls on the control itself.
+
+Parents publish behavior and presentation through slots. Keep field triggers as `Button slot="trigger"`, steppers as `slot="decrement"`/`slot="increment"`, and dismissal as `slot="close"`. Slot names are parent-specific. `ButtonContext` is an advanced defaults API; ordinary compositions do not require a custom provider. Button omits RAC's `isPending` prop; use application-owned pending state and supported disabled/content props.
+
+Match the actual state model: field `value`/`onChange`, collection `selectedKeys`/`onSelectionChange`, boolean `isSelected`/`onChange`, and disclosure `isExpanded`/`onExpandedChange` are not interchangeable. Use defaults for uncontrolled state, or update state from the controlled callback; do not combine both modes accidentally.
+
+## Fields and validation
+
+`TextField` and `NumberField` provide the field relationship, while children provide visible parts. The field's `isInvalid` state controls whether `FieldError` renders. Use `Text slot="description"` for persistent help.
+
+Set `name` for native form submission and use supported root props such as `isRequired`, `isDisabled` and `isInvalid`. Keep the application's form/validation library and connect its state to the exact Antares value/change API. Place controls in a semantic form and choose submit/reset button types deliberately. The following field fragments assume `emailError` comes from that validation state.
+
+```tsx
+import { Button, FieldError, Group, Input, Label, NumberField, Text, TextArea, TextField } from '@godaddy/antares';
+
+<TextField name="email" type="email" isRequired isInvalid={Boolean(emailError)}>
+  <Label>Email</Label>
+  <Input placeholder="you@example.com" />
+  <Text slot="description">We'll send receipts here.</Text>
+  <FieldError>{emailError}</FieldError>
+</TextField>;
+
+<TextField name="message">
+  <Label>Message</Label>
+  <TextArea />
+</TextField>;
+
+<NumberField defaultValue={1} minValue={1} maxValue={10}>
+  <Label>Quantity</Label>
+  <Group>
+    <Button slot="decrement" />
+    <Input />
+    <Button slot="increment" />
+  </Group>
+</NumberField>;
+```
+
+An `Input` inside NumberField is numeric because the field supplies its context. Do not switch it to a plain TextField for exact numeric behavior. A `Button slot="control"` inside a TextField `Group` is an interactive affix. For a required group of independent options, use `CheckboxGroup`; for one exclusive answer, `RadioGroup`. Their composed structure is `Label`, `Group` with items, optional description and `FieldError`.
+
+`CheckboxIndicator` supplies the visual check in custom Checkbox compositions. A standalone Checkbox or Switch needs visible children or an accessible name. `RangeField` uses RAC Slider behavior and supports multiple thumb values; supply corresponding `thumbLabels` for a range. `InputContext`, `TextAreaContext`, `LabelContext` and `FieldErrorContext` are advanced field-part context APIs.
+
+```tsx
+import { Checkbox, CheckboxGroup, Group, Label, Radio, RadioGroup } from '@godaddy/antares';
+
+<CheckboxGroup name="interests">
+  <Label>Interests</Label>
+  <Group>
+    <Checkbox value="design">Design</Checkbox>
+    <Checkbox value="code">Code</Checkbox>
+  </Group>
+</CheckboxGroup>;
+
+<RadioGroup name="plan">
+  <Label>Plan</Label>
+  <Group>
+    <Radio value="basic">Basic</Radio>
+    <Radio value="pro">Pro</Radio>
+  </Group>
+</RadioGroup>;
+```
+
+## Collections and actions
+
+`Select` explicitly composes a Label, trigger and `SelectOptions` containing `SelectItem` children. An empty trigger receives the value/chevron; use `SelectValue` when writing custom trigger content. `ListBox` contains `ListBoxItem` children. Both use RAC collection behavior.
+
+```tsx
+import { Button, Label, ListBox, ListBoxItem, Select, SelectItem, SelectOptions } from '@godaddy/antares';
+
+<Select name="region" placeholder="Choose a region">
+  <Label>Region</Label>
+  <Button slot="trigger" />
+  <SelectOptions>
+    <SelectItem id="na">North America</SelectItem>
+    <SelectItem id="eu">Europe</SelectItem>
+  </SelectOptions>
+</Select>;
+
+<ListBox aria-label="Available regions" selectionMode="single">
+  <ListBoxItem id="na">North America</ListBoxItem>
+  <ListBoxItem id="eu">Europe</ListBoxItem>
+</ListBox>;
+```
+
+Use stable IDs/keys for collections. Give composed items `textValue` when visible content is not straightforward text, so typeahead and accessible naming work. Controlled collection APIs often use `selectedKeys`/`onSelectionChange`, while `Select` uses `value`/`onChange`; check the exact component.
+
+- `MenuTrigger` wraps a trigger and `Menu`; commands are `MenuItem` children. `MenuGroup` groups commands, `MenuSeparator` divides them, and `SubmenuTrigger` connects a submenu. Preserve the menu's keyboard model; arbitrary form controls belong in a Popover.
+- `SegmentedController` contains `SegmentedControllerItem value="..."` children. Its single string `value`/`defaultValue` pairs with `onSelectionChange(value)`. `ToggleButtonGroup` instead uses selection keys and `ToggleButton id="..."` children. Both build on RAC toggle behavior.
+- `ChipGroup` + `ChipList` + `Chip` wrap RAC TagGroup/TagList/Tag behavior. When removal is enabled, the group's `onRemove` must update the consumer's item collection. `ChipButton` is a standalone action. `ChipContext` is an advanced defaults API.
+- `CardGroup` + `Card` wrap RAC GridList behavior. Name the group and give composed cards stable IDs and `textValue`; `CardSelectionIndicator` optionally displays selection. A standalone Card can be static or use `href`; keep nested controls out of a standalone card link.
+
+## Dates and locale
+
+`Calendar` and `RangeCalendar` are inline; date pickers show a field and open one in a popover. `CalendarDate` helpers come from the public `date` subpath. The date picker trigger is an explicitly written `Button slot="trigger"`; the matching calendar component is also explicit.
+
+```tsx
+import { Button, Calendar, DatePicker, DatePickerCalendar, Label } from '@godaddy/antares';
+import { parseDate } from '@godaddy/antares/date';
+
+<Calendar aria-label="Delivery date" defaultValue={parseDate('2026-10-16')} />;
+
+<DatePicker defaultValue={parseDate('2026-10-16')}>
+  <Label>Delivery date</Label>
+  <Button slot="trigger" />
+  <DatePickerCalendar />
+</DatePicker>;
+```
+
+`DatePickerValue` customizes the single-date trigger. For a range, change to `DateRangePicker`, `DateRangePickerCalendar`, and optionally `DateRangePickerValue`; the inline equivalent is `RangeCalendar`. These build on the corresponding RAC date/calendar primitives. Use `minValue`/`maxValue` for continuous bounds and `isDateUnavailable` for scattered blocked days. Preserve date-only versus time/zoned values rather than converting everything to JavaScript Date. Localize through the consuming application's locale context.
+
+## Disclosure and tabs
+
+One revealable section uses `Collapsible`; related sections use an `Accordion` group. The trigger must have `slot="trigger"`, and each grouped section needs a stable ID. The Accordion controls `expandedKeys`/`onExpandedChange`; a standalone Collapsible controls `isExpanded`/`onExpandedChange`.
+
+These wrap RAC DisclosureGroup/Disclosure/DisclosurePanel. `InlineDrawer` + `InlineDrawerPanel` use disclosure behavior while occupying page flow. `AccordionContext` and `CollapsibleContext` are advanced context APIs.
+
+```tsx
+import { Accordion, Button, Collapsible, CollapsiblePanel, Heading, Text } from '@godaddy/antares';
+
+<Accordion defaultExpandedKeys={['billing']}>
+  <Collapsible id="billing">
+    <Heading level={2}>
+      <Button slot="trigger">Billing</Button>
+    </Heading>
+    <CollapsiblePanel>
+      <Text>Manage invoices and payment methods.</Text>
+    </CollapsiblePanel>
+  </Collapsible>
+</Accordion>;
+```
+
+For peer panels that replace each other, use `Tabs` rather than disclosures. `TabList` needs an accessible name. Match each Tab's `id` with its panel's `id`.
+
+```tsx
+import { Tab, TabList, TabPanel, TabPanels, Tabs } from '@godaddy/antares';
+
+<Tabs>
+  <TabList aria-label="Account settings">
+    <Tab id="profile">Profile</Tab>
+    <Tab id="security">Security</Tab>
+  </TabList>
+  <TabPanels>
+    <TabPanel id="profile">Profile settings</TabPanel>
+    <TabPanel id="security">Security settings</TabPanel>
+  </TabPanels>
+</Tabs>;
+```
+
+## Modal layers
+
+`ModalTrigger`, `DrawerTrigger`, `PopoverTrigger` and `TooltipTrigger` connect their triggers to the corresponding content and open state. Modal and Drawer use RAC DialogTrigger/ModalOverlay/Modal/Dialog; Popover is an anchored RAC dialog, and Tooltip uses description semantics. Use non-interactive content in Tooltip.
+
+Give Modal/Drawer a `Heading slot="title"` or another accessible name. A standalone Popover anchored with `triggerRef` needs its own name. Structural regions such as Content and ButtonGroup receive the overlay's presentation through context.
+
+```tsx
+import { Button, ButtonGroup, CloseButton, Content, Heading, Modal, ModalTrigger } from '@godaddy/antares';
+
+<ModalTrigger>
+  <Button>Review order</Button>
+  <Modal>
+    <Heading slot="title">Review order</Heading>
+    <CloseButton />
+    <Content>Confirm the items before placing the order.</Content>
+    <ButtonGroup>
+      <Button slot="close">Back</Button>
+      <Button variant="primary">Place order</Button>
+    </ButtonGroup>
+  </Modal>
+</ModalTrigger>;
+```
+
+Wire a confirming action to application logic and close only after the action succeeds. `slot="close"` dismisses, so avoid applying it to a button that must wait for an async operation. `CloseButton` is already named and slotted. React Aria's modal stack supplies focus containment and return; do not build a second focus trap.
+
+`FocusScope` is an advanced root-only export from `@react-aria/focus` for custom focus containment/restoration. Existing overlay behavior is the default. Advanced structural contexts are `ContentContext`, `HeaderContext`, `FooterContext`, `ButtonGroupContext`, `GroupContext` and `CornerActionsContext`; they provide defaults rather than visible UI.
+
+## File input
+
+For file selection, `FileTrigger` wraps one pressable child. `DropZone` receives dropped items; use the exported `isFileDropItem` guard, then call `getFile()` on each narrowed item. The application validates type/size and handles upload. Pair a visible browse button with drag/drop when useful; do not rely on drag as the only path.
+
+```tsx
+import { Button, DropZone, FileTrigger, isFileDropItem, Text } from '@godaddy/antares';
+
+<DropZone
+  onDrop={async (event) => {
+    const files = await Promise.all(event.items.filter(isFileDropItem).map((item) => item.getFile()));
+    handleFiles(files);
+  }}
+>
+  <Text slot="label">Drop files here or browse.</Text>
+  <FileTrigger onSelect={(files) => files && handleFiles(Array.from(files))}>
+    <Button>Browse files</Button>
+  </FileTrigger>
+</DropZone>;
+```
+
+Here `handleFiles` is the consumer application's validation/upload callback. `acceptedFileTypes` is only a picker filter; validate again before upload. Handle directory and text items separately only when the product accepts them.
+
+`isTextDropItem` and `isDirectoryDropItem` narrow those other item types. The public `useDrop` hook is a lower-level React Aria export for a custom drop surface. FileTrigger is an Antares hidden-input/press composition; DropZone uses RAC drop behavior. Keep a keyboard-accessible browse path available.
+
+## Progress, pagination and feedback
+
+`ProgressBar` is composable: the label, value display, track and description are explicit children. `CircularProgress` is a compact alternative. Both represent an operation; `RangeField` accepts input and `GaugeChart` displays a measured score.
+
+```tsx
+import { Box, Label, ProgressBar, Text } from '@godaddy/antares';
+
+<ProgressBar value={60}>
+  <Label>Uploading</Label>
+  <Box slot="value" />
+  <Box slot="track" />
+  <Text slot="description">Please keep this page open.</Text>
+</ProgressBar>;
+```
+
+`Pagination` has one-based state and intentionally leaves page count, separator and page-size selector to the consumer. Give the region, previous/next buttons and single page input accessible names. `PaginationDots` does not replace page controls. For cursor-based data, omit `pageCount` and disable Next when there is no next page.
+
+`ProgressSteps` contains `ProgressStep` children and uses zero-based `currentStep`; a step's `onPress` enables navigation. `Carousel` uses Embla rather than a RAC collection; check its installed API for slide content and controls. Keep a finite panel gallery's labels and keyboard navigation meaningful.
+
+`Alert` supplies a persistent in-page live alert; avoid using it for ordinary static copy. `Tag` is a static status/category span (`TagContext` provides advanced defaults). `MetricsLockup` composes a KPI label, value, trend and optional contextual tooltip.
diff --git a/.agents/skills/antares-builder/references/layout-and-styling.md b/.agents/skills/antares-builder/references/layout-and-styling.md
new file mode 100644
index 0000000000..26073931ed
--- /dev/null
+++ b/.agents/skills/antares-builder/references/layout-and-styling.md
@@ -0,0 +1,53 @@
+# Layout and styling
+
+Read this for layout, responsive CSS, typography, media, icons or consistent component sizing.
+
+## Select the layout primitive
+
+- `Flex` arranges a row or column, with wrapping and alignment.
+- `Grid` arranges two dimensions, named areas or card/form grids. `columns` accepts a CSS string such as `repeat(3, minmax(0, 1fr))`.
+- `Box` provides a surface or semantic `as` wrapper. Flex and Grid already extend Box; avoid extra wrappers solely for shared spacing or surface props.
+- `Header`, `Content` and `Footer` define component regions; `ButtonGroup` groups actions, `Group` groups controls, and `CornerActions` positions corner controls. These Antares structural parts extend Flex and can receive styling from a parent field or overlay context.
+
+Use spacing scale props (`xs`, `sm`, `md`, `lg`, `xl`, `2xl`) where supported, and logical properties for directional layout. Keep DOM reading order consistent with visual order.
+
+## Make the layout responsive
+
+Antares has no viewport breakpoints or Chakra-like responsive prop objects. Use the application's media/container queries. Layout props write inline styles: when CSS changes a property at breakpoints, omit that JSX prop and define its base and responsive values in CSS.
+
+```tsx
+// columns is intentionally left to the stylesheet; gap stays constant.
+<Grid className={styles.cards} gap="md">{children}</Grid>
+```
+
+```css
+.cards {
+  grid-template-columns: minmax(0, 1fr);
+}
+
+@media (min-width: 48rem) {
+  .cards {
+    grid-template-columns: repeat(3, minmax(0, 1fr));
+  }
+}
+```
+
+Use the project's actual breakpoint values. Check long labels, zoom and narrow containers. Portaled overlays do not inherit container queries from the trigger's original DOM ancestry.
+
+## Size and visual treatment
+
+Prefer component variants, emphasis and size props before CSS overrides. `SizeProvider size="sm" | "md" | "lg"` optionally scopes adopted components, renders no element and can cross a portal. The nearest scope wins; an explicit component size overrides it.
+
+Adopted families include Text/Detail/Heading/Label, Button/LinkButton, TextField/NumberField/Select, date pickers/Calendar, TextLockup and Modal/Drawer/Popover/Tooltip. Other components keep their own size behavior. Responsive `--antares-size` is documented for TextLockup (`xs` through `2xl`); do not assume it sizes every component. An explicit TextLockup size takes precedence.
+
+Extend styles through `className` and confirmed state attributes such as `[data-selected]`, `[data-invalid]` and `[data-focus-visible]`. Preserve visible focus. Use existing application/theme tokens for custom CSS rather than inventing token names or copying another library's theming API.
+
+## Typography, media and icons
+
+- `Heading` is RAC-backed semantic heading content. Set `level` for document rank independently of visual `size`.
+- `Text` supplies body copy; `Detail` supplies secondary metadata. `TextLockup` coordinates eyebrow, title and description with suitable heading semantics.
+- `Image` wraps a native image: provide meaningful `alt`, or `alt=""` when decorative.
+- `Avatar` presents identity; compose Image and fallback Text using the installed version's examples.
+- `Icon` uses Antares's icon system. Verify the icon identifier in the installed package/docs. Name an icon-only control on the control; hide decorative icons from assistive technology. The advanced `set`, `ondemand` and `parser` exports configure icon sets/loading/parsing, rather than adding a new UI component.
+
+`BoxContext`, `HeadingContext`, `TextContext`, `ImageContext` and `IconContext` are public advanced defaults/context APIs. Prefer ordinary props and parent compositions for routine UI.
diff --git a/.agents/skills/antares-builder/references/setup.md b/.agents/skills/antares-builder/references/setup.md
new file mode 100644
index 0000000000..b0b51d6db0
--- /dev/null
+++ b/.agents/skills/antares-builder/references/setup.md
@@ -0,0 +1,47 @@
+# Consumer setup
+
+Read this for package installation, import resolution, missing CSS or framework integration. Resolve API differences using the installed package's metadata, public types and matching README.
+
+## Install and import
+
+Add `@godaddy/antares` using the application's package manager. Respect the React and React DOM peer-dependency ranges declared by the package being installed.
+
+```tsx
+import { Button, Flex, Text } from '@godaddy/antares';
+// Public subpaths allow focused component JS/CSS imports:
+import { Button } from '@godaddy/antares/Button';
+import { Flex } from '@godaddy/antares/Layout';
+```
+
+Subpaths follow component families rather than every exported name: charts come from `@godaddy/antares/Chart`, structural parts from `@godaddy/antares/Structure`, RangeCalendar from `Calendar`, and both date-picker families from `DatePicker`. Confirm the public export map before constructing an import path.
+
+The root barrel loads CSS custom properties as a side effect; component subpaths ship CSS through their JS chunks. Use the bundler's CSS pipeline. Do not add guessed stylesheet paths or copy library source. Ordinary rendering needs no Antares provider.
+
+Date constructors and helpers are available separately from `@godaddy/antares/date`, which re-exports `@internationalized/date`. They are intentionally absent from the root barrel. Import component props/types from the same public path as the component.
+
+## Framework integration
+
+- **Vite SPA:** standard CSS import handling is sufficient.
+- **Next.js:** add `@godaddy/antares` to the existing `transpilePackages` array for package CSS.
+- **Remix/Vite SSR:** add `@godaddy/antares` to the existing `ssr.noExternal` array.
+- **Other bundlers:** confirm that CSS imports from `node_modules` are processed.
+
+```js
+// Merge into the existing Next.js configuration.
+const nextConfig = {
+  transpilePackages: ['@godaddy/antares']
+};
+```
+
+```ts
+// Merge into the existing Vite SSR configuration.
+import { defineConfig } from 'vite';
+
+export default defineConfig({
+  ssr: { noExternal: ['@godaddy/antares'] }
+});
+```
+
+Preserve unrelated configuration entries. In Next.js App Router, put `"use client"` on the boundary that owns hooks, event handlers or browser APIs. Inspect the actual import/rendering path when diagnosing server/client errors.
+
+For date and number formatting, use the application's locale setup. If an explicit React Aria `I18nProvider` is needed, import it from an explicitly declared dependency rather than assuming Antares exports it.
diff --git a/.claude/skills/antares-builder b/.claude/skills/antares-builder
new file mode 120000
index 0000000000..68a5139730
--- /dev/null
+++ b/.claude/skills/antares-builder
@@ -0,0 +1 @@
+../../.agents/skills/antares-builder
\ No newline at end of file

From 3694f8218cc6ad55f7e9f0ed6460987d33c88536 Mon Sep 17 00:00:00 2001
From: rmojica-godaddy <rmojica@godaddy.com>
Date: Wed, 21 Oct 2026 09:50:19 -0500
Subject: [PATCH 2/4] fix(skills): tighten antares-builder guidance, add eval
 suite

Adds evals/evals.json (12 cases) and trigger-evals.json for the
antares-builder skill, built with skill-creator and validated against
a full with/without-skill benchmark.

Fixes informed by that benchmark and by cross-checking guidance against
the real component source:
- Move focus to the first invalid field on a failed submission
  (fields-and-validation).
- Don't unmount a step/panel's stateful children (e.g. a Carousel) when
  switching steps - keep mounted, toggle visibility.
- Trim repeated "*Context is an advanced API" disclaimers into one
  general note.
- Describe PaginationDots as a passive current-page indicator with no
  ellipsis/page-omission support, matching its real implementation
  (resolves PR review comment on component-decision-tree.md).
- SKILL.md/setup.md: point API discovery at the real Antares repo
  instead of a dead anchor link (resolves PR review comment).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 .agents/skills/antares-builder/SKILL.md       |   6 +-
 .../skills/antares-builder/evals/evals.json   | 143 ++++++++++++++++++
 .../evals/files/contact-form.tsx.txt          |  17 +++
 .../evals/files/dashboard-data.json           |  45 ++++++
 .../antares-builder/evals/trigger-evals.json  |  82 ++++++++++
 .../references/component-decision-tree.md     |   2 +-
 .../references/composition-patterns.md        |  16 +-
 .../references/layout-and-styling.md          |   2 +-
 .../antares-builder/references/setup.md       |   2 +-
 9 files changed, 304 insertions(+), 11 deletions(-)
 create mode 100644 .agents/skills/antares-builder/evals/evals.json
 create mode 100644 .agents/skills/antares-builder/evals/files/contact-form.tsx.txt
 create mode 100644 .agents/skills/antares-builder/evals/files/dashboard-data.json
 create mode 100644 .agents/skills/antares-builder/evals/trigger-evals.json

diff --git a/.agents/skills/antares-builder/SKILL.md b/.agents/skills/antares-builder/SKILL.md
index 9fdb4afdf0..a5d9946791 100644
--- a/.agents/skills/antares-builder/SKILL.md
+++ b/.agents/skills/antares-builder/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: antares-builder
-description: Build, adapt, or review React interfaces with @godaddy/antares. Use for component selection and composition, forms, accessible interactions, responsive layouts, charts, and consumer setup. Do not use for authoring the Antares library itself.
+description: Build, adapt, fix, or review React interfaces with @godaddy/antares. Use for component selection and composition, forms, accessible interactions, responsive layouts, charts (including chart data and rendering bugs), and consumer setup. Do not use for authoring the Antares library itself.
 ---
 
 # Antares Builder
@@ -13,7 +13,9 @@ Follow the steps relevant to the request. Load only the reference sections neede
 
 Inspect `package.json`, the lockfile, framework configuration and neighboring UI. Identify the Antares version, package manager, routing, form library, CSS conventions and locale. Preserve those conventions when adapting existing UI.
 
-Check the installed package's public exports/types before using an unfamiliar API. Follow [API and documentation discovery](references/setup.md#resolve-the-installed-api-and-documentation) for commands, official sources and mismatches; a consumer may not have the library's source checkout. Adapt these references to that installed API. For installation, imports, CSS failures or server/client boundaries, read the relevant setup sections.
+Resolve the Antares version used by the consuming application and verify its public exports and types before using unfamiliar APIs. Use the [Antares repository](https://github.com/godaddy/antares) for documentation matching that version. When sources disagree, prioritize the installed public API over documentation and this skill's examples.
+
+For installation, imports, CSS failures or server/client boundaries, read the relevant [setup](references/setup.md) sections.
 
 Use public root or subpath imports. Do not derive Antares APIs from another design system or import `#components/*`, `dist` files or transitive internals.
 
diff --git a/.agents/skills/antares-builder/evals/evals.json b/.agents/skills/antares-builder/evals/evals.json
new file mode 100644
index 0000000000..7c883b983a
--- /dev/null
+++ b/.agents/skills/antares-builder/evals/evals.json
@@ -0,0 +1,143 @@
+{
+  "skill_name": "antares-builder",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Adapt the supplied contact form to Antares. Keep ExistingContactForm and its save prop. Use Antares field components and no third-party form library. Validate email, preserve its label and help, prevent duplicate saves, and announce success or a retryable error.",
+      "expected_output": "An Antares form with inline field validation and async saving.",
+      "files": [
+        "evals/files/contact-form.tsx.txt"
+      ],
+      "assertions": [
+        "Uses TextField, Label, Input and FieldError with associated help.",
+        "Invalid email activates the Antares field error state, shows its associated FieldError, receives focus, and does not call save.",
+        "Valid submission calls save({ email }); pending requests prevent duplicate saves.",
+        "Failure retains the value and announces an error; success is announced only after saving resolves."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Build Antares preferences for email/SMS opt-ins, one of three shipping plans, and a notifications toggle. Show current choices and support keyboard use.",
+      "expected_output": "Working independent, exclusive and on/off preferences.",
+      "files": [],
+      "assertions": [
+        "A labeled CheckboxGroup allows independent email and SMS choices.",
+        "A labeled RadioGroup keeps exactly one shipping plan selected.",
+        "A labeled Switch controls notifications; keyboard changes update displayed choices."
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "Build an Antares form with a required country popup and a visible multi-select region list. Include a country option with an icon and description. Show selections and country errors; changing country must preserve regions.",
+      "expected_output": "A working Select and multi-select ListBox with country validation.",
+      "files": [],
+      "assertions": [
+        "Uses a labeled Select with a trigger, SelectOptions and SelectItem.",
+        "Uses an Antares multi-select ListBox with an accessible name (e.g. aria-label), stable item IDs, and accessible option labels and descriptions.",
+        "Selections update correctly; missing country blocks submission with an associated error, and country changes preserve regions."
+      ]
+    },
+    {
+      "id": 4,
+      "prompt": "Use Antares for a Rename/Duplicate menu, a popover filter form, and help shown on hover or focus. Wire the actions and make all triggers keyboard accessible.",
+      "expected_output": "Menu, Popover and Tooltip used for their matching interactions.",
+      "files": [],
+      "assertions": [
+        "MenuTrigger, Menu and MenuItem invoke working Rename/Duplicate handlers.",
+        "PopoverTrigger opens the filter form; TooltipTrigger shows non-interactive help on hover or focus.",
+        "Triggers have accessible names; menu/popover support keyboard access, dismissal and focus return."
+      ]
+    },
+    {
+      "id": 5,
+      "prompt": "Add an Antares stay date-range picker with a visible label. Make only 2026-12-25 unavailable, preserve selected start and end as date-only values, and support keyboard selection and focus return.",
+      "expected_output": "An accessible Antares date-range picker with one unavailable date and timezone-stable values.",
+      "files": [],
+      "assertions": [
+        "DateRangePicker has a visible label, working trigger and DateRangePickerCalendar.",
+        "Selection updates date-only start/end values without timezone shifts; only 2026-12-25 is unavailable.",
+        "Keyboard users can open, select a range, dismiss the calendar, and return focus to the trigger."
+      ]
+    },
+    {
+      "id": 6,
+      "prompt": "Build an Antares FAQ with at most one answer open, plus Profile/Billing tabs. Support keyboard use and accessible expanded/selected states.",
+      "expected_output": "A working Accordion and Tabs interface.",
+      "files": [],
+      "assertions": [
+        "Accordion coordinates Collapsible sections with at most one answer open.",
+        "Tabs has a named TabList and matching Tab/TabPanel IDs within TabPanels.",
+        "Keyboard interaction updates content and expanded/selected states."
+      ]
+    },
+    {
+      "id": 7,
+      "prompt": "Build ConfirmOrder with Antares and an onConfirm(): Promise<void> prop. Review order opens a titled modal. Allow Back/Escape before submission; block closing and duplicate requests while pending. Keep errors open, close on success, and return focus to the trigger.",
+      "expected_output": "A modal that follows the async confirmation lifecycle.",
+      "files": [],
+      "assertions": [
+        "The titled Modal opens from Review order, traps focus and blocks background interaction.",
+        "Confirm calls onConfirm; failure keeps an error visible, and success closes the modal.",
+        "Pending confirmation blocks duplicate requests and all dismissal paths.",
+        "Back/Escape dismiss before submission; closing restores focus to Review order."
+      ]
+    },
+    {
+      "id": 8,
+      "prompt": "Build an Antares product grid: one column below 48rem, three at or above it. Use a medium gap and the existing stylesheet; long names must not overflow the page.",
+      "expected_output": "A responsive Grid styled through consumer CSS.",
+      "files": [],
+      "assertions": [
+        "Stylesheet rules set one column below 48rem and three at or above it, without conflicting inline columns.",
+        "Uses supported medium spacing.",
+        "Long names and narrow containers cause no horizontal page overflow."
+      ]
+    },
+    {
+      "id": 9,
+      "prompt": "Build RevenueDashboard with Antares and dashboard-data.json: regional revenue in USD, monthly revenue with February missing, traffic share, and health 3/5. Preserve the data, provide text equivalents, and support 390px and 1024px. Export the component and stylesheet.",
+      "expected_output": "A responsive, accessible dashboard with accurate charts.",
+      "files": [
+        "evals/files/dashboard-data.json"
+      ],
+      "assertions": [
+        "Regional revenue and traffic shares match the supplied data, labels and units.",
+        "Months stay chronological; February remains missing, not zero or an interpolated line.",
+        "GaugeChart shows value 3 with five segments and a 3/5 label.",
+        "Charts have accessible names and text/table equivalents, and render without page overflow at 390px and 1024px."
+      ]
+    },
+    {
+      "id": 10,
+      "prompt": "Using only the installed public Antares API, advise whether Antares supports a searchable country selector. Work offline. Do not edit files, install dependencies or compile. If no public Antares search control exists, explain the gap and the closest supported Antares components; do not recommend another library.",
+      "expected_output": "An evidence-based recommendation limited to the installed public Antares API.",
+      "files": [],
+      "assertions": [
+        "Component and prop claims cite installed Antares public exports or declarations only.",
+        "Recommends a verified keyboard-accessible Antares search control, or explains that none exists and identifies the closest supported Antares components without inventing exports.",
+        "Respects offline, advice-only scope; does not edit files, install dependencies, compile, or recommend another library."
+      ]
+    },
+    {
+      "id": 11,
+      "prompt": "Build a document library: let users browse or drag-drop files to upload, show the uploaded files in a paginated grid of cards, and let each file be removed.",
+      "expected_output": "A working upload surface with a paginated, removable card grid of uploaded files.",
+      "files": [],
+      "assertions": [
+        "FileTrigger offers a keyboard-accessible browse button and DropZone accepts drag/drop; both add to the same uploaded-files list.",
+        "Uploaded files render as Cards with stable IDs and accessible names; Pagination has named previous/next controls and reflects the current/total pages correctly.",
+        "Removing a file updates the card grid and the pagination count without losing the other uploaded files."
+      ]
+    },
+    {
+      "id": 12,
+      "prompt": "Build a 3-step onboarding wizard: a ProgressSteps indicator tracks the current step, and the middle step shows a feature carousel users can browse with next/prev controls.",
+      "expected_output": "A working wizard with step progress and a keyboard-accessible feature carousel.",
+      "files": [],
+      "assertions": [
+        "ProgressSteps shows the zero-based currentStep and the middle step's Carousel supports keyboard and button navigation between slides, each with a meaningful label.",
+        "Advancing or returning between wizard steps preserves state correctly without resetting unrelated progress."
+      ]
+    }
+  ]
+}
diff --git a/.agents/skills/antares-builder/evals/files/contact-form.tsx.txt b/.agents/skills/antares-builder/evals/files/contact-form.tsx.txt
new file mode 100644
index 0000000000..276185315d
--- /dev/null
+++ b/.agents/skills/antares-builder/evals/files/contact-form.tsx.txt
@@ -0,0 +1,17 @@
+type Values = { email: string };
+
+export function ExistingContactForm({ save }: { save: (values: Values) => Promise<void> }) {
+  return (
+    <form>
+      <label htmlFor="contact-email">Email</label>
+      <p id="contact-email-help">We'll send receipts here.</p>
+      <input
+        id="contact-email"
+        type="text"
+        autoComplete="email"
+        aria-describedby="contact-email-help"
+      />
+      <button type="submit">Save contact</button>
+    </form>
+  );
+}
diff --git a/.agents/skills/antares-builder/evals/files/dashboard-data.json b/.agents/skills/antares-builder/evals/files/dashboard-data.json
new file mode 100644
index 0000000000..2ebe5289bc
--- /dev/null
+++ b/.agents/skills/antares-builder/evals/files/dashboard-data.json
@@ -0,0 +1,45 @@
+{
+  "currency": "USD",
+  "regions": [
+    {
+      "id": "na",
+      "region": "North America",
+      "revenue": 12000
+    },
+    {
+      "id": "eu",
+      "region": "Europe",
+      "revenue": 9000
+    }
+  ],
+  "monthlyRevenue": [
+    {
+      "month": "2026-01-01",
+      "revenue": 12000
+    },
+    {
+      "month": "2026-02-01",
+      "revenue": null
+    },
+    {
+      "month": "2026-03-01",
+      "revenue": 15000
+    }
+  ],
+  "traffic": [
+    {
+      "id": "organic",
+      "name": "Organic",
+      "value": 70
+    },
+    {
+      "id": "direct",
+      "name": "Direct",
+      "value": 30
+    }
+  ],
+  "health": {
+    "value": 3,
+    "segments": 5
+  }
+}
diff --git a/.agents/skills/antares-builder/evals/trigger-evals.json b/.agents/skills/antares-builder/evals/trigger-evals.json
new file mode 100644
index 0000000000..ff3988589d
--- /dev/null
+++ b/.agents/skills/antares-builder/evals/trigger-evals.json
@@ -0,0 +1,82 @@
+[
+  {
+    "query": "Build an Antares contact form with validation and retryable saving.",
+    "should_trigger": true
+  },
+  {
+    "query": "Our app uses Antares. What fits a compact Grid/List view switch?",
+    "should_trigger": true
+  },
+  {
+    "query": "can u fix our antares filters? removing the last chip crashes",
+    "should_trigger": true
+  },
+  {
+    "query": "Fix missing months in our Antares revenue chart.",
+    "should_trigger": true
+  },
+  {
+    "query": "Review our Antares checkout dialog for focus and async confirmation bugs.",
+    "should_trigger": true
+  },
+  {
+    "query": "Our Antares app is missing styles on one route. Help diagnose the consumer setup.",
+    "should_trigger": true
+  },
+  {
+    "query": "Add a required Antares date-range picker that keeps date-only values.",
+    "should_trigger": true
+  },
+  {
+    "query": "Build an accessible Antares dashboard with regions, traffic share and health.",
+    "should_trigger": true
+  },
+  {
+    "query": "Antares Select or ListBox for a visible multi-select region picker?",
+    "should_trigger": true
+  },
+  {
+    "query": "Build a responsive Antares product grid with named icon-only actions.",
+    "should_trigger": true
+  },
+  {
+    "query": "Change the Antares library Button source and its tests.",
+    "should_trigger": false
+  },
+  {
+    "query": "Add a public Combobox to the Antares library with exports and stories.",
+    "should_trigger": false
+  },
+  {
+    "query": "Refactor focus management inside the Antares Modal source.",
+    "should_trigger": false
+  },
+  {
+    "query": "Fix a chart normalization hook in Antares library internals.",
+    "should_trigger": false
+  },
+  {
+    "query": "Write release notes and publishing config for Antares.",
+    "should_trigger": false
+  },
+  {
+    "query": "Build a React settings form with the app's existing controls; do not use Antares.",
+    "should_trigger": false
+  },
+  {
+    "query": "Add a country picker using the app's existing UI; do not use Antares.",
+    "should_trigger": false
+  },
+  {
+    "query": "Build a plain HTML/CSS landing page without React or a component library.",
+    "should_trigger": false
+  },
+  {
+    "query": "Fix Nx build caching in the Antares repo; no UI changes.",
+    "should_trigger": false
+  },
+  {
+    "query": "Fix the backend endpoint for Antares revenue data; do not change the Antares UI.",
+    "should_trigger": false
+  }
+]
diff --git a/.agents/skills/antares-builder/references/component-decision-tree.md b/.agents/skills/antares-builder/references/component-decision-tree.md
index f0ed4aab08..9c6f51c77e 100644
--- a/.agents/skills/antares-builder/references/component-decision-tree.md
+++ b/.agents/skills/antares-builder/references/component-decision-tree.md
@@ -32,7 +32,7 @@ Read [actions and slots](composition-patterns.md#actions-slots-and-state) or [co
 - Expand a rail/panel within page flow → `InlineDrawer`.
 - Replace peer panels in one view → `Tabs`.
 - Communicate wizard stages → `ProgressSteps` with `ProgressStep`.
-- Move through a dataset's pages → `Pagination`; decorative page omissions → `PaginationDots`.
+- Move through a dataset's pages → `Pagination`; a passive current-page dot indicator (one dot per page, no ellipsis or page-omission support) → `PaginationDots`.
 - Browse sequential gallery/feature panels → `Carousel`.
 
 See [disclosure and tabs](composition-patterns.md#disclosure-and-tabs) and [progress, pagination and feedback](composition-patterns.md#progress-pagination-and-feedback).
diff --git a/.agents/skills/antares-builder/references/composition-patterns.md b/.agents/skills/antares-builder/references/composition-patterns.md
index b257ba6576..8f49096ca3 100644
--- a/.agents/skills/antares-builder/references/composition-patterns.md
+++ b/.agents/skills/antares-builder/references/composition-patterns.md
@@ -2,11 +2,13 @@
 
 Read only the sections relevant to the task. These shapes are verified against the package's component READMEs and examples. Use the consumer's installed types for detailed props and adapt data and handlers to the product. RAC conventions explain behavior but do not replace Antares's explicit children and slots.
 
+Most composed parts also publish a matching `*Context` (for example `ButtonContext`, `InputContext`, `AccordionContext`, `ChipContext`) that lets an advanced consumer set subtree-wide defaults; ordinary composition through explicit children and props never needs these.
+
 ## Actions, slots and state
 
 `Button` uses RAC button behavior; `LinkButton` uses link behavior. `Pressable` adds press/focus/hover behavior to exactly one child that forwards its ref and DOM/ARIA props, without rendering a wrapper. Prefer the semantic Button/LinkButton when they fit. Name icon-only controls on the control itself.
 
-Parents publish behavior and presentation through slots. Keep field triggers as `Button slot="trigger"`, steppers as `slot="decrement"`/`slot="increment"`, and dismissal as `slot="close"`. Slot names are parent-specific. `ButtonContext` is an advanced defaults API; ordinary compositions do not require a custom provider. Button omits RAC's `isPending` prop; use application-owned pending state and supported disabled/content props.
+Parents publish behavior and presentation through slots. Keep field triggers as `Button slot="trigger"`, steppers as `slot="decrement"`/`slot="increment"`, and dismissal as `slot="close"`. Slot names are parent-specific. Button omits RAC's `isPending` prop; use application-owned pending state and supported disabled/content props.
 
 Match the actual state model: field `value`/`onChange`, collection `selectedKeys`/`onSelectionChange`, boolean `isSelected`/`onChange`, and disclosure `isExpanded`/`onExpandedChange` are not interchangeable. Use defaults for uncontrolled state, or update state from the controlled callback; do not combine both modes accidentally.
 
@@ -14,7 +16,7 @@ Match the actual state model: field `value`/`onChange`, collection `selectedKeys
 
 `TextField` and `NumberField` provide the field relationship, while children provide visible parts. The field's `isInvalid` state controls whether `FieldError` renders. Use `Text slot="description"` for persistent help.
 
-Set `name` for native form submission and use supported root props such as `isRequired`, `isDisabled` and `isInvalid`. Keep the application's form/validation library and connect its state to the exact Antares value/change API. Place controls in a semantic form and choose submit/reset button types deliberately. The following field fragments assume `emailError` comes from that validation state.
+Set `name` for native form submission and use supported root props such as `isRequired`, `isDisabled` and `isInvalid`. Keep the application's form/validation library and connect its state to the exact Antares value/change API. Place controls in a semantic form and choose submit/reset button types deliberately. On a failed submission, move focus to the first invalid field so assistive technology announces its error immediately; do not leave focus on the submit control. The following field fragments assume `emailError` comes from that validation state.
 
 ```tsx
 import { Button, FieldError, Group, Input, Label, NumberField, Text, TextArea, TextField } from '@godaddy/antares';
@@ -43,7 +45,7 @@ import { Button, FieldError, Group, Input, Label, NumberField, Text, TextArea, T
 
 An `Input` inside NumberField is numeric because the field supplies its context. Do not switch it to a plain TextField for exact numeric behavior. A `Button slot="control"` inside a TextField `Group` is an interactive affix. For a required group of independent options, use `CheckboxGroup`; for one exclusive answer, `RadioGroup`. Their composed structure is `Label`, `Group` with items, optional description and `FieldError`.
 
-`CheckboxIndicator` supplies the visual check in custom Checkbox compositions. A standalone Checkbox or Switch needs visible children or an accessible name. `RangeField` uses RAC Slider behavior and supports multiple thumb values; supply corresponding `thumbLabels` for a range. `InputContext`, `TextAreaContext`, `LabelContext` and `FieldErrorContext` are advanced field-part context APIs.
+`CheckboxIndicator` supplies the visual check in custom Checkbox compositions. A standalone Checkbox or Switch needs visible children or an accessible name. `RangeField` uses RAC Slider behavior and supports multiple thumb values; supply corresponding `thumbLabels` for a range. The matching field-part contexts are `InputContext`, `TextAreaContext`, `LabelContext` and `FieldErrorContext`.
 
 ```tsx
 import { Checkbox, CheckboxGroup, Group, Label, Radio, RadioGroup } from '@godaddy/antares';
@@ -91,7 +93,7 @@ Use stable IDs/keys for collections. Give composed items `textValue` when visibl
 
 - `MenuTrigger` wraps a trigger and `Menu`; commands are `MenuItem` children. `MenuGroup` groups commands, `MenuSeparator` divides them, and `SubmenuTrigger` connects a submenu. Preserve the menu's keyboard model; arbitrary form controls belong in a Popover.
 - `SegmentedController` contains `SegmentedControllerItem value="..."` children. Its single string `value`/`defaultValue` pairs with `onSelectionChange(value)`. `ToggleButtonGroup` instead uses selection keys and `ToggleButton id="..."` children. Both build on RAC toggle behavior.
-- `ChipGroup` + `ChipList` + `Chip` wrap RAC TagGroup/TagList/Tag behavior. When removal is enabled, the group's `onRemove` must update the consumer's item collection. `ChipButton` is a standalone action. `ChipContext` is an advanced defaults API.
+- `ChipGroup` + `ChipList` + `Chip` wrap RAC TagGroup/TagList/Tag behavior. When removal is enabled, the group's `onRemove` must update the consumer's item collection. `ChipButton` is a standalone action, with its own `ChipContext`.
 - `CardGroup` + `Card` wrap RAC GridList behavior. Name the group and give composed cards stable IDs and `textValue`; `CardSelectionIndicator` optionally displays selection. A standalone Card can be static or use `href`; keep nested controls out of a standalone card link.
 
 ## Dates and locale
@@ -117,7 +119,7 @@ import { parseDate } from '@godaddy/antares/date';
 
 One revealable section uses `Collapsible`; related sections use an `Accordion` group. The trigger must have `slot="trigger"`, and each grouped section needs a stable ID. The Accordion controls `expandedKeys`/`onExpandedChange`; a standalone Collapsible controls `isExpanded`/`onExpandedChange`.
 
-These wrap RAC DisclosureGroup/Disclosure/DisclosurePanel. `InlineDrawer` + `InlineDrawerPanel` use disclosure behavior while occupying page flow. `AccordionContext` and `CollapsibleContext` are advanced context APIs.
+These wrap RAC DisclosureGroup/Disclosure/DisclosurePanel. `InlineDrawer` + `InlineDrawerPanel` use disclosure behavior while occupying page flow. Their contexts are `AccordionContext` and `CollapsibleContext`.
 
 ```tsx
 import { Accordion, Button, Collapsible, CollapsiblePanel, Heading, Text } from '@godaddy/antares';
@@ -176,7 +178,7 @@ import { Button, ButtonGroup, CloseButton, Content, Heading, Modal, ModalTrigger
 
 Wire a confirming action to application logic and close only after the action succeeds. `slot="close"` dismisses, so avoid applying it to a button that must wait for an async operation. `CloseButton` is already named and slotted. React Aria's modal stack supplies focus containment and return; do not build a second focus trap.
 
-`FocusScope` is an advanced root-only export from `@react-aria/focus` for custom focus containment/restoration. Existing overlay behavior is the default. Advanced structural contexts are `ContentContext`, `HeaderContext`, `FooterContext`, `ButtonGroupContext`, `GroupContext` and `CornerActionsContext`; they provide defaults rather than visible UI.
+`FocusScope` is an advanced root-only export from `@react-aria/focus` for custom focus containment/restoration. Existing overlay behavior is the default. The structural contexts are `ContentContext`, `HeaderContext`, `FooterContext`, `ButtonGroupContext`, `GroupContext` and `CornerActionsContext`.
 
 ## File input
 
@@ -221,4 +223,6 @@ import { Box, Label, ProgressBar, Text } from '@godaddy/antares';
 
 `ProgressSteps` contains `ProgressStep` children and uses zero-based `currentStep`; a step's `onPress` enables navigation. `Carousel` uses Embla rather than a RAC collection; check its installed API for slide content and controls. Keep a finite panel gallery's labels and keyboard navigation meaningful.
 
+When a step or panel holds its own state (a Carousel's position, a form draft), keep it mounted and toggle its visibility rather than conditionally rendering it away and back in — unmounting resets that state.
+
 `Alert` supplies a persistent in-page live alert; avoid using it for ordinary static copy. `Tag` is a static status/category span (`TagContext` provides advanced defaults). `MetricsLockup` composes a KPI label, value, trend and optional contextual tooltip.
diff --git a/.agents/skills/antares-builder/references/layout-and-styling.md b/.agents/skills/antares-builder/references/layout-and-styling.md
index 26073931ed..9ab2e146de 100644
--- a/.agents/skills/antares-builder/references/layout-and-styling.md
+++ b/.agents/skills/antares-builder/references/layout-and-styling.md
@@ -50,4 +50,4 @@ Extend styles through `className` and confirmed state attributes such as `[data-
 - `Avatar` presents identity; compose Image and fallback Text using the installed version's examples.
 - `Icon` uses Antares's icon system. Verify the icon identifier in the installed package/docs. Name an icon-only control on the control; hide decorative icons from assistive technology. The advanced `set`, `ondemand` and `parser` exports configure icon sets/loading/parsing, rather than adding a new UI component.
 
-`BoxContext`, `HeadingContext`, `TextContext`, `ImageContext` and `IconContext` are public advanced defaults/context APIs. Prefer ordinary props and parent compositions for routine UI.
+The matching contexts here are `BoxContext`, `HeadingContext`, `TextContext`, `ImageContext` and `IconContext`.
diff --git a/.agents/skills/antares-builder/references/setup.md b/.agents/skills/antares-builder/references/setup.md
index b0b51d6db0..dd86564f48 100644
--- a/.agents/skills/antares-builder/references/setup.md
+++ b/.agents/skills/antares-builder/references/setup.md
@@ -1,6 +1,6 @@
 # Consumer setup
 
-Read this for package installation, import resolution, missing CSS or framework integration. Resolve API differences using the installed package's metadata, public types and matching README.
+Read this for package installation, import resolution, missing CSS or framework integration.
 
 ## Install and import
 

From f13b0f77cf00919890923668003b36ddd991c176 Mon Sep 17 00:00:00 2001
From: rmojica-godaddy <rmojica@godaddy.com>
Date: Wed, 21 Oct 2026 11:11:06 -0500
Subject: [PATCH 3/4] feat(skills): cover the new Skeleton component in
 antares-builder

main merged a new Skeleton component (#396) after this branch diverged.
Add it to the skill instead of leaving it listed as an unsupported gap,
and point consumers at the skill from the package README:

- Remove Skeleton from component-decision-tree.md's API-gaps list and
  add it to the decision tree under information/feedback.
- Document composition-patterns.md guidance: match size/width/
  aspectRatio/rounding to the real layout, and mark the loading region
  with role="status"/aria-busy/aria-label since Skeleton itself is
  aria-hidden.
- Add eval 13 (profile-card loading state) validated with-skill and
  without-skill, 3/3 both configs - kept as a regression guard even
  though it didn't differentiate skill value in this run, since the
  library's own example already matches the pattern closely.
- Add an "AI Agent Skills" section to the antares package README,
  right after the Quick Start import examples, with the install
  command for antares-builder.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 .agents/skills/antares-builder/evals/evals.json       | 11 +++++++++++
 .../references/component-decision-tree.md             |  3 ++-
 .../references/composition-patterns.md                |  2 ++
 packages/@godaddy/antares/README.mdx                  |  8 ++++++++
 4 files changed, 23 insertions(+), 1 deletion(-)

diff --git a/.agents/skills/antares-builder/evals/evals.json b/.agents/skills/antares-builder/evals/evals.json
index 7c883b983a..4431cbea66 100644
--- a/.agents/skills/antares-builder/evals/evals.json
+++ b/.agents/skills/antares-builder/evals/evals.json
@@ -138,6 +138,17 @@
         "ProgressSteps shows the zero-based currentStep and the middle step's Carousel supports keyboard and button navigation between slides, each with a meaningful label.",
         "Advancing or returning between wizard steps preserves state correctly without resetting unrelated progress."
       ]
+    },
+    {
+      "id": 13,
+      "prompt": "Build a profile card that shows Skeleton placeholders matching the final layout (a circular avatar plus two lines of text) while the profile loads, then swaps to the real content once it arrives.",
+      "expected_output": "An accessible loading state that previews the real layout and hands off cleanly to real content.",
+      "files": [],
+      "assertions": [
+        "Skeleton composition matches the final layout: a circular avatar (rounding=\"full\", width equal to height) plus two text-line Skeletons of differing widths.",
+        "The loading region is marked with role=\"status\", aria-busy=\"true\" and a descriptive aria-label while loading.",
+        "Once data resolves, aria-busy is set to false (or removed) and the real content fully replaces the Skeletons — no stale placeholders left visible."
+      ]
     }
   ]
 }
diff --git a/.agents/skills/antares-builder/references/component-decision-tree.md b/.agents/skills/antares-builder/references/component-decision-tree.md
index 9c6f51c77e..d4ffc92832 100644
--- a/.agents/skills/antares-builder/references/component-decision-tree.md
+++ b/.agents/skills/antares-builder/references/component-decision-tree.md
@@ -51,6 +51,7 @@ For layered content, read [modal layers](composition-patterns.md#modal-layers):
 - Operation progress → `ProgressBar` or compact `CircularProgress`; a numeric input belongs to RangeField.
 - Text-first KPI/trend → `MetricsLockup`.
 - Category comparison → `BarChart`; continuous/time trend → `LineChart`; few parts of a whole → `DonutChart`; one measure against a scale → `GaugeChart`.
+- Content still loading → `Skeleton`, composed into the shape of the content it previews.
 
 Read [charts](charts.md) for chart data/accessors, dimensions, axes, legends and accessibility; read [progress, pagination and feedback](composition-patterns.md#progress-pagination-and-feedback) for feedback and navigation contracts.
 
@@ -69,4 +70,4 @@ Read [layout and styling](layout-and-styling.md) for composition and responsive
 
 ## API gaps
 
-Do not infer Antares exports such as `Combobox`, `Table`, `Toast`, `Skeleton`, `EmptyState`, `NativeSelect`, `Link`, `Breadcrumb`, `Sidebar` or `FileUpload` from other libraries. Check the installed export map first. When a required component is unavailable, use semantic HTML or the application's established solution. A separate RAC dependency is an option when its API and styling fit the requirement; it does not create an Antares export. For empty states, Antares typography, media, actions and layout can form a suitable composition.
+Do not infer Antares exports such as `Combobox`, `Table`, `Toast`, `EmptyState`, `NativeSelect`, `Link`, `Breadcrumb`, `Sidebar` or `FileUpload` from other libraries. Check the installed export map first. When a required component is unavailable, use semantic HTML or the application's established solution. A separate RAC dependency is an option when its API and styling fit the requirement; it does not create an Antares export. For empty states, Antares typography, media, actions and layout can form a suitable composition.
diff --git a/.agents/skills/antares-builder/references/composition-patterns.md b/.agents/skills/antares-builder/references/composition-patterns.md
index 8f49096ca3..45eb276701 100644
--- a/.agents/skills/antares-builder/references/composition-patterns.md
+++ b/.agents/skills/antares-builder/references/composition-patterns.md
@@ -226,3 +226,5 @@ import { Box, Label, ProgressBar, Text } from '@godaddy/antares';
 When a step or panel holds its own state (a Carousel's position, a form draft), keep it mounted and toggle its visibility rather than conditionally rendering it away and back in — unmounting resets that state.
 
 `Alert` supplies a persistent in-page live alert; avoid using it for ordinary static copy. `Tag` is a static status/category span (`TagContext` provides advanced defaults). `MetricsLockup` composes a KPI label, value, trend and optional contextual tooltip.
+
+`Skeleton` previews a loading layout; compose several to sketch text, media or cards, matching `size`/`width`/`aspectRatio`/`rounding` to the real content's shape. Each `Skeleton` is hidden from assistive technology, so mark the region it fills with `role="status"`, `aria-busy="true"` and a describing `aria-label`, then set `aria-busy` to `false` (or remove it) once real content replaces the placeholders. Its shimmer already respects reduced motion and `dir="rtl"`; no extra handling needed for those.
diff --git a/packages/@godaddy/antares/README.mdx b/packages/@godaddy/antares/README.mdx
index f64818a7cc..b8755b7f55 100644
--- a/packages/@godaddy/antares/README.mdx
+++ b/packages/@godaddy/antares/README.mdx
@@ -38,6 +38,14 @@ import { BarChart } from '@godaddy/antares/Chart';
 
 This also works with autocomplete in IDEs and LLMs, so you can import from the root package and let your editor/agent suggest the available components.
 
+## AI Agent Skills
+
+Install the `antares-builder` skill so AI coding agents can build with Antares:
+
+```bash
+npx skills add godaddy/antares --skill antares-builder
+```
+
 ## Framework Setup
 
 Antares ships CSS alongside its JavaScript modules. Each component chunk imports a corresponding `.css` file (e.g., `import './src-BZhWcxqJ.css'`). Most bundlers handle this automatically, but some frameworks need extra configuration to process CSS imports from `node_modules`.

From e1673f248a9c175f505d5270abc12277bc171421 Mon Sep 17 00:00:00 2001
From: rmojica-godaddy <rmojica@godaddy.com>
Date: Fri, 23 Oct 2026 11:41:35 -0500
Subject: [PATCH 4/4] fix(skills): address PR review gaps in antares-builder

- Move antares-builder to skills/ at the repo root; remove the
  .agents/skills contributor symlink and .claude/skills consumer symlink
  so contributor tooling stays separate from the published collection.
- Add metadata.version/author to SKILL.md frontmatter.
- Extend Step 2 guidance so the agent verifies that a recommended
  component (not just a fallback) still exists in the installed Antares
  version, since the decision tree reflects one point in release history.
- Add 3 eval cases (14-16) plus installed-types fixtures proving the
  installed public API wins over stale skill guidance for a newer
  install with an unlisted component, an older install missing a
  documented component, and a component with changed props.
- Flesh out the "AI Agent Skills" section in the package README.mdx with
  install/agent-selection guidance matching the root README.
- Fill in apm.yml with license, keywords, type and includes per the
  published APM manifest schema.
---
 .claude/skills/antares-builder                |  1 -
 README.md                                     | 32 +++++++++++++
 apm.yml                                       | 14 ++++++
 packages/@godaddy/antares/README.mdx          | 10 +++-
 .../antares-builder/SKILL.md                  |  7 ++-
 .../antares-builder/evals/evals.json          | 41 +++++++++++++---
 .../evals/files/contact-form.tsx.txt          |  0
 .../evals/files/dashboard-data.json           |  0
 .../files/installed-types-newer.d.ts.txt      | 48 +++++++++++++++++++
 .../files/installed-types-older.d.ts.txt      | 37 ++++++++++++++
 .../installed-types-progressbar.d.ts.txt      | 38 +++++++++++++++
 .../antares-builder/evals/trigger-evals.json  |  0
 .../antares-builder/references/charts.md      |  0
 .../references/component-decision-tree.md     |  0
 .../references/composition-patterns.md        |  0
 .../references/layout-and-styling.md          |  0
 .../antares-builder/references/setup.md       |  0
 17 files changed, 217 insertions(+), 11 deletions(-)
 delete mode 120000 .claude/skills/antares-builder
 create mode 100644 apm.yml
 rename {.agents/skills => skills}/antares-builder/SKILL.md (82%)
 rename {.agents/skills => skills}/antares-builder/evals/evals.json (77%)
 rename {.agents/skills => skills}/antares-builder/evals/files/contact-form.tsx.txt (100%)
 rename {.agents/skills => skills}/antares-builder/evals/files/dashboard-data.json (100%)
 create mode 100644 skills/antares-builder/evals/files/installed-types-newer.d.ts.txt
 create mode 100644 skills/antares-builder/evals/files/installed-types-older.d.ts.txt
 create mode 100644 skills/antares-builder/evals/files/installed-types-progressbar.d.ts.txt
 rename {.agents/skills => skills}/antares-builder/evals/trigger-evals.json (100%)
 rename {.agents/skills => skills}/antares-builder/references/charts.md (100%)
 rename {.agents/skills => skills}/antares-builder/references/component-decision-tree.md (100%)
 rename {.agents/skills => skills}/antares-builder/references/composition-patterns.md (100%)
 rename {.agents/skills => skills}/antares-builder/references/layout-and-styling.md (100%)
 rename {.agents/skills => skills}/antares-builder/references/setup.md (100%)

diff --git a/.claude/skills/antares-builder b/.claude/skills/antares-builder
deleted file mode 120000
index 68a5139730..0000000000
--- a/.claude/skills/antares-builder
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/antares-builder
\ No newline at end of file
diff --git a/README.md b/README.md
index 63a51022c8..4d25f86713 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,7 @@ packages/dev/                     # Dev tooling (storybook-addon-helpers, enviro
 apps/docs/                        # Storybook documentation
 apps/site/                        # Documentation site (Next.js)
 configs/                          # Shared build and test configs
+skills/                           # Consumer-facing agent skills
 ```
 
 ## Packages
@@ -81,6 +82,37 @@ configs/                          # Shared build and test configs
 
 See individual package READMEs for installation and usage instructions.
 
+### Antares Builder skill
+
+[Antares Builder](./skills/antares-builder/SKILL.md) helps coding agents build
+consumer interfaces with the public `@godaddy/antares` API. Run either command
+from your consuming application:
+
+```sh
+npx skills add godaddy/antares --skill antares-builder --agent codex
+```
+
+Or, with [Agent Package Manager (APM)](https://microsoft.github.io/apm/) installed:
+
+```sh
+apm install godaddy/antares --skill antares-builder --target codex
+```
+
+Select your agent with `--agent` for the skills CLI or `--target` for APM; for
+example, use `claude-code` with the skills CLI or `claude` with APM. The installer
+places the skill and its references in the consumer's agent directory.
+
+Then ask your agent, for example:
+
+> Build a responsive settings form with Antares, including validation and a confirmation dialog.
+
+The root [`apm.yml`](./apm.yml) describes the published `skills/` collection.
+Contributor tooling stays in `.agents/skills/`. The collection is versioned
+independently of `@godaddy/antares`; keep its version aligned with the skill's
+`metadata.version` for releases of this single-skill collection. To pin an APM
+release, append `#<git-ref>` to `godaddy/antares` and commit the consumer's
+`apm.yml` and `apm.lock.yaml`.
+
 ## Documentation
 
 Documentation is powered by Storybook and a Next.js docs site.
diff --git a/apm.yml b/apm.yml
new file mode 100644
index 0000000000..47b4cbb62b
--- /dev/null
+++ b/apm.yml
@@ -0,0 +1,14 @@
+name: antares-skills
+version: "0.1.0"
+description: Skills for building React interfaces with the public Antares API.
+author: GoDaddy LLC
+license: MIT
+repository: https://github.com/godaddy/antares
+keywords:
+  - godaddy
+  - antares
+  - react
+  - design-system
+  - skills
+type: skill
+includes: auto
diff --git a/packages/@godaddy/antares/README.mdx b/packages/@godaddy/antares/README.mdx
index b8755b7f55..7021dd044b 100644
--- a/packages/@godaddy/antares/README.mdx
+++ b/packages/@godaddy/antares/README.mdx
@@ -40,12 +40,18 @@ This also works with autocomplete in IDEs and LLMs, so you can import from the r
 
 ## AI Agent Skills
 
-Install the `antares-builder` skill so AI coding agents can build with Antares:
+Install the `antares-builder` skill from your consuming application's directory so AI coding agents can build with Antares:
 
 ```bash
-npx skills add godaddy/antares --skill antares-builder
+npx skills add godaddy/antares --skill antares-builder --agent claude-code
 ```
 
+Select your coding agent with `--agent` (e.g. `claude-code`, `codex`); omit it to be prompted. The installer places the skill and its references into the consumer app's agent directory. Then ask your agent, for example:
+
+> Build a responsive settings form with Antares, including validation and a confirmation dialog.
+
+See the [repository README](https://github.com/godaddy/antares#antares-builder-skill) for the full reference, including an Agent Package Manager (APM) alternative and version-pinning notes.
+
 ## Framework Setup
 
 Antares ships CSS alongside its JavaScript modules. Each component chunk imports a corresponding `.css` file (e.g., `import './src-BZhWcxqJ.css'`). Most bundlers handle this automatically, but some frameworks need extra configuration to process CSS imports from `node_modules`.
diff --git a/.agents/skills/antares-builder/SKILL.md b/skills/antares-builder/SKILL.md
similarity index 82%
rename from .agents/skills/antares-builder/SKILL.md
rename to skills/antares-builder/SKILL.md
index a5d9946791..d924b1c83d 100644
--- a/.agents/skills/antares-builder/SKILL.md
+++ b/skills/antares-builder/SKILL.md
@@ -1,6 +1,9 @@
 ---
 name: antares-builder
 description: Build, adapt, fix, or review React interfaces with @godaddy/antares. Use for component selection and composition, forms, accessible interactions, responsive layouts, charts (including chart data and rendering bugs), and consumer setup. Do not use for authoring the Antares library itself.
+metadata:
+  version: "0.1.0"
+  author: GoDaddy LLC
 ---
 
 # Antares Builder
@@ -11,7 +14,7 @@ Follow the steps relevant to the request. Load only the reference sections neede
 
 ## Step 1 — Read the project context
 
-Inspect `package.json`, the lockfile, framework configuration and neighboring UI. Identify the Antares version, package manager, routing, form library, CSS conventions and locale. Preserve those conventions when adapting existing UI.
+Inspect `package.json`, the lockfile, framework configuration and existing components and pages in the consuming application. Identify the Antares version, package manager, routing, form library, CSS conventions and locale. Preserve those conventions when adapting existing UI.
 
 Resolve the Antares version used by the consuming application and verify its public exports and types before using unfamiliar APIs. Use the [Antares repository](https://github.com/godaddy/antares) for documentation matching that version. When sources disagree, prioritize the installed public API over documentation and this skill's examples.
 
@@ -21,7 +24,7 @@ Use public root or subpath imports. Do not derive Antares APIs from another desi
 
 ## Step 2 — Choose the component by behavior
 
-Identify the action, value, navigation or information the user needs. Read the relevant branch of the [component decision tree](references/component-decision-tree.md) when choosing a component or comparing alternatives. If Antares has no matching export, use the application's established solution or semantic HTML and explain the gap.
+Identify the action, value, navigation or information the user needs. Read the relevant branch of the [component decision tree](references/component-decision-tree.md) when choosing a component or comparing alternatives. The decision tree and examples describe one point in Antares's release history. Before using a component the tree recommends, verify it — and the specific props/children an example shows — still exist in the installed version's public exports and types: a newer install may add components the tree doesn't list yet, and an older install may lack a component the tree recommends or expose different props for it. If no matching export exists, use the application's established solution or semantic HTML and explain the gap.
 
 ## Step 3 — Arrange and style the interface
 
diff --git a/.agents/skills/antares-builder/evals/evals.json b/skills/antares-builder/evals/evals.json
similarity index 77%
rename from .agents/skills/antares-builder/evals/evals.json
rename to skills/antares-builder/evals/evals.json
index 4431cbea66..7df9c29b94 100644
--- a/.agents/skills/antares-builder/evals/evals.json
+++ b/skills/antares-builder/evals/evals.json
@@ -5,9 +5,7 @@
       "id": 1,
       "prompt": "Adapt the supplied contact form to Antares. Keep ExistingContactForm and its save prop. Use Antares field components and no third-party form library. Validate email, preserve its label and help, prevent duplicate saves, and announce success or a retryable error.",
       "expected_output": "An Antares form with inline field validation and async saving.",
-      "files": [
-        "evals/files/contact-form.tsx.txt"
-      ],
+      "files": ["evals/files/contact-form.tsx.txt"],
       "assertions": [
         "Uses TextField, Label, Input and FieldError with associated help.",
         "Invalid email activates the Antares field error state, shows its associated FieldError, receives focus, and does not call save.",
@@ -97,9 +95,7 @@
       "id": 9,
       "prompt": "Build RevenueDashboard with Antares and dashboard-data.json: regional revenue in USD, monthly revenue with February missing, traffic share, and health 3/5. Preserve the data, provide text equivalents, and support 390px and 1024px. Export the component and stylesheet.",
       "expected_output": "A responsive, accessible dashboard with accurate charts.",
-      "files": [
-        "evals/files/dashboard-data.json"
-      ],
+      "files": ["evals/files/dashboard-data.json"],
       "assertions": [
         "Regional revenue and traffic shares match the supplied data, labels and units.",
         "Months stay chronological; February remains missing, not zero or an interpolated line.",
@@ -149,6 +145,39 @@
         "The loading region is marked with role=\"status\", aria-busy=\"true\" and a descriptive aria-label while loading.",
         "Once data resolves, aria-busy is set to false (or removed) and the real content fully replaces the Skeletons — no stale placeholders left visible."
       ]
+    },
+    {
+      "id": 14,
+      "prompt": "The attached file lists our installed Antares version's public type declarations. Build a searchable country selector with autocomplete filtering using Antares. Check the attached declarations before assuming Antares has no combobox.",
+      "expected_output": "An Antares combobox built from the installed version's actual exports.",
+      "files": ["evals/files/installed-types-newer.d.ts.txt"],
+      "assertions": [
+        "Inspects the attached installed declarations rather than relying solely on the skill's API-gaps list, which still says Combobox does not exist.",
+        "Implements the installed Combobox/ComboboxTrigger/ComboboxOptions/ComboboxItem API from the fixture, not a hand-rolled autocomplete or a Select+ListBox substitute.",
+        "Wires selectedKey/onSelectionChange and inputValue/onInputChange per the attached declarations."
+      ]
+    },
+    {
+      "id": 15,
+      "prompt": "The attached file lists our installed Antares version's public exports. Build a profile card with a loading placeholder that previews the final avatar-plus-two-lines layout before data arrives.",
+      "expected_output": "A loading placeholder built only from exports that actually exist at the installed version.",
+      "files": ["evals/files/installed-types-older.d.ts.txt"],
+      "assertions": [
+        "Notices Skeleton is absent from the attached installed exports and does not import or render it, despite the skill's guidance recommending Skeleton for loading placeholders.",
+        "Falls back to a capability the installed exports actually support (e.g. existing progress/loading primitives or a semantic ARIA-busy placeholder) rather than inventing a Skeleton export.",
+        "States to the user that Skeleton isn't available at the installed version and explains what it used instead."
+      ]
+    },
+    {
+      "id": 16,
+      "prompt": "The attached file is our installed Antares version's ProgressBar type declaration. Build a labeled file-upload progress bar with helper text below it, like 'Uploading... 42%'. Use the installed API, not older examples that may still show label/helperText props.",
+      "expected_output": "A ProgressBar composed per the installed declaration, with no removed props.",
+      "files": ["evals/files/installed-types-progressbar.d.ts.txt"],
+      "assertions": [
+        "Composes Label, the value/track Box slots and a Text description per the attached declaration instead of passing label or helperText props to ProgressBar.",
+        "Does not reference a label or helperText prop on ProgressBar anywhere in the output.",
+        "The progress bar still has a correctly associated accessible name and description in the composed markup."
+      ]
     }
   ]
 }
diff --git a/.agents/skills/antares-builder/evals/files/contact-form.tsx.txt b/skills/antares-builder/evals/files/contact-form.tsx.txt
similarity index 100%
rename from .agents/skills/antares-builder/evals/files/contact-form.tsx.txt
rename to skills/antares-builder/evals/files/contact-form.tsx.txt
diff --git a/.agents/skills/antares-builder/evals/files/dashboard-data.json b/skills/antares-builder/evals/files/dashboard-data.json
similarity index 100%
rename from .agents/skills/antares-builder/evals/files/dashboard-data.json
rename to skills/antares-builder/evals/files/dashboard-data.json
diff --git a/skills/antares-builder/evals/files/installed-types-newer.d.ts.txt b/skills/antares-builder/evals/files/installed-types-newer.d.ts.txt
new file mode 100644
index 0000000000..2b2ac8b435
--- /dev/null
+++ b/skills/antares-builder/evals/files/installed-types-newer.d.ts.txt
@@ -0,0 +1,48 @@
+// Installed @godaddy/antares type declarations (partial root export list).
+// This is a NEWER install than the version the antares-builder skill's
+// decision tree and "API gaps" list were written against.
+
+export declare function Button(props: ButtonProps): JSX.Element;
+export declare function TextField(props: TextFieldProps): JSX.Element;
+export declare function Select(props: SelectProps): JSX.Element;
+export declare function ListBox(props: ListBoxProps): JSX.Element;
+
+// Added since the skill's decision tree was written. Not mentioned anywhere
+// in component-decision-tree.md or composition-patterns.md.
+export declare function Combobox(props: ComboboxProps): JSX.Element;
+export declare function ComboboxTrigger(props: ComboboxTriggerProps): JSX.Element;
+export declare function ComboboxOptions(props: ComboboxOptionsProps): JSX.Element;
+export declare function ComboboxItem(props: ComboboxItemProps): JSX.Element;
+
+export interface ComboboxProps<T = object> {
+  /** Accessible label for the combobox trigger/input. */
+  label?: React.ReactNode;
+  /** Collection items rendered as ComboboxItem children. */
+  items?: Iterable<T>;
+  /** Controlled filter text shown in the input. */
+  inputValue?: string;
+  /** Called when the user edits the filter text. */
+  onInputChange?: (value: string) => void;
+  /** Controlled selected item key. */
+  selectedKey?: React.Key | null;
+  /** Called when the selected item changes. */
+  onSelectionChange?: (key: React.Key | null) => void;
+  /** Disallows free text; selection must match a listed item. */
+  allowsCustomValue?: boolean;
+  children?: React.ReactNode;
+}
+
+export interface ComboboxTriggerProps {
+  children?: React.ReactNode;
+}
+
+export interface ComboboxOptionsProps<T = object> {
+  items?: Iterable<T>;
+  children?: React.ReactNode | ((item: T) => React.ReactNode);
+}
+
+export interface ComboboxItemProps {
+  id: React.Key;
+  textValue?: string;
+  children?: React.ReactNode;
+}
diff --git a/skills/antares-builder/evals/files/installed-types-older.d.ts.txt b/skills/antares-builder/evals/files/installed-types-older.d.ts.txt
new file mode 100644
index 0000000000..18c4848f23
--- /dev/null
+++ b/skills/antares-builder/evals/files/installed-types-older.d.ts.txt
@@ -0,0 +1,37 @@
+// Installed @godaddy/antares type declarations (partial root export list).
+// This is an OLDER install than the version the antares-builder skill's
+// decision tree currently documents.
+//
+// Notably absent: Skeleton. The skill's decision tree recommends Skeleton
+// for "content still loading" placeholders, but this installed version
+// predates that component — it is not part of this export list.
+
+export declare function Button(props: ButtonProps): JSX.Element;
+export declare function Avatar(props: AvatarProps): JSX.Element;
+export declare function Text(props: TextProps): JSX.Element;
+export declare function Flex(props: FlexProps): JSX.Element;
+export declare function Box(props: BoxProps): JSX.Element;
+export declare function CircularProgress(props: CircularProgressProps): JSX.Element;
+export declare function ProgressBar(props: ProgressBarProps): JSX.Element;
+
+export interface AvatarProps {
+  src?: string;
+  alt?: string;
+  size?: 'sm' | 'md' | 'lg';
+}
+
+export interface CircularProgressProps {
+  'aria-label'?: string;
+  isIndeterminate?: boolean;
+  value?: number;
+}
+
+export interface ProgressBarProps {
+  'aria-label'?: string;
+  label?: React.ReactNode;
+  helperText?: React.ReactNode;
+  value?: number;
+  isIndeterminate?: boolean;
+}
+
+// No Skeleton export exists in this installed version.
diff --git a/skills/antares-builder/evals/files/installed-types-progressbar.d.ts.txt b/skills/antares-builder/evals/files/installed-types-progressbar.d.ts.txt
new file mode 100644
index 0000000000..1e7bbef829
--- /dev/null
+++ b/skills/antares-builder/evals/files/installed-types-progressbar.d.ts.txt
@@ -0,0 +1,38 @@
+// Installed @godaddy/antares type declarations for ProgressBar.
+//
+// Breaking change from an older skill example or memory: `label` and
+// `helperText` props were REMOVED. ProgressBar is now composed from
+// Label, Box (value/track slots) and Text as children instead.
+
+export interface ProgressBarProps {
+  /** Composed label, value, track, and description. A function receives progress state. */
+  children?: React.ReactNode | ((state: ProgressBarRenderProps) => React.ReactNode);
+
+  /** Accessible value text and default value-slot content. Does not add visible output. */
+  valueLabel?: string;
+
+  /** Visual size of the track. @default 'md' */
+  size?: 'xs' | 'sm' | 'md';
+
+  /** Color intent of the fill. @default 'default' */
+  status?: 'default' | 'success' | 'warning' | 'critical';
+
+  value?: number;
+  minValue?: number;
+  maxValue?: number;
+  isIndeterminate?: boolean;
+  'aria-label'?: string;
+  'aria-labelledby'?: string;
+  'aria-describedby'?: string;
+
+  // NOTE: no `label` prop.
+  // NOTE: no `helperText` prop.
+  // Compose a visible label, value, and description instead:
+  //   <ProgressBar value={42}>
+  //     <Label>Uploading</Label>
+  //     <Box slot="value">42%</Box>
+  //     <Text slot="description">Uploading... 42%</Text>
+  //   </ProgressBar>
+}
+
+export declare function ProgressBar(props: ProgressBarProps): JSX.Element;
diff --git a/.agents/skills/antares-builder/evals/trigger-evals.json b/skills/antares-builder/evals/trigger-evals.json
similarity index 100%
rename from .agents/skills/antares-builder/evals/trigger-evals.json
rename to skills/antares-builder/evals/trigger-evals.json
diff --git a/.agents/skills/antares-builder/references/charts.md b/skills/antares-builder/references/charts.md
similarity index 100%
rename from .agents/skills/antares-builder/references/charts.md
rename to skills/antares-builder/references/charts.md
diff --git a/.agents/skills/antares-builder/references/component-decision-tree.md b/skills/antares-builder/references/component-decision-tree.md
similarity index 100%
rename from .agents/skills/antares-builder/references/component-decision-tree.md
rename to skills/antares-builder/references/component-decision-tree.md
diff --git a/.agents/skills/antares-builder/references/composition-patterns.md b/skills/antares-builder/references/composition-patterns.md
similarity index 100%
rename from .agents/skills/antares-builder/references/composition-patterns.md
rename to skills/antares-builder/references/composition-patterns.md
diff --git a/.agents/skills/antares-builder/references/layout-and-styling.md b/skills/antares-builder/references/layout-and-styling.md
similarity index 100%
rename from .agents/skills/antares-builder/references/layout-and-styling.md
rename to skills/antares-builder/references/layout-and-styling.md
diff --git a/.agents/skills/antares-builder/references/setup.md b/skills/antares-builder/references/setup.md
similarity index 100%
rename from .agents/skills/antares-builder/references/setup.md
rename to skills/antares-builder/references/setup.md