What this prompt does
This prompt generates a complete pharmacy e-commerce interface specification across seven interconnected components — medication search, prescription upload, product page, auto-refill, cart and checkout, order tracking, and working framework code for the search and interaction warning system. The embedded industry ruleset is what separates it from a generic e-commerce prompt: it enforces clinical trust signals at generation time (extra-large dosage typography, amber modal interaction warnings, pharmacist review status indicators) while explicitly blocking anti-patterns like obscuring contraindications or letting a prescription-required item reach checkout without verification.
The [framework] variable drives the code output. Specify React, Vue, or Alpine and the prompt produces a working medication search component with auto-complete and drug interaction warning logic — not a wireframe description. The [pharmacy_type] and [regulatory] variables together determine compliance posture: a compounding pharmacy under strict DEA and state board rules produces a materially different flow than an OTC wellness retailer where no prescription verification step exists.
The color and typography directives are functional, not aesthetic. Medication UIs have a documented error surface around ambiguous dosage numbers and warnings that blend into backgrounds. Specifying extra-large text for medication names and dosages, and amber modals for interaction alerts, reduces that risk during the design-generation stage before a developer writes a line of CSS.
When to use it
- Building an online pharmacy MVP and need a full component map — search through tracking — before committing to an architecture.
- Adding a prescription fulfillment or dispensing flow to a telehealth platform that previously handled only consultations.
- Designing a pharmacist-facing review dashboard where OCR feedback and prescription approval status need to surface unambiguously.
- Starting a pharmacy client engagement and need a structured, compliance-aware discovery artifact to present before the statement of work.
- Adding a white-label pharmacy module to an existing healthcare SaaS product where the regulatory variables will differ per client.
- Prototyping a veterinary pharmacy storefront — the
[pharmacy_type]and[regulatory]variables accommodate non-human medication contexts cleanly.
Example output
For [pharmacy_type]: independent retail pharmacy, [products]: generic and brand-name prescription drugs, OTC, vitamins, [regulatory]: FDA, state pharmacy board, [framework]: React:
The medication search component generates as a debounced input tied to a medication lookup API, with an autocomplete dropdown that distinguishes brand names from generic names visually (typically bold vs. regular weight), shows dosage strength variants, and displays price. On drug selection, it triggers an interaction check against whatever API you wire it to — if the check returns a flag, an amber modal renders with collapsible detail and a severity indicator. Items marked prescription-required lock the add-to-cart action and redirect to the prescription upload flow.
The prescription upload component generates an upload zone with OCR processing status and a pharmacist review status indicator — the exact states and labels will reflect whatever you specify in [regulatory]; a DEA Schedule II context produces a more explicit verification chain than a state-board-only context.
The auto-refill component generates a medication schedule view with reminder settings and delivery preferences, but the countdown logic depends on how you specify supply units — see Pro tips.
Pro tips
- Set
[regulatory]as specifically as possible. "DEA Schedule II, HIPAA, California Board of Pharmacy" produces stricter checkout verification and prescription handling flows than a vague "standard pharma regulations" — the prompt uses this variable to calibrate every compliance-gated step. - For the interaction checker, the prompt generates the UI pattern and the API call structure — it does not embed a drug database. In a follow-up prompt or in your
[products]description, specify which interaction API you will wire to (RxNorm, DrugBank, your pharmacy system's endpoint) so the generated code targets a real interface rather than a placeholder stub. - The auto-refill countdown timer produces different logic depending on whether your system tracks supply in days-supply or quantity units. Specify this explicitly in your prompt or the generated reminder logic will be ambiguous about what triggers a refill alert.
- If your pharmacy serves patients in multiple languages, add bilingual labeling requirements to the prompt directly — don't rely on
[regulatory]for this, since that variable governs compliance jurisdiction, not localization. Explicit language requirements in the prompt body will carry through to the dosage typography and warning label patterns. - After generating the interface, run the interaction modals and prescription upload flow through a separate accessibility audit prompt. Medication UIs are subject to WCAG 2.1 AA requirements, and the interaction warning modals need keyboard-navigable dismiss patterns — this prompt establishes the visual design but does not auto-enforce focus management or screen-reader labeling.
