Build your own Discord.

# Build an original app inspired by Discord

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 text chat app called Commonroom, inspired by Discord. It is for small interest groups organizing conversations in servers and channels. The main flow is joining a server, finding a text channel, sending messages, and participating under clear community permissions.

## Design
Use an original dark interface with a compact server rail, channel sidebar, message stream, and collapsible member panel. Differentiate roles and unread channels accessibly. The mobile layout should reveal one primary panel at a time. Use an original indigo accent and assets.

## Features
1. Servers: create and rename servers; invite members through expiring or revocable invite tokens; join and leave servers.

2. Text channels: create channel categories and text channels, edit topics, and control visibility by role. Reorder channels within categories.

3. Messages: send, edit, and delete your own text messages; reply to messages; add/remove emoji reactions; paginate history and deliver updates through a real-time connection or reliable polling.

4. Roles and moderation: define a small role model for owner, moderator, and member; moderators can remove messages and members; keep an audit log and prevent removing the sole owner.

5. Navigation: show actual unread counts, search permitted channel messages, and list server members. Indicate connection failures and retry unsent messages.

## Tech stack
Use the existing repository and conventions if there is one. If starting from scratch, use React with TypeScript and a practical, lightweight styling approach. Pick well-maintained libraries only when they materially help. Keep components, domain logic, and data access separate. Explain your chosen stack briefly, then begin implementation.

Follow the persistence requirements in Data & behavior. Personal tools may use IndexedDB. Products with public submission, bookings, permissions, or shared messaging require an authenticated backend with server-side authorization and durable storage. Use infrastructure already available in the environment. Do not put secrets in frontend code. If external infrastructure is unavailable, build a clearly labeled local demo, provide the schema and setup instructions, and state which shared features need configuration. Do not present simulated sharing or authentication as production functionality.

## Data & behavior
User; Server {id, name, ownerId}; Membership {serverId, userId, role}; Invite {serverId, tokenHash, expiresAt, revokedAt}; Category; Channel {id, serverId, categoryId, name, allowedRoles}; Message {id, channelId, authorId, replyToId, text, editedAt, createdAt}; Reaction; ReadPosition; AuditEvent. Use authenticated server storage and enforce server membership and channel permissions for HTTP and real-time operations.

Acceptance checks and scope:
Test two-user messaging, unread updates, reconnect without duplication, revoked invites, denied private-channel access, moderator permissions, and owner protection. Rate-limit messages and validate inputs. Exclude voice/video, bots, streaming, payments, and large file uploads from this first version.

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