beauty-cosmetics is a complete, production-ready, mobile-first beauty and cosmetics e-commerce platform. It is an original premium beauty shopping brand — not a clone of any existing store — whose visual layout is inspired by two uploaded reference screenshots used strictly as visual and structural inspiration. The brand's design language is built on pink, white, lavender, and teal, and it must feel premium, playful, and confident rather than austere.
The platform serves the full commerce lifecycle end-to-end: a customer storefront with search, a product catalog, product details, offers, a wishlist, a cart, secure checkout with real payment gateway integration, order tracking, notifications, and customer support; plus an administrative and merchant back office covering an admin dashboard, catalog management, inventory management, seller management, offer management, support management, and seller-owned listings and inventory. All backend APIs and database functionality are in scope.
Audience. The primary audience is a mobile-first, mostly 20–35 shopper who browses beauty products by mood and identity, alongside the operational staff (store administrators, sellers, and support agents) who keep the storefront accurate and resolve customer issues.
Non-negotiable product intent. Every button, menu, form, and shopping feature must work end-to-end. There is no mock functionality. Payments must never be reported as successful without verified payment gateway confirmation. There are no unfinished pages, broken links, placeholder buttons, or fake checkout flows. The deliverable is a working, tested, deployable full-stack application with setup and deployment steps explained.
beauty-cosmetics is delivered as a first-party full-stack web application with a mobile-first responsive storefront and a role-protected back office, backed by first-party APIs and a persistent database.
Actors. The accepted active human personas are the Shopper, the Registered Customer, the Store Administrator, the Seller, and the Support Agent. The payment gateway is a typed non-persona external actor: it is a provider-owned service that authorizes and confirms payments, and its confirmation is the sole authority for reporting payment success.
Accepted behavior. Shoppers browse the catalog, search, view product details, view offers, and add items to a cart. Registered customers additionally keep a persistent wishlist, order history, order tracking, notifications, and support requests across sessions. Store administrators manage the catalog, inventory, sellers, offers, and support requests through role-based access. Sellers maintain their own product listings and stock. Support agents handle customer support requests and communicate resolutions back to customers.
Ownership. All customer-facing and back-office surfaces are first-party application pages. Payment authorization and confirmation are owned by the external payment gateway; the application only reflects gateway-confirmed outcomes. Identity is application-owned: shoppers self-enroll, returning users verify, and administrators provision staff roles.
Narrow exclusions. The platform does not implement mock or simulated payment success, does not ship placeholder or unfinished UI, and does not copy the uploaded reference screenshots — they inform layout only. No adjacent capabilities beyond the accepted scope (for example, loyalty programs, subscriptions, or marketplace-wide analytics suites) are introduced.
beauty-cosmetics is a first-party, application-owned commerce platform. The storefront is publicly reachable for browsing, search, catalog, product details, and offers, so a visitor can evaluate products before committing to an account. Persistent, customer-specific state — wishlist, cart continuity, checkout, orders, notifications, and support — is bound to an application-owned identity so that a commitment, entitlement, or order remains attached to the correct person across sessions.
Identity is established in two ways. Shoppers self-enroll through Sign Up and verify on return through Login. Staff roles — Store Administrator, Seller, and Support Agent — are provisioned by an administrator rather than self-selected, and they verify through the same Login surface. Access to protected destinations is role-restricted: a customer's own orders, wishlist, cart, notifications, and support are visible only to that customer, and back-office workspaces are visible only to the roles that own them.
Payment is delivered through a real external payment gateway. The application never asserts payment success on its own; it reports success only after the gateway confirms it, and it presents a retry path when confirmation does not arrive. Everything described in this document is current scope. No future-horizon features are asserted.
Not applicable. No reference directive declares a content_source; the uploaded screenshots are declared inspiration_only for visual layout and structure, and therefore supply no product names, copy, facts, or capabilities.
FR-1 — Storefront browsing. As a Shopper, I should browse the beauty and cosmetics product catalog so that I can discover products to buy. (explicit)
FR-2 — Product search. As a Shopper, I should search the catalog by query so that I can find a specific product quickly. (explicit)
FR-3 — Product detail review. As a Shopper, I should review a single product's details so that I can decide whether to buy it. (explicit)
FR-4 — Add to cart. As a Shopper, I should add an in-stock product to my cart so that I can purchase it. (explicit)
FR-5 — Cart management. As a Registered Customer, I should manage my cart lines and quantities so that my order reflects what I intend to buy. (explicit)
FR-6 — Customer account enrollment. As a Shopper, I should create an account so that my cart, wishlist, orders, and notifications persist across sessions. (required_inference)
FR-7 — Returning verification. As a Registered Customer, Store Administrator, Seller, or Support Agent, I should verify my identity on return so that I can reach the destinations my role owns. (required_inference)
FR-8 — Staff role provisioning. As a Store Administrator, I should provision Store Administrator, Seller, and Support Agent roles so that staff can perform their accepted work under role-based access. (required_inference)
FR-9 — Wishlist management. As a Registered Customer, I should save products to a wishlist so that I can return to them later. (explicit)
FR-10 — Offers viewing and application. As a Shopper or Registered Customer, I should view available offers and apply an eligible one so that I receive the stated discount. (explicit)
FR-11 — Secure checkout with verified payment. As a Registered Customer, I should complete checkout with a real payment gateway so that my order is placed only when payment is genuinely confirmed. (explicit)
FR-12 — Order history and tracking. As a Registered Customer, I should view my orders and track their status so that I know where my purchase stands. (explicit)
FR-13 — Notifications. As a Registered Customer, I should receive and read notifications about my orders, offers, and support requests so that I stay informed. (explicit)
FR-14 — Customer support requests. As a Registered Customer, I should submit and follow support requests so that my issues are resolved. (explicit)
FR-15 — Support handling. As a Support Agent, I should handle customer support requests so that customer issues are resolved and communicated back. (explicit)
FR-16 — Admin dashboard. As a Store Administrator, I should use an admin dashboard so that I can see platform state and reach each management workspace. (explicit)
FR-17 — Catalog management. As a Store Administrator, I should maintain product catalog records so that the storefront stays accurate. (explicit)
FR-18 — Inventory management. As a Store Administrator, I should manage platform inventory levels so that storefront availability is truthful. (explicit)
FR-19 — Seller management. As a Store Administrator, I should manage seller records so that merchant participants and their listings are correctly represented. (explicit)
FR-20 — Offer management. As a Store Administrator, I should maintain customer offers so that promotions shown to customers are correct. (explicit)
FR-21 — Seller listing maintenance. As a Seller, I should maintain my own product listings so that my products are correctly represented and sellable. (explicit)
FR-22 — Seller stock maintenance. As a Seller, I should maintain stock for my own products so that availability is accurate. (explicit)
FR-23 — Backend APIs and database persistence. As the platform, I should provide backend APIs and database functionality for all durable workflows so that every accepted capability persists and enforces its rules. (explicit)
FR-24 — End-to-end functional completeness. As the platform, every button, menu, form, and shopping feature should work end-to-end with no mock functionality, no unfinished pages, no broken links, no placeholder buttons, and no fake checkout flows. (explicit)
The Shopper is the primary customer and the reason the storefront exists. They arrive mobile-first, often on a 375px phone, and browse by mood and identity rather than by specification. Their product context is discovery: they want to see what the brand offers, compare products, and decide whether something is worth buying.
Primary goal: find beauty and cosmetics products they want and get them into a cart ready to purchase.
Distinct accepted responsibilities: browsing the Product Catalog, searching on Search, reviewing Product Details, viewing Offers, and adding in-stock products to the Cart. The Shopper's work is exploratory and non-committal — nothing they do requires an account until they want their cart, wishlist, or orders to persist.
Relevant inputs or decisions: which category or query to explore, which product to open, whether a product is in stock, and whether to add it to the cart.
Interactions with other accepted participants: the Shopper's browsing depends on the Store Administrator's catalog and inventory accuracy and on the Seller's listing and stock accuracy; inaccurate data directly degrades the Shopper's experience. The Shopper becomes a Registered Customer when they enroll.
Observable success: products render with accurate prices and availability, search returns relevant results, and an in-stock product can be added to the cart with the cart count reflecting it.
The Registered Customer is a Shopper who has enrolled so that their shopping state persists. Their product context is continuity: they expect their cart, wishlist, orders, notifications, and support history to be there when they return, on any session.
Primary goal: complete purchases and keep track of everything they have bought, saved, and asked about.
Distinct accepted responsibilities: managing the Cart, saving to the Wishlist, completing secure Checkout with verified payment, viewing and tracking Orders, reading Notifications, and submitting and following Support requests. This is materially different from the Shopper's work: the Registered Customer owns durable, private state and makes a payment commitment.
Relevant inputs or decisions: order details at checkout, whether to apply an offer, whether to retry a failed payment, and whether to raise a support request about an order.
Interactions with other accepted participants: the Registered Customer's payment is confirmed by the external payment gateway; their support requests are handled by the Support Agent; their orders depend on the Store Administrator's and Seller's catalog, inventory, and listing accuracy.
Observable success: an order is reported as placed only after verified gateway confirmation, the order appears in Orders with accurate status, notifications link to the related records, and support requests receive a visible response.
The Store Administrator is the operator who keeps the storefront truthful. Their product context is the back office: they work across the whole platform rather than within a single customer's state.
Primary goal: keep catalog, inventory, sellers, offers, and support accurate and handled so that customers can shop without friction.
Distinct accepted responsibilities: using the Admin Dashboard, maintaining product records in Catalog Management, adjusting stock in Inventory Management, managing seller records in Seller Management, maintaining offers in Offer Management, handling support requests in Support Management, and provisioning staff roles. This is materially different from every other persona: the Store Administrator is the only role with platform-wide authority and the only one who provisions other roles.
Relevant inputs or decisions: product and category data, stock levels, seller associations, offer terms and eligibility, support request status, and staff role assignment.
Interactions with other accepted participants: the Store Administrator's catalog and inventory decisions directly determine what Shoppers and Registered Customers can buy; seller records determine what Sellers can maintain; offer records determine what customers see on Offers; support handling overlaps with the Support Agent.
Observable success: storefront data stays accurate, active offers appear to customers, and support requests move to resolution.
The Seller is a merchant participant managed through seller management who supplies and maintains their own products within the platform. Their product context is narrow and owned: they see and change only their own listings and stock.
Primary goal: have their products correctly represented and sellable in the storefront.
Distinct accepted responsibilities: maintaining owned product listings in Seller Listings and maintaining stock for owned products in Seller Inventory. This is materially different from the Store Administrator's work: the Seller's authority is scoped to their own products and does not extend to platform-wide catalog, inventory, offers, or support.
Relevant inputs or decisions: listing content, category, price, and stock levels for their own products.
Interactions with other accepted participants: the Seller's listings and stock are what Shoppers and Registered Customers browse and buy; the Store Administrator manages the seller record that establishes the Seller's participation.
Observable success: their listings appear in the storefront under their ownership and their stock levels are reflected in availability.
The Support Agent is a staff member who handles customer support requests and notifications raised by shoppers. Their product context is the support queue and the conversations within it.
Primary goal: resolve customer issues and communicate the resolution back to the customer.
Distinct accepted responsibilities: reviewing incoming support requests, responding to them, and updating their status in Support Management. This is materially different from the Store Administrator's work: the Support Agent's focus is the customer conversation and its resolution rather than platform configuration.
Relevant inputs or decisions: the customer's request content, the related order reference, and the appropriate response and status.
Interactions with other accepted participants: the Support Agent responds to Registered Customers' requests, and those responses become visible to the customer on Support and in Notifications.
Observable success: customer issues are resolved and the resolution is communicated back to the customer.
Muse and headline. Saturated beauty maximalism after Jessica Walsh — colour as material, wit as luxury. The storefront is a hot-pink ground with a teal counter-accent, lavender as soft support, and products staged like art objects with a wink. Premium but never austere: colour is the product.
Colour tokens (light mode).
| Role | Hex | Usage |
|---|---|---|
| Background (blush-white ground) | #FFF6F8 | ~55% of every screen |
| Surface | #FFFFFF | ~25% — cards, sheets, checkout panels |
| Text (ink) | #1A0E1C | All body and heading text; never pure black |
| Primary (hot raspberry-pink) | #E5387A | CTAs, price tags, active states, wordmark — never diluted |
| Accent (teal) | #00B3A4 | Hard colour blocks: offer bands, "in stock" pills, category chips, second half of the hero |
| Muted (lavender) | #B98BD6 | Section grounds, badges, wishlist hearts on hover, illustration fills |
Contrast rules. Ink on blush-white = 15.8:1. White on pink = 4.6:1 — use only for 18px+ or bold text. Ink on teal = 7.4:1. Ink on lavender = 7.9:1. Never put white body text on lavender or teal.
Typography.
-0.02em; uppercase for section labels and category names, sentence case for editorial headlines.clamp(44px, 11vw, 128px) with 0.92 line-height; section headlines clamp(30px, 6vw, 64px); product title 18px → 24px; price 20px → 28px; body 16px with 1.6 line-height; micro-labels 12px uppercase tracked +0.14em.Shape language. Big radii — 24px cards, 32px hero blocks, 999px pills for all filters and CTAs. Sticker-like overlapping shapes with 2px ink outlines. Colour blocks that collide rather than nest. Diagonal 8° colour bands as section dividers. Capsule "swatch" chips. Shadows are hard and offset (6px 6px 0 ink) rather than soft — a printed-sticker feel. Nothing is transparent; every surface is a flat colour.
Layout. Mobile-first single column at 375px: sticky top bar with wordmark, search pill, and cart count; full-bleed hero colour block; horizontally scrollable category rail (touch-scroll, snap, with a visible "swipe" affordance); 2-up product grid at 375px, 3-up at 768px, 4-up at 1280px, with a max content width of 1280px and 24px gutters. Sections are separated by diagonal colour bands, not whitespace. Every text block sits inside a container with a hard edge — no text ever bleeds off-screen; only decorative shapes, bands, and the marquee cross edges. Product cards are never identical hover-lift tiles: they alternate between white and lavender grounds with a rotated sticker badge.
Imagery. Art-directed product photography and 3D props on flat saturated colour grounds: a lipstick standing on a teal block, a serum bottle half-submerged in pink liquid, a blush compact with a lavender shadow. Props are surreal but clean — floating pearls, ribbon curls, glossy 3D capsules. No stock-model lifestyle shots, no white-background packshots, no gradient blobs. Illustrations are chunky flat vector doodles (sparkles, hearts, stars) used as stickers, never as hero art.
Readable-content rule. Headlines, wordmarks, labels, numbers, item images, cards, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit, and no other element covers any part of them. Crops, bleeds, and off-edge placement are for decoration only. Moving and scrollable content (marquees, tickers, carousels, horizontally scrollable rows) may cross the viewport edge by design, judged by whether it actually moves and whether every item becomes fully readable as it passes; under prefers-reduced-motion it stops and shows whole items, wrapping into rows or sitting in a horizontally scrollable row (overflow-x: auto).
Forbidden. Blue or indigo primary/accent anywhere (#0057FF, #2563EB, #6366F1, #7C3AED); Inter, Roboto, Arial, Helvetica, Poppins, Open Sans, Lato, or system-ui for headings or body; gradient-blob heroes, frosted glass panels, or soft blurred drop shadows; a grid of identical hover-lift cards with uniform white surfaces; centred headline + subtext + single button hero composition; white-background packshot photography or stock-model lifestyle imagery; text, prices, buttons, or product images cropped or overlapped at 375px, 768px, or 1280px; decorative motion that does not carry meaning, or any animation that ignores prefers-reduced-motion.
"The Beauty Counter" — a hero as two colliding colour blocks.
The public entry (Landing) opens on a full-bleed split colour block, not a centred SaaS hero. The left 60% is hot pink #E5387A; the right 40% is teal #00B3A4; a hard diagonal cut separates them. On mobile the blocks stack, pink first.
The hero headline is set in Archivo Black at clamp(44px, 11vw, 128px), flush-left, breaking across three lines, spanning the full pink field edge to edge, with the word "glow" in italic Fraunces — one accent word only. A single art-directed product still (a lipstick on a pink pedestal with a real cast shadow) sits in the teal half, cropped by the diagonal. The primary CTA is an ink-black pill with white text cut into the pink block; a secondary teal-outlined pill sits beside it. No centred stack, no sub-headline paragraph, no blue button, no gradient.
Below the hero, the signature moves carry the page: the sticker-swatch product cards (flat colour tiles alternating white and lavender, 2px ink border, hard 6px offset shadow, rotated category badge, and an on-card "Add to bag" pill that flips from pink to teal on tap), the 28s offers marquee running edge-to-edge in ink on teal with uppercase 14px tracked labels and · separators, and the category rail as a horizontally scrollable row of capsule chips with real product thumbnails inside, snapping to centre, active chip filled teal and the rest outlined ink on blush.
The concept recomposes only accepted content and controls — brand, featured products, categories, offers, search, cart count, and account entry. It introduces no new behaviour, page, or destination.
Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d
Landing Hero Motion Brief.
cubic-bezier(0.22, 1, 0.36, 1) entrances; staggered 60ms word reveals on the hero headline; springy scale(1.04) on tap targets; colour-flip on hover for category chips (pink → teal); a slow 28s marquee for the offers ticker; a scale keyframe pop on the cart count when it increments.prefers-reduced-motion; the marquee becomes wrapped rows of whole items; the headline appears fully composed with no stagger; the cart count changes without a pop.NFR-1 — Mobile-first responsive design. The platform is designed mobile-first and remains fully usable at 375px, 768px, and 1280px, with the layout rules in Section 6. (explicit)
NFR-2 — Accessibility. The platform implements accessibility: semantic structure, keyboard operability, visible focus, labelled controls, and sufficient contrast per the token rules in Section 6. (explicit)
NFR-3 — Secure authentication. Authentication is secure: credentials are verified server-side, sessions are protected, and protected destinations are unreachable without verified identity. (explicit)
NFR-4 — Role-based access. Access is enforced by role for every protected destination and operation: customers reach only their own state; Store Administrators, Sellers, and Support Agents reach only the workspaces their role owns. (explicit)
NFR-5 — Input validation. All user input is validated, with field-level feedback on forms and server-side enforcement on every API. (explicit)
NFR-6 — Error handling. Failures are surfaced honestly with an actionable recovery path; no failure is masked as success. (explicit)
NFR-7 — Loading states. Every asynchronous surface presents a loading state and prevents duplicate submission while pending. (explicit)
NFR-8 — Empty states. Every collection surface presents a meaningful empty state with a next step. (explicit)
NFR-9 — No mock functionality. No capability is simulated; every feature operates against real data and real services. (explicit)
NFR-10 — Verified payment only. Payment success is reported only after verified payment gateway confirmation; the application never asserts success on its own. (explicit)
NFR-11 — No unfinished or placeholder UI. There are no unfinished pages, broken links, placeholder buttons, or fake checkout flows. (explicit)
NFR-12 — Testing. The application is tested, covering the accepted customer and back-office workflows. (explicit)
NFR-13 — Deployment documentation and environment configuration. Setup and deployment steps are documented, and environment configuration is provided for all required services including the payment gateway. (explicit)
NFR-14 — Deployable full-stack deliverable. The result is a working, tested, deployable full-stack application. (explicit)
Constraints (binding).
Assumptions (narrow, labeled).
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!