Fastest Typist in Bedford

Act as a civic game designer, product strategist, and front-end builder tasked with creating a lightweight public typing challenge for a local civic campaign.

The tool to build is:
A Bedford-themed typing challenge that turns a simple typing test into a playful civic participation experience.

Objective:
Create a self-contained interactive page that feels like a local public-interest experiment, not a generic typing game. The experience should be visually aligned with the campaign site, simple to understand, easy to replay, and transparent enough that another town could adapt it without a budget.

Design and maintain these priorities throughout the build:

1. Civic Framing
The experience should begin by making clear that this is not just a typing test. It is a small experiment in making civic participation more approachable, lower pressure, and more shareable. The copy should explain that playful tools can still serve a civic purpose.

2. Familiar Game Logic
The core mechanic should feel immediately understandable. Show one Bedford-themed passage at a time. Start the timer on the first keystroke. Track elapsed time, words per minute, accuracy, and completion state. The interface should feel clean, calm, and confidence-building rather than intimidating.

3. Fair Scoring
Use standard typing-test logic. Words per minute should be based on total typed characters divided by five, adjusted for elapsed minutes. Accuracy should be based on correct characters divided by total typed characters. No character should appear incorrect before the player begins typing. Fresh starts, retries, and resets must always begin with neutral styling.

4. Submission Rules
Only allow score capture if the player completes the passage with at least 75 percent accuracy. If the score is below threshold, show a dismissible modal that clearly explains why the score was not captured. The modal must include both a visible close control and a clear Try Again action.

5. Lightweight Community Leaderboard
If scores are submitted, collect only minimal community-friendly fields such as display name, hamlet, WPM, accuracy, and timestamp. Avoid unnecessary personal data. The leaderboard should support both overall ranking and grouping by hamlet.

6. Transparent UX
The interface should visibly explain what is happening. Show the current text, the input state, live or final performance stats, retry behavior, and submission outcomes. If any modal appears, it should never trap the user. Every state should be recoverable.

7. Design System Discipline
Match the visual language of the Uncampaign site. Use the same restrained palette, spacing rhythm, typography, and card treatment. This should feel like a civic prototype built with care, not a startup game or flashy arcade module.

8. Accessibility and Resilience
The game must work with keyboard-first input, scale on mobile even if desktop is preferred, and fail gracefully if score submission or leaderboard retrieval is unavailable. Do not let a network failure break the local play experience.

Build instructions:
- Start with a clear hero and explanatory section.
- Include a back link to /best-of-bedford.
- Present the game in a single primary module.
- Use Bedford-specific prompt text or passages.
- Make the "best played on desktop" note visible but unobtrusive.
- Keep the score flow transparent and low pressure.
- Let the user retry instantly.
- Keep the leaderboard readable and community-oriented.
- Treat the entire experience as a civic participation artifact, not a gimmick.

Output format:
1. Civic framing
2. Core game architecture
3. Scoring and accuracy rules
4. Submission and leaderboard rules
5. Accessibility and failure-state handling
6. Visual design requirements
7. Final implementation checklist