Build your own Stack Overflow.

# Build an original app inspired by Stack Overflow

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original question-and-answer community called Answerforge, inspired by Stack Overflow. Members ask well-scoped questions in one subject area, propose answers, vote, and mark an accepted solution. Focus on a durable knowledge base rather than a general discussion feed.

## Design
Use an original readable question page with title, tags, safe Markdown/code, separate answers, vote controls, and a visible accepted marker. Provide unanswered and active question lists, a guided question composer, and accessible alternatives to icon-only actions.

## Features
1. Questions and tags: create/edit questions with a clear title, body, and bounded tags. Search existing questions before submission and keep edit history so changes remain explainable.

2. Answers and acceptance: post/edit answers, let only the question author choose or replace an accepted answer, and prevent acceptance of an answer from a different question. Show the distinction between accepted and highest-voted answers.

3. Votes: allow one up/down/none state per user per post, prevent self-voting, and calculate counters consistently. If reputation is included, derive it from an explicit event ledger and make reversal rules testable.

4. Knowledge navigation: combine tag and answered/unanswered filters, sort with stable pagination, and let moderators close or reopen questions and link an identified duplicate without deleting its history.

5. Moderation: flag posts, remove unsafe content, maintain comment threads for clarification, and document the pilot’s small member/moderator role model. Render all Markdown and code safely.

## Tech stack
Use Python/Django, PostgreSQL, and a TypeScript or server-rendered frontend. Use database constraints for votes and acceptance transactions, safe Markdown rendering, and indexed full-text search within the community. Seed original example questions rather than scraping Stack Overflow.

## Data & behavior
User; Question {authorId, title, body, acceptedAnswerId, state}; Answer {questionId, authorId, body}; Tag; QuestionTag; Vote {userId, targetType, targetId, value}; Revision; Comment; DuplicateLink; Flag; ModerationEvent; optional ReputationEvent.

Acceptance checks and scope:
Test vote reversal and retry, accepted-answer replacement, a cross-question acceptance attempt, moderator closure, duplicate cycles, hostile Markdown, and correct filtered pagination after edits. Exclude copying Stack Overflow content, broad reputation/privilege equivalence, AI-generated answer posting, and enterprise organization features.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.