Build your own Facebook.

# Build an original app inspired by Facebook

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 network called Commonplace, inspired by Facebook. It serves a small invited community sharing updates and organizing interest groups. The primary journey is creating a profile, connecting with another member, publishing an update, and responding through the permitted feed. Implement a bounded social graph and genuine privacy rules rather than a decorative newsfeed.

## Design
Use an original responsive three-area layout with community navigation, a readable chronological feed, and upcoming group activity. On phones prioritize feed and composer. Provide clear audiences on posts, recognizable pending friend requests, accessible reaction controls, and explicit empty, removed-content, and blocked-member states.

## Features
1. Profiles and connections: authenticate members, edit an original profile and avatar, search permitted profiles, send/accept/decline friend requests, and remove a connection. Enforce one relationship record per pair and prevent self-invitations.

2. Posts and feed: create text or bounded image posts, choose community or friends-only visibility, edit/delete your own content, and paginate a newest-first feed. Visibility must apply to direct URLs, media downloads, and search as well as feed cards.

3. Interaction: comment and reply at one level, toggle a reaction idempotently, and show real persisted counts. Maintain stable pagination when new posts arrive and an understandable tombstone for deleted parent content.

4. Groups: create a group with a description and rules, request or approve membership, publish group posts, and assign a moderator. Private group membership and content must not leak through global search.

5. Moderation: block members, report posts/comments, review reports, remove content, and log moderator actions. Notify users about accepted requests and replies using in-app notifications derived from real events.

## Tech stack
Use a TypeScript frontend and backend with PostgreSQL, authenticated sessions, and scoped object storage. Use safe Markdown or plain text, cursor pagination, and transaction/unique-constraint protection for relationships and reactions. Check authorization on every API and media operation. Keep one community and chronological ordering; a public deployment also needs maintained abuse handling.

## Data & behavior
User; Profile; Connection {lowUserId, highUserId, requesterId, status}; Post {authorId, audience, groupId, body, mediaKey, state}; Comment; Reaction; Group; GroupMembership {role, status}; Block; Report; ModerationAction; Notification. Define explicit audience rules and index feed queries. Store original uploads, not copied reference content.

Acceptance checks and scope:
Test friend acceptance from two sessions, duplicate requests, friends-only posts fetched by a stranger, private group search, blocked-member interactions, pagination after a new post, and removed content. Exclude Messenger calls, marketplace payments, ad targeting, commercial recommendations, and mass scraping.

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