Build your own Reddit.

# Build an original app inspired by Reddit

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 community discussion app called Threadgarden, inspired by Reddit. It is for a few topic communities sharing original posts and conversations. The main flow is joining a community, publishing a text or link post, voting, and replying in a threaded discussion. Focus on understandable ordering and actual moderation, not a global social network.

## Design
Use an original readable feed with community navigation, clear post types, vote controls, and an expandable comment tree. Show moderation and removed-content states without hiding context. Use comfortable typography, compact metadata, responsive layouts, and keyboard-friendly voting and thread navigation.

## Features
1. Accounts and communities: authenticate users, create communities with descriptions and rules, join/leave communities, and assign owner/moderator/member roles with server-side checks.

2. Posts: publish original text or validated links, edit/delete your own posts, search permitted content, and sort by newest or an explicit score/time formula. Do not fetch arbitrary link previews from private network addresses.

3. Voting: allow one up/down/no vote per user and post, toggle votes idempotently, and derive scores from persisted votes. Avoid client-side counters that drift under retries.

4. Comments: support nested replies with a bounded depth, collapsed branches, edit/delete rules, and pagination. Preserve tombstones when removing a parent with replies.

5. Moderation: report content, review reports, remove posts/comments, lock threads, and ban members from a community. Keep moderator actions auditable and apply permissions to search and feeds.

## Tech stack
Use a Go API with PostgreSQL and a TypeScript browser frontend for a new project. Use transactions and unique constraints for voting, server-side roles for moderation, and safe Markdown rendering. Keep feed ordering deterministic and paginated. Preserve the current stack if one exists. A public service needs operational moderation and abuse controls; the first version should be a small controlled community.

## Data & behavior
User; Community {ownerId, rules}; Membership {role, status}; Post {authorId, communityId, kind, title, body, link, state}; Vote {userId, postId, value}; Comment {postId, authorId, parentId, depth, body, deletedAt}; Report; ModerationAction. Use unique vote constraints and indexes for feed/search access. Never rely on a hidden UI button for authorization.

Acceptance checks and scope:
Test vote toggling/retries and concurrent updates, a deleted parent with replies, a locked thread, a banned member posting via API, moderator ownership, and pagination stability. Restrict unsafe links and markup. Exclude scraped Reddit data, recommendations, paid memberships, arbitrary media uploads, and global-scale ranking.

## 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.