` holding a bare `py-3 px-4 sm:px-6` header plus two nested `p-4 sm:p-6 bg-layer rounded-xl shadow-2xs` inner cards - the details/summary card first, then the tracking-and-items card.
- Header is `grid grid-cols-2 md:grid-cols-4 gap-2 md:gap-5`: `Status` = a `size-2 bg-green-500` dot plus `Order in progress`; `Order number` = `72813820`; `Order date` = `04/08/2024`; `Total` = `$229`.
- First inner card is `grid grid-cols-1 sm:grid-cols-2 md:grid-cols-3 gap-y-7 gap-x-3`. Column 1 is `Shipping address` listing `James Collins`, `280 Suzanne Throughway`, `New York, Breannabury, OR 45801, US`, then `+44 000 000 0001`, with a small `Change address` pencil button carrying `data-hs-overlay="#hs-pro-sheam"`. Column 2 stacks `Contact details` / `jamescollins@site.so` and `Payment method` / a MasterCard brand SVG in a `p-1 border rounded-md` chip beside `MasterCard •••• 4242` - keep that exact card mark and the bullet glyphs.
- Column 3 is an unheaded totals list (`Order summary` is passed as a parameter but never rendered): `Subtotal` `$229`, `Shipping` `Free`, `Estimated Tax` `$0`, `Sale` `-$20` in muted text, then `Total` shown as a small `USD` followed by `$229`. Under it, right-aligned, is a `View or Print receipt` button with a printer icon.
- That card ends with a `pt-6 mt-6 border-t border-line-2` row reading `Something wrong?` plus the underlined link `Exchange or return` with a right chevron, and a right-aligned `Cancel order` button in the destructive text color carrying `data-hs-overlay="#hs-pro-shcom"`.
- Second inner card opens with a single truck-icon line `Estimated delivery: Wednesday, Aug 7 2024` (date `font-semibold`). This variant shows no address line and no `Order details` button in that row.
- Then the 4-segment status timeline (`grid grid-cols-4 gap-x-1 sm:gap-x-3`, `h-1.5` bars): `Order placed` (check icon, 100%), `Preparing order` (current, `animate-ping` dot, `bg-primary` at 100%), `Shipped` (`opacity-50`, 0%), `Delivered` (`opacity-50`, 0%); below `md` it collapses to an `Order status` row showing `Preparing order` and `Shipped`.
- Exactly 3 item rows close the card, each with a `w-24 sm:w-32` photo at `h-40 object-cover rounded-xl` and a `Color` / `Size` / `Quantity` grid: `Nike SB Zoom Blazer Mid Electric` / `$150` / `White` / `US 10` / `1`; `Windrunner` / `$60` struck through with `$40` / `Gray` / `M` / `1`; `White Jeans` / `$39` / `White` / `M` / `1`. The only JS wiring in the block is the two `data-hs-overlay` triggers; their overlay panels are not part of this block.
Token and Tailwind rules:
- Treat source token classes as semantic roles, not fixed class names to blindly copy.
- Map every source `primary` role to the destination project's current primary token/config/CSS variable. Active links, checked states, progress lines, focus rings, primary gradients, logo primary fills/strokes, and primary buttons must share that destination primary color.
- Do not hardcode Preline blue or emit `text-blue-*`, `bg-blue-*`, `border-blue-*`, `fill-blue-*`, `stroke-blue-*`, `from-blue-*`, `via-blue-*`, `to-blue-*`, or fixed blue hex/rgb values for primary roles unless the destination primary is explicitly blue.
- Before using source-only token classes such as `text-foreground-inverse`, `bg-layer`, `border-layer-line`, `bg-navbar`, `border-line-2`, `bg-dropdown`, or similar Preline tokens, inspect the destination Tailwind config, global CSS/theme variables, and existing components for an equivalent utility/token.
- Prefer existing destination utilities such as `text-white`, `text-primary-foreground`, `text-foreground`, `text-muted-foreground`, `bg-background`, `bg-card`, `bg-popover`, `border-border`, `bg-muted`, `bg-accent`, `ring-ring`, or app-specific tokens when they match the source role.
- If no equivalent exists, add the smallest project-appropriate token or utility before using it. Do not leave undefined source classes in the generated markup.
Asset and icon rules:
- Use exact source images, avatars, product media, branded SVGs, payment marks, channel logos, and app icons when the source provides them.
- Do not replace source assets with initials, emojis, generic icons, generated placeholders, or different stock media.
- Ordinary interface icons should match the destination icon system. If the project uses Lucide-style outline icons, keep the 24 viewBox, `fill="none"`, `stroke="currentColor"`, rounded caps/joins, and source stroke widths.
- Brand/source SVG shape is fixed content. Only map semantic colors such as primary fill/stroke to the destination token.
Behavior and accessibility:
- Preserve source interactions: links, buttons, dropdowns, tooltips, tabs, menus, drawers, modals, toggles, search, filters, form controls, validation states, loading/empty states, and open/closed defaults.
- For source behavior powered by Preline JS or a third-party package, inspect installed dependencies and existing primitives first. Reuse a destination primitive only when it can preserve the source geometry, states, accessibility, and behavior.
- Treat new dependencies as allowed by default unless the user, repository instructions, or package policy explicitly prohibit them. When no faithful equivalent exists, install/use the Preline UI runtime/plugin or the exact source third-party package; do not silently substitute ad hoc JavaScript or custom React state.
- Only under an explicit dependency prohibition may you implement a scoped framework-native equivalent. It must preserve keyboard and focus management, placement and layering, responsive behavior, and accessibility; static or simplified approximations are not acceptable.
- Use semantic HTML and accessible names. Keep `aria-current`, `aria-expanded`, `aria-haspopup`, `role`, labels, focus states, and keyboard behavior when the source exposes them or the destination primitive requires them.
- Desktop and mobile states must not overlap text, clip controls, or shift layout unexpectedly. Controls with icons, counters, badges, and labels should keep stable dimensions across hover/focus/active states.
Final QA:
- Compare the result against the source preview and HTML tab.
- Verify primary color follows the destination project, not Preline's default blue.
- Verify all emitted classes exist in the destination or are added deliberately.
- Verify responsive layout, focus states, dropdown/popover layering, long-text truncation, and source asset paths.
- Keep the final implementation scoped to this block and avoid unrelated refactors.