The cell is instance-swapped inside Date Picker - Group when the user switches to Month or Year view. 12 cells are rendered as a 4 × 3 month grid, or 20 cells as a 4 × 5 year grid. Same Figma component for both — only the text label changes.

• Sibling duplication with Date Picker - Item. The two components are the same selectable-cell primitive at different pixel sizes (100×32 vs 32×32) with overlapping state semantics (Default, Today, Selected). Maintaining them as siblings doubles the variant surface and forces the Group panel to instance-swap based on view. C1 · Layer Structure & Naming
• Inner frame is always named Month — even when it's the year cell. The same Figma component is instance-swapped as both a month cell (Jan, Feb, Mar…) and a year cell (2024, 2025…), but the inner auto-layout frame is named Month in all three variants. The layer name lies for half the instances. C1 · Layer Structure & Naming
• State axis is narrower than the sibling day cell. The day cell has Type × State=Enabled|Disabled. This cell has a single Type axis with no State at all. Cells in the same family should share the same state shape — even if specific values differ by kind. C2 · Variant & Property Naming
• Tokens named main/date-picker/day/* are used for non-day cells. The cell's bg and label resolve to main/date-picker/day/color/selected/* and main/date-picker/day/color/unselected/* — but it's rendering a month or year, not a day. The token scope is misleadingly named. Either rename to main/date-picker/cell/* or split into main/picker-cell/{day|month|year}/*. C3 · Token Coverage
• Cell has no 1:1 native primitive. Both SwiftUI DatePicker(.graphical) and Material 3 DatePicker render their own month/year views and don't accept a custom cell view. This Figma component is therefore a reference spec, not a mappable component — should be marked as such or merged into the Picker Cell family. C4 · Native Mappability
• No Disabled variant. When a parent limits the pickable date range, disabled months or years have no token-bound appearance on this cell. The sibling day cell at least ships Disabled on Default and Today — this cell has no Disabled form for any Type. C5 · Interaction State Coverage
• No Pressed, Hover, or Focused variants. Tap feedback (iOS ripple / Android state layer) and keyboard focus ring are not defined. Native pickers supply these automatically, but any custom wrapper has no tokens to apply. C5 · Interaction State Coverage
• Today + Selected collision is unresolved. There is no variant for the common case of the current month/year being the selected one. The design team should decide which presentation wins (ring + fill, fill-only, or a hybrid) and publish a variant. C5 · Interaction State Coverage
• Today ring thickness drifts from the sibling day cell. This cell uses a 1px border; the sibling day cell uses a 1.5px ring. Same visual pattern, different stroke weight — selection/today emphasis should be one token shared across Picker Cell kinds, not per-component values. C6 · Asset & Icon Quality
• Code Connect mappings not registered. Blocked by the native-pickers-own-it direction (C4) and by the pending Picker Cell family unification (C1). Map only once the unified component exists and the wrapper surface is confirmed. C7 · Code Connect Linkability

• Family — Consolidate Date Picker - Item + Month and Year Picker - Item into ONE Picker Cell. Both are selectable cells with identical state semantics (Default / Today / Selected); only pixel size (32×32 vs 100×32) and corner radius (30px pill vs 8px rounded-rect) differ. Proposed schema: kind = day | month | year + state = default | today | selected | disabled (plus range-middle | prev-next exposed only when kind=day). Collapses 10 sibling variants across two components into one component with two clean axes. A single native PickerCell composable renders the correct dimensions, radius, and typography per kind. Family
• Property — Add a State axis to match the day cell. Even before consolidation, promote the single-axis Type schema into Type × State = Enabled | Disabled | Pressed | Focused to align with the day cell's shape. At minimum, publish Disabled variants for Default, Today, and Selected so the cell is usable in a date-range-restricted picker. Property
• Rename — Fix the inner frame name. The inner auto-layout frame is named Month in all three variants, but the same component is instance-swapped as the year cell too. Rename to Cell or Label Container so it reads true for both Month and Year views. Rename
• Token — Rename main/date-picker/day/* to main/date-picker/cell/*. The shared token scope is named day but also resolves for month and year cells. Rename (or split into main/picker-cell/{day|month|year}/* if treatments intentionally diverge) so the token name honestly describes what it styles. Token
• Token — Share a selection-emphasis token across Picker Cell kinds. Create main/picker-cell/selection/* tokens that resolve to either "fill" or "ring" based on kind, and harmonise the Today ring stroke (1px here, 1.5px on the day cell) on a single border/picker-cell/today token. Token
• State — Add Pressed, Focused, and Today+Selected variants. Extend the state coverage with Pressed and Focused (needed for any custom wrapper rendering tap / keyboard affordances), and publish a decision variant for the common "today is also selected" case. State
• A11y — Flag the 32px height as below minimum target. The 100×32 cell is below WCAG 2.5.5 minimum 44×44 on the vertical axis. If a custom wrapper is ever built, pad the tap zone vertically so the hit area meets 44px. Document on the component so consumers don't ship the tight target outside the native picker context. A11y
• Docs — Mark as reference, not a production component. Given that both platforms render their own month/year views inside the native DatePicker, this cell is a visual reference for the token-styled wrapper, not a component developers rebuild. Add a description banner and a _reference prefix once the Picker Cell family unification lands. Docs