Build your own Pinterest.

# Build an original app inspired by Pinterest

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 visual bookmarking app called Pinfolio, inspired by Pinterest. People create image-and-link pins from permitted material, organize them on boards, search their collection, and optionally share selected boards. Start with owned uploads and explicit destination links rather than scraping images from arbitrary websites.

## Design
Use an original responsive masonry-style gallery with stable image dimensions, useful text descriptions, board covers, and a pin detail view. Provide accessible list navigation alongside the visual layout. Make public/private state visible on every board and sharing control.

## Features
1. Pins: create a pin with a permitted image, title, description, alt text, and optional validated HTTPS destination. Validate uploads, store image dimensions, and safely render captions.

2. Boards and sections: create/rename boards, move or save pins into sections, reorder intentionally, and prevent duplicate saves. Deleting a board must not silently delete a source pin owned elsewhere.

3. Discovery and search: search visible pin titles/descriptions/tags, filter by board, and show a chronological public discovery feed. Keep private pins and their thumbnails out of public search and APIs.

4. Sharing: support public/private boards and revocable invitations for a small collaborator role. Enforce board membership on pin downloads and previews, not just on the gallery screen.

5. Collections and portability: follow public boards, retain saved references when a source pin is removed using a clear tombstone, and export owned board metadata and permitted image files.

## Tech stack
Use TypeScript, PostgreSQL for board permissions and saves, and object storage with private-image delivery. Generate thumbnails in a bounded image worker. Avoid server-side URL previews in the first version so arbitrary remote fetching is unnecessary.

## Data & behavior
User; Pin {ownerId, imageKey, title, description, destination, removedAt}; Board {ownerId, visibility}; Section; BoardPin {pinId, position}; BoardMember; Invitation {tokenHash}; Follow; Tag; PinTag. Derive accessible search results from board/pin visibility.

Acceptance checks and scope:
Test saving a pin to two boards, duplicate saves, removing the source, revoking a collaborator, private thumbnail access, changing a board to private, and export after reordering. Exclude Pinterest scraping, arbitrary image harvesting, shopping checkout, visual similarity ML, and external-site trackers.

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