Stepper - Bullet appears at the top or bottom of multi-step flows — most commonly paginated onboarding, swipeable carousels of tutorial cards, and photo galleries where the user needs a minimal position indicator without numerical labels.

• Step count is modeled as 3 sibling components instead of a steps prop. The family ships as Stepper - Bullet - 3 Steps, - 4 Steps, - 5 Steps — three top-level components that differ only by hardcoded count. Same anti-pattern as Stepper - Circular (9 siblings). Should be a single Stepper - Bullet with steps: Int and current: Int — 3× maintenance collapses to 1×, and the component scales to 6, 7, 8+ without new files. C1 · Layer Structure & Naming
• Variant axis highlighted = 1st | 2nd | … | Nth uses ordinal enums instead of an integer. Each sibling has a nested symbol with highlighted=1st, 2nd, 3rd, 4th, 5th to mark the active dot. Ordinals don't compose — the 4-step sibling can't have a "5th" option, and there's no path to current=N+1. Promote to a top-level integer current: 1..steps. C2 · Variant & Property Naming
• Every dot is a raster <img> PNG — 8×8 ellipse baked as an image. Two PNGs per sibling (filled + track) × 3 siblings = six raster assets for what is mathematically a filled circle. Blocks theming (can't retint), breaks at @3x, and ships bytes the native renderer doesn't need. An 8-px Circle() / Box(Modifier.clip(CircleShape)) with a token-bound fill is all that's required. C6 · Asset & Icon Quality
• No native primitive matches — this needs a custom component. SwiftUI has no BulletStepper; Material 3 provides only LinearProgressIndicator and a linear Stepper. Both platforms need a custom EBStepperBullet built from an HStack/Row of Circle/Box shapes. The raster-baked dots make this worse — the dev can't reuse the asset. C4 · Native Mappability
• No completed / upcoming distinction, no pressed / focused states, no connector line. The spec treats every non-current dot identically. Users can't see direction of travel. Tappable-to-jump behavior (common in carousels) has no pressed state modeled. And the 8-px blank gaps between dots would normally be a connector rail in classic bullet steppers. C5 · Interaction State Coverage
• Code Connect mappings not registered. Blocked until the family collapses to one component and the raster dots are replaced with vector circles. Mapping 3 separate siblings would codify the anti-pattern into the tooling. C7 · Code Connect Linkability

• Collapse all 3 siblings into one Stepper - Bullet with steps and current properties. Delete Stepper - Bullet - 3 Steps, - 4 Steps, - 5 Steps as separate components. Create one Stepper - Bullet with steps: 3 | 4 | … | 10 and current: 1 | 2 | … | 10. Variant math drops from 3 top-level × 3–5 highlighted = 12 pre-baked variants to 1 component with runtime-computed fills. Native API: EBStepperBullet(current: Int, total: Int). Family
• Unify Dash + Bullet + Circular under one EBStepper(current:total:style:) API. All three siblings share the same data shape (current + total) and the same token set (main/stepper/color/*). Collapse them into one native component with style: .dash | .bullet | .circular. Figma keeps three component symbols (different visual languages) but they share the same property schema — making migration / swap between styles trivial. Family
• Rename the nested highlighted = 1st | 2nd | … | Nth ordinal axis to an integer current. Ordinal enums don't scale and conflate position with presentation. Use current: Int at the top level and let each dot compute its own fill from index == current ? bg : bg-track. Property
• Replace raster dot PNGs with vector Ellipse fills bound to tokens. Each dot is an 8×8 ellipse — the simplest possible vector. Two fills only: main/stepper/color/bg (active) and main/stepper/color/bg-track (inactive). No PNG assets, resolution-independent, theme-able. Asset
• Add completed vs upcoming differentiation. Optional but common: completed dots use a muted brand tint; upcoming use the track. Model as status: completed | current | upcoming computed per-slot from current. Adds direction-of-travel cue without the user having to count. State
• Spec a connector line between dots (optional variant). Classic bullet steppers draw a 1–2 px line between each dot pair, tinted to match completed (brand) vs upcoming (track). Today the 8-px blank gap reads as isolated markers. Add showConnector: Bool (default off for carousel-style use, on for wizard-style use). Property
• Add an orientation property for vertical layouts. Dot steppers sometimes appear as a vertical list in sidebars or long-form onboarding. Add orientation: horizontal | vertical. Property
• Build as a custom native component. Neither SwiftUI nor Material has a BulletStepper primitive. Ship EBStepperBullet: iOS uses HStack { ForEach(0..<total) { Circle().fill(index == current ? Color.stepperBg : Color.stepperBgTrack).frame(width: 8, height: 8) } }; Android uses Row { repeat(total) { Box(Modifier.size(8.dp).clip(CircleShape).background(if (it == current) EBTokens.stepperBg else EBTokens.stepperBgTrack)) } }. Composition
• Announce "Step X of Y" to screen readers. The component is decorative by default — assistive tech reads nothing. Wrap in a semantic container that announces "Step \(current) of \(total)" (SwiftUI .accessibilityLabel, Compose Modifier.semantics { contentDescription = … }). Also: minimum touch target is 44×44 — if dots are tappable, wrap each in a padded hit area, don't make the 8-px dot itself the target. A11y
• Document the canonical composition and retire the sibling names. Update the sticker sheet page to show one Stepper - Bullet with property controls; add a migration note pointing Stepper - Bullet - N Steps consumers at the new steps prop. Docs