Implementation Prompt: Barcbots.com Redesign

What the prompt had to do

The primary goal of the prompt was not just to describe the redesign. It had to operationalize it. That meant converting aesthetic direction into enforceable rules that an implementation agent could follow without guessing.

The prompt covered all six pages, the season detail template, reusable components, responsive expectations, motion, and dark mode so the build could move as one system instead of as a series of disconnected pages.

Design system instructions

• Define typography scale, weights, tracking, and hierarchy down to the label level.
• Establish a monochrome base with six semantic award accent colors and four event badge colors.
• Lock the spacing rhythm, content width, section cadence, and standard hero pattern.
• Require dark mode support and specify where color inversion should remain restrained.

Component contracts

• Pill filters for program-level switching without introducing complex filter UI.
• Team accordions that support progressive disclosure for large award datasets.
• Award rows with icon mapping, badge logic, and semantic categorization.
• Stats grids, highlight strips, CTA blocks, and value sections that keep the visual language consistent across pages.

Implementation constraints

The prompt did more than say what to build. It also established what should not change. Existing content needed to stay intact, the design needed to feel editorial rather than template-like, and motion had to stay controlled. Those constraints mattered because they preserved the point of view while still giving room for implementation judgment.

Why the prompt structure mattered

Prompt quality was the bridge between design direction and implementation fidelity. A vague prompt would have produced a technically correct rebuild that still felt ordinary. A structured prompt turned subjective design intent into a durable delivery artifact.