Remix

Make your own version of UK By-Election Simulator

Get an exact, working copy in your account, then change anything with chat.

Original by He Wa

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

# UK BY-ELECTION SIMULATOR — COMPLETE BUILD PROMPT

Build a realistic, interactive UK Parliamentary By-Election Simulator set in modern-day Britain, starting in 2026. It should feel like a professional UK election control room, combining a constituency map, party management, campaigning, live vote counting and realistic election-night results.

## 1. MAIN MENU
Create a professional main menu with:
- Start New By-Election
- Continue Saved Election
- Constituency Explorer
- Party Manager
- Election Results Archive
- Settings

Use a modern British political aesthetic: dark navy, white backgrounds, restrained red and blue accents, clear typography, detailed maps and compact information panels. Avoid cartoon graphics, oversized buttons and mobile-game styling.

## 2. ELECTION SETUP
Allow the player to configure:
- Election name and date
- Any UK parliamentary constituency
- Reason for the by-election: resignation, death of an MP, recall petition or other vacancy
- Candidates standing
- Political parties and independent candidates
- Campaign duration
- Starting polling estimates
- Turnout assumptions
- Campaign budgets
- Whether the election is simulated automatically or controlled manually

Include England, Scotland, Wales and Northern Ireland. Clearly distinguish UK Parliament Westminster by-elections from devolved and local elections.

Provide a working constituency selector and map. Use real constituency names and political data where available. Never invent supposedly official historical results or claim a complete real-world dataset exists if it has not been implemented. Allow custom constituencies and editable data.

## 3. MAP AND CONTROL ROOM
The main interface should resemble a professional election operations dashboard.

Include:
- A large constituency map
- Constituency name and region
- Previous general-election winner
- Incumbent MP and party
- Previous winning majority
- Previous turnout
- Candidate list
- Latest polling
- Campaign progress
- Election countdown
- Current simulation date and time

Add navigation tabs for Overview, Constituency, Candidates, Campaign, Polling, Count, Results and History.

Clicking a constituency, candidate or party should open its detailed information panel. All navigation and controls must work.

## 4. POLITICAL PARTIES
Include the major UK parties: Labour, Conservative, Liberal Democrats, Reform UK, Green Party, Scottish National Party, Plaid Cymru, Democratic Unionist Party, Sinn Féin, Social Democratic and Labour Party, Alliance Party and other relevant parties.

Allow players to:
- Create custom parties
- Edit party names, colours and logos
- Select candidates
- Set campaign strategies
- Allocate budgets
- Choose campaign priorities
- Withdraw candidates
- Support tactical voting arrangements

Use real parties and actual historical results when verified data is available. Party support should vary by constituency, and not every party should contest every election.

## 5. CANDIDATES
Every candidate should have:
- Name
- Party
- Previous political experience
- Local recognition
- Campaign effectiveness
- Public approval
- Constituency connection
- Campaign spending
- Current polling estimate

Allow custom candidates and independents. Candidate attributes must influence the simulation without guaranteeing victory.

## 6. CAMPAIGN SIMULATION
Let the player advance time manually through campaign days.

Available campaign actions:
- Canvassing
- Leaflet distribution
- Door-knocking
- Public meetings
- Local media interviews
- Social media campaigns
- Leader visits
- Community events
- Local issue campaigning
- Targeted advertising

Each action should cost money and influence voter support, turnout or candidate recognition. Effects should depend on constituency demographics, party strength, campaign effectiveness and local issues.

Create local issues such as the NHS, cost of living, immigration, housing, transport, jobs and public services. Constituencies should respond differently to different issues.

Add campaign events, unexpected controversies, endorsements and local news stories. Events must have meaningful consequences rather than being decorative text.

## 7. POLLING AND VOTER MODEL
Create a realistic constituency-level voting model.

Calculate support using:
- Previous election results
- National political climate
- Constituency-specific party support
- Candidate popularity
- Campaign effectiveness
- Local issues
- Tactical voting
- Turnout changes
- Campaign spending
- Random but controlled uncertainty

Show polling estimates, projected vote shares, estimated turnout and uncertainty ranges. Polling must not perfectly predict the final result.

The player should be able to compare current projections with the previous general election and see which parties are gaining or losing support.

## 8. ELECTION DAY
Create an election-day interface with:
- Polling station opening and closing
- Turnout updates
- Candidate and party information
- Election-day news
- Closing-time notification
- Transition to the count

Allow manual advancement through election day. Do not declare a winner before the count is completed.

## 9. LIVE COUNT
This is the core feature.

Create a realistic vote-counting room with:
- Ballot papers counted
- Valid and rejected ballots
- Turnout
- Verified ballot batches
- Candidate vote totals
- Party vote shares
- Projected winner
- Declared results
- Remaining ballots to count

Allow the player to reveal count batches individually. Each batch should add votes to candidates based on the underlying voter model. Show how the projected result changes as the count progresses.

Add a declaration button that becomes available only when the count is complete and verified.

Display realistic count updates such as:
“First batch of votes verified.”
“Candidate A moves into the lead.”
“Majority calculation updated.”
“Official result declared.”

The count must be internally consistent. Candidate votes must add up to the valid ballots counted, and rejected ballots must be accounted for separately.

## 10. RESULTS
When the count finishes, generate a professional results screen showing:
- Winning candidate
- Winning party
- Total votes for every candidate
- Vote share for every candidate
- Majority
- Turnout
- Valid and rejected ballots
- Previous result
- Vote-share changes
- Party gains and losses
- Swing between parties

Include a result comparison chart and a clear victory declaration.

Calculate the majority as the winner's votes minus the second-place candidate's votes. Calculate vote share using valid votes. Calculate swing using comparable previous results, accounting for changes in candidates and party representation where necessary.

Distinguish a change of party from a change in vote share. Do not label a party as having gained a seat if it already held the constituency.

## 11. NEWS AND ELECTION NIGHT
Generate contextual headlines during campaigning and counting.

Examples:
- “By-election campaign enters its final week.”
- “Latest projection suggests a close contest.”
- “Turnout figures released as polls close.”
- “First count update puts the challenger ahead.”
- “Constituency declares its new MP.”

Headlines must be generated from actual simulation events and results. Do not report contradictory or impossible developments.

## 12. SAVING AND HISTORY
Allow players to:
- Save an election
- Resume an unfinished election
- Review completed elections
- Compare previous by-elections
- Replay saved scenarios
- Export results as a simple report

Save all relevant settings, candidates, campaign decisions, polling, votes and count progress.

## 13. REALISM AND DATA
Use verified historical UK parliamentary election results and constituency boundaries wherever available. Make the election year and constituency boundary version explicit. Support custom data imports and editable scenarios.

If live data is unavailable, operate using the built-in dataset and clearly label simulated values. Do not fabricate current polling or official declarations.

The simulator must distinguish real historical information from generated gameplay events.

## 14. TECHNICAL REQUIREMENTS
Build this as a functional application, not a static mock-up.

Every button, tab, map interaction, selector, campaign action, save function and count control must work. All screens must share the same underlying election data.

Use persistent storage for saved elections. Validate all vote totals and calculations. Include useful empty states, error handling and confirmation messages.

Prioritise the core loop:
SET UP BY-ELECTION → SELECT CANDIDATES → CAMPAIGN → POLLING → ELECTION DAY → COUNT → DECLARE RESULT → REVIEW HISTORY.

Build the complete working core before adding decorative features. The finished product should be easy to understand, highly replayable and realistic enough for someone interested in UK politics to run their own Westminster by-election simulations.

Tryy to use a maximum of 10 credits

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.