Build your own Hacker News.

# Build an original app inspired by Hacker News

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 link-discussion community called Linkyard, inspired by Hacker News. Members submit interesting links or text posts, vote, and discuss them in threaded comments. Keep the pilot focused on one topic, with a transparent ranking formula and a small moderation workflow.

## Design
Create an original compact text-forward interface with ranked titles, source domains, points, age, and comment counts. Use readable indentation, collapse controls, visible visited links, and a responsive discussion page. Keep the product’s own typography, colors, and naming.

## Features
1. Submissions: create link or text posts, validate HTTP(S) destinations, normalize obvious duplicate URLs, and render user text safely. Display source domains without fetching arbitrary page metadata from the server.

2. Feeds: provide newest and ranked views with stable cursor pagination. Define an explicit score/time-decay formula and derive scores from stored votes. Keep ranking reproducible in tests.

3. Voting: allow one upvote per user/post with undo, prevent self-vote inflation, and calculate counts transactionally. Do not implement hidden or random score changes to imitate a larger community.

4. Discussion: support threaded replies, collapse/expand, editing your own comments within a documented window, and deletion tombstones that preserve the thread. Show actual reply counts.

5. Moderation: flag submissions/comments, let moderators remove or restore content, rate-limit posting, and record moderation actions. Provide a clear public community guideline page.

## Tech stack
Use a Go HTTP API, PostgreSQL, and a TypeScript or server-rendered frontend. Use authenticated sessions, database uniqueness constraints for votes, bounded nesting, and a deterministic ranking function with an injectable clock. No crawler or third-party content import is required.

## Data & behavior
User; Post {authorId, kind, title, normalizedUrl, text, createdAt, moderationState}; Vote {userId, postId}; Comment {postId, parentId, authorId, text, deletedAt}; Flag; ModerationAction. Index feed ordering and thread lookups; keep removed content out of public search.

Acceptance checks and scope:
Test vote/undo retries, equal-score pagination, ranking over time, duplicate URLs, deleted parents with replies, posting restrictions, and moderator permissions. Exclude copying Hacker News posts, private ranking algorithms, scraping, notifications infrastructure, and paid 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.