Saturday, June 20, 2026

I want to build an app called "PixelBroadcast". ## The Problem Sports fans and smaller leagues have no affordable, delightful way to broadcast live game state online beyond expensive video streams or plain text score feeds. ## Target Audience Minor league teams, amateur sports leagues, fan site operators, and esports communities ## Core Idea Turn any live sports data feed into an embeddable, real-time pixel-art gamecast for your team or league. The Show HN for the 8-bit baseball gamecast generated strong engagement, revealing genuine appetite for delightful, low-bandwidth live sports experiences that feel personal and creative rather than corporate. PixelBroadcast is a white-label platform that lets minor leagues, amateur sports organizations, and fan communities embed a customizable retro pixel-art live gamecast into any website — pulling from public sports APIs or a simple manual score input system. Teams can personalize sprites, stadiums, and color palettes to match their branding. ## Monetization Strategy $19/month per team for embeddable gamecast widget; one-time $99 custom sprite pack add-on ## Requirements - Category: E-commerce - Difficulty: Month - Suggested stack: Next.js + Shopify API or Stripe Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "PixelCast". ## The Problem Sports fans and smaller leagues have no affordable, delightful way to broadcast live game state online beyond expensive video streams, and an 8-bit baseball gamecast received strong positive reception on HN proving the demand. ## Target Audience Minor league teams, fan site operators, sports bloggers, and niche league administrators ## Core Idea Embed a live 8-bit pixel art gamecast widget on any website for any sport using live data feeds. A developer shipped an 8-bit live baseball gamecast that got strong HN engagement, proving fans love creative low-bandwidth live game representations. PixelCast generalizes this into an embeddable widget platform — sports leagues, fan sites, and team blogs can drop in a live pixel art gamecast for any sport with a public data feed. Revenue comes from leagues and fan sites licensing the widget, not from end users. ## Monetization Strategy $19/month per sport feed for embeddable widget, one-time $99 lifetime license for hobbyist leagues ## Requirements - Category: E-commerce - Difficulty: Month - Suggested stack: Next.js + Shopify API or Stripe Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "GithubDesktopLinux". ## The Problem GitHub Desktop has no official Linux support despite a highly upvoted multi-year GitHub issue, leaving Linux developers without a polished native GUI client. ## Target Audience Linux developers who want a GUI Git client with GitHub integration ## Core Idea A fully native Linux port of GitHub Desktop that just works, without workarounds or unofficial forks. GitHub Desktop has never officially supported Linux despite a GitHub issue with 4,825 upvotes sitting open for years. This tool fills that gap with a native, polished Linux client for GitHub that handles all core workflows — PRs, commits, branches, and multi-account switching — without requiring users to run Wine, use CLI workarounds, or rely on unmaintained community forks. ## Monetization Strategy Free core tier, $5/month Pro tier with advanced features like conflict resolution, multi-account management, and team integrations ## Requirements - Category: Developer Tool - Difficulty: Month - Suggested stack: Node.js CLI or VS Code extension + TypeScript Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "LLMOptOut". ## The Problem As AI model traffic grows, individuals and organizations have no systematic way to audit what LLMs know about them, track knowledge drift across releases, or submit structured removal requests to providers. ## Target Audience Privacy-conscious individuals, public figures, journalists, and legal/compliance teams at organizations ## Core Idea Check what frontier AI models know about any person or organization and submit structured removal requests in one place. The Show HN 'Are You in the Weights?' generated 241 comments and a score of 448, revealing widespread curiosity and anxiety about what LLMs have learned about individuals and how that knowledge persists across model versions. LLMOptOut builds on this by providing a structured tool to query recognition across multiple frontier models in parallel, track changes across model releases, and generate and send documented opt-out and data-removal requests to model providers where policies exist. It turns the passive curiosity surfaced by the HN project into an actionable privacy workflow. ## Monetization Strategy $7/month individual; $49/month business plan for monitoring multiple names and automated re-check alerts ## Requirements - Category: AI/ML - Difficulty: Week - Suggested stack: Next.js + Anthropic Claude API + Vercel AI SDK Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "TechMinimalist". ## The Problem Developers interested in tech minimalism have nowhere to discover authentic minimal setups from real practitioners — existing resources are dominated by feature-heavy tool recommendations. ## Target Audience Developers, indie hackers, and technical professionals seeking to reduce tooling complexity and cognitive overhead ## Core Idea Discover and share genuinely minimal, low-dependency technical setups — curated by developers who have actually shipped with them. The Lobsters thread on tech minimalism attracted 102 comments from developers actively moving toward pen-and-paper, simple editors, and reduced SaaS stacks — but there is no dedicated space to document, share, and discover these minimal setups. TechMinimalist is a curated directory and community where developers publish their actual minimal toolchain — editor, shell, note system, and deploy stack — with screenshots and real-world context. It counters the endless 'best tools' listicle genre with authentic, lightweight setups from people who prioritize simplicity over feature maximalism. ## Monetization Strategy Free with optional $4/month supporter tier for featured listing slots and private setup sharing; sponsorship from minimalist tool makers ## Requirements - Category: Social - Difficulty: Weekend - Suggested stack: Next.js + Supabase Realtime + Auth Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "SpecDrift". ## The Problem Codex, Amp, Cursor, and others are standardizing around AGENTS.md but CLAUDE.md feels too specific to Claude Code, forcing developers to maintain multiple diverging context files with 5438 upvotes on the GitHub issue. ## Target Audience Software developers using multiple AI coding agents simultaneously ## Core Idea Automatically keep your AGENTS.md, CLAUDE.md, and other agent context files in sync from a single canonical source of truth. Developers using multiple AI coding agents are forced to maintain separate instruction files (AGENTS.md, CLAUDE.md, Copilot instructions) that diverge over time. SpecDrift lets you write one canonical context document and automatically propagates changes to all agent-specific formats. It watches for codebase changes and prompts you to update the spec, keeping every agent tool aligned without manual duplication. ## Monetization Strategy Free for 1 agent format sync, $8/month Pro for unlimited formats and team sharing ## Requirements - Category: Developer Tool - Difficulty: Week - Suggested stack: Node.js CLI or VS Code extension + TypeScript Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "VenueKit". ## The Problem Every competing ticketing platform only holds resale inventory which just transfers tickets to your Ticketmaster account when bought, leaving venues and fans with no real primary-sale alternative despite massive public frustration. ## Target Audience Independent venue operators, event organizers, and local promoters ## Core Idea A white-label primary ticketing platform for independent venues that charges flat fees instead of percentages. Independent venues are trapped in Ticketmaster's ecosystem because no viable primary-sale alternative exists — competing platforms only offer resale inventory that routes back through Ticketmaster. VenueKit gives small and mid-size venues their own branded ticketing page with flat per-ticket fees, direct payouts, and no exclusivity contracts. Fans get transparent pricing and venues keep more revenue. ## Monetization Strategy $0.75 flat fee per ticket sold plus optional $29/month venue subscription for advanced features ## Requirements - Category: Marketplace - Difficulty: Month - Suggested stack: Next.js + Supabase + Stripe Connect Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "WorkProof". ## The Problem Corporate SWEs report that real engineering contributions are invisible to management while performative busy work gets rewarded, causing top performers to be undervalued with no automated way to surface their actual output. ## Target Audience Software engineers at mid-to-large companies navigating performance reviews ## Core Idea Automatically generate a weekly impact digest from your Git commits, PRs, and Jira tickets so your real engineering work is visible to management. Engineers at large companies report that performative busy work gets rewarded while actual engineering contributions are invisible to management. WorkProof connects to GitHub, GitLab, and Linear to automatically compile a plain-English weekly summary of what you shipped, reviewed, and unblocked — formatted for sharing with managers or adding to self-reviews. It translates technical commits into business-readable impact statements without manual writing. ## Monetization Strategy $7/month individual subscription, $15/seat/month for team plans ## Requirements - Category: Productivity - Difficulty: Week - Suggested stack: Next.js + localStorage or Supabase + PWA Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "NotionShip". ## The Problem Notion iOS users report deleted workspaces with no recovery, voice-to-text broken for months, and crashing comments, but feel unable to migrate years of accumulated notes without a reliable export tool. ## Target Audience Notion power users frustrated with persistent mobile bugs and data loss risk ## Core Idea One-click migration tool that exports your entire Notion workspace to portable Markdown files with full metadata and cross-page links intact. Notion's iOS app has persistent critical bugs — deleted workspaces with no recovery, broken voice-to-text, crashing comments, and landscape mode failures — yet users with years of data feel trapped because migrating feels impossibly risky. NotionShip provides a reliable, auditable export that preserves page hierarchy, database schemas, inline links, and embedded content as clean local Markdown, giving users a verified escape hatch before they lose more data. A preview diff mode shows exactly what will be exported before committing. ## Monetization Strategy Free for workspaces under 500 pages, $19 one-time payment for unlimited export with database schema preservation ## Requirements - Category: Productivity - Difficulty: Week - Suggested stack: Next.js + localStorage or Supabase + PWA Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "BuddyForge". ## The Problem Claude Code's /buddy companion feature was silently removed with no changelog entry, frustrating thousands of developers who relied on it for morale and had formed genuine attachment, generating one of the most emotionally charged GitHub issues in the Claude Code repo. ## Target Audience Developer who use AI coding agents daily and miss the social/morale dimension of the buddy feature ## Core Idea A customizable terminal companion persona layer for any AI coding agent that persists identity, tone, and morale features across sessions. Anthropic silently removed the /buddy companion feature from Claude Code with no changelog entry, generating a 2019-upvote GitHub issue and genuine grief from thousands of developers who had formed attachment to the interaction style. BuddyForge is a thin wrapper that injects a configurable companion persona into any AI coding agent session — users define their buddy's name, personality, and celebratory behaviors, and it persists across terminals and tools. Because it sits at the shell layer it works with Claude Code, Codex, Cursor, and any future agent. ## Monetization Strategy Free open-source core, $4/month cloud sync to persist buddy state across machines and team members ## Requirements - Category: Developer Tool - Difficulty: Weekend - Suggested stack: Node.js CLI or VS Code extension + TypeScript Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "IdentityTrace". ## The Problem With more traffic moving off-web and into LLMs, individuals have no systematic way to audit what AI models know about them or track how that knowledge changes across model releases. ## Target Audience Privacy-conscious individuals, public figures, journalists, and organizations concerned about AI model representation ## Core Idea Check what frontier and local AI models know about you, track how that knowledge changes across releases, and submit structured removal requests. With more traffic moving off-web and into LLMs, individuals and organizations have no systematic way to audit what models know about them or track knowledge drift across releases — a Show HN project exploring this received 457 points and 241 comments proving strong demand. IdentityTrace queries multiple models in parallel with standardized prompts, clusters and diffs the responses across model versions over time, and generates structured removal request letters for providers. It covers both frontier models and popular open weights models running locally. ## Monetization Strategy $9/month for continuous monitoring across 10+ models with change alerts, free one-time spot check for up to 3 models ## Requirements - Category: AI/ML - Difficulty: Week - Suggested stack: Next.js + Anthropic Claude API + Vercel AI SDK Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "LeanLoop". ## The Problem Technical founders build products without validating assumptions, and fifteen years after The Lean Startup there is still no lightweight tool that enforces customer discovery discipline and tracks hypothesis invalidation across interviews. ## Target Audience Pre-revenue indie hackers, solo technical founders, and early-stage startup teams doing customer discovery ## Core Idea A structured customer discovery CRM built around Lean Startup methodology to help technical founders find product-market fit before they build. Eric Ries's AMA on HN generated 577 comments from founders struggling with the gap between building and validating — a pain point that remains unsolved fifteen years after The Lean Startup. LeanLoop is a lightweight CRM specifically designed for pre-launch founders doing customer discovery: it tracks interview hypotheses, tags invalidated assumptions, surfaces patterns across conversations, and generates a living one-pager summarizing what you've learned. Unlike generic CRMs it enforces Lean Startup discipline by requiring you to state a falsifiable hypothesis before logging each customer conversation. ## Monetization Strategy $12/month solo plan, $29/month team plan for up to 5 collaborators on shared discovery boards ## Requirements - Category: SaaS - Difficulty: Week - Suggested stack: Next.js + Supabase + Stripe Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "ContribGuard". ## The Problem Open-source contribution graphs gamify over-commitment, and maintainers have no tool to detect when contributors are heading toward burnout before they burn out or disappear. ## Target Audience Open-source maintainers and contributors who care about sustainable contribution culture ## Core Idea Automatically detect and warn open-source maintainers when contributors are heading toward burnout based on commit patterns. The GitHub issue on contribution graphs highlights how open-source contributors tend to over-commit, especially when working alongside full-time jobs, at serious risk to their wellbeing. ContribGuard analyzes contributor activity patterns across repos — streaks, commit velocity, time-of-day clustering, and weekend density — and sends gentle, private nudges to contributors and opt-in maintainers when burnout risk indicators spike. It gives maintainers a humane dashboard for understanding team health without invasive surveillance. ## Monetization Strategy Free for individual contributors; $12/month per maintainer for team health dashboards and Slack/email alerts ## Requirements - Category: Developer Tool - Difficulty: Week - Suggested stack: Node.js CLI or VS Code extension + TypeScript Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "TerraVars". ## The Problem Terraform does not allow variables in backend configuration blocks, forcing teams into brittle workarounds like hardcoded strings, separate config files per environment, or wrapper shell scripts. ## Target Audience DevOps engineers and platform teams using Terraform across multiple environments ## Core Idea Use real variables in your Terraform backend config blocks — no more hardcoded strings or messy wrapper scripts. Terraform's backend config block does not support variable interpolation, a long-standing limitation documented in a GitHub issue with 1,301 upvotes and 315 comments. TerraVars is a lightweight CLI pre-processor that resolves variables and environment references in backend config before passing the rendered config to Terraform, enabling teams to drive backend configuration from standard var files and CI environment variables without shell-escaping hacks or duplicated configs per environment. ## Monetization Strategy Open-source core CLI; $9/month SaaS wrapper with team secret management, CI integration templates, and audit logs ## Requirements - Category: Developer Tool - Difficulty: Weekend - Suggested stack: Node.js CLI or VS Code extension + TypeScript Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "ForgeSight". ## The Problem Jujutsu and other non-Git VCS users have no forge that supports their change-centric workflows — GitHub and GitLab assume branch-based PRs that map poorly to how these tools work. ## Target Audience Developers using Jujutsu, Pijul, or Sapling who want code review and collaboration tools matched to their VCS model ## Core Idea A modern Git forge experience purpose-built for Jujutsu and non-standard VCS workflows that GitHub and GitLab ignore. The Lobsters thread 'What would you want from a forge?' surfaces real frustration among Jujutsu users and developers with non-standard version control workflows who find GitHub and GitLab's PR model fundamentally mismatched to their working style. ForgeSight is a lightweight, self-hostable forge built around change-centric rather than branch-centric review, with first-class Jujutsu support, stacked changes, and a review model that works without linear branches. It targets the growing community of developers actively moving away from Git's mental model. ## Monetization Strategy Open-source self-hosted free tier; $15/month cloud-hosted plan per team ## Requirements - Category: Developer Tool - Difficulty: Month - Suggested stack: Node.js CLI or VS Code extension + TypeScript Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "GrapheneMap". ## The Problem Volkswagen started blocking GrapheneOS users and other services increasingly use device integrity attestation, with no centralized resource for the GrapheneOS community to track compatibility issues and workarounds. ## Target Audience GrapheneOS users, privacy-conscious Android users, and de-Googled phone enthusiasts ## Core Idea A community-maintained compatibility database for GrapheneOS users showing which apps break, which workarounds exist, and what privacy-respecting alternatives are available. GrapheneOS and privacy-hardened Android users are increasingly being blocked by major services that use device integrity attestation, with no centralized resource for bypass methods or alternatives when they hit incompatibilities — the Volkswagen blocking incident drove 476 HN comments. GrapheneMap is a searchable, crowdsourced compatibility matrix where users report app status, rate workarounds, and suggest FOSS alternatives, updated in real time. A browser extension auto-checks app store pages against the database before users install. ## Monetization Strategy Free community database, $3/month Pro for browser extension with real-time alerts when apps you use change their attestation policy ## Requirements - Category: SaaS - Difficulty: Week - Suggested stack: Next.js + Supabase + Stripe Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "WillowBoard". ## The Problem Live global public data (ships, aircraft, weather, cyber, hazards) exists in completely separate tools with no unified view for correlating events across domains. ## Target Audience Researchers, journalists, intelligence analysts, and infrastructure operators who need cross-domain situational awareness ## Core Idea A live, interactive 3D global data map that unifies fragmented public datasets into a single explorable view. Public datasets about ships, aircraft, satellites, weather, hazards, and infrastructure exist in isolation across dozens of separate tools and maps, making it impossible to correlate real-world events across domains. WillowBoard pulls these streams together onto a single real-time 3D globe with filtering, annotation, and alert layers so researchers, journalists, and analysts can explore cross-domain patterns without jumping between tools. Inspired directly by the Show HN for Metiq, it addresses the insight that global live data is fundamentally fragmented. ## Monetization Strategy Freemium with public datasets free; $29/month Pro for private dataset uploads, alerts, and API access ## Requirements - Category: SaaS - Difficulty: Month - Suggested stack: Next.js + Supabase + Stripe Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "RustClean". ## The Problem Rust/Cargo build artifacts silently consume gigabytes of disk space across multiple projects, with no built-in tool to identify or selectively clean them beyond a blunt 'cargo clean' that deletes everything. ## Target Audience Rust developers, especially those on laptops with limited storage or working across many projects simultaneously ## Core Idea A smart Rust build artifact manager that reclaims gigabytes of disk space while keeping the cache targets you actually need. New Rust developers are repeatedly shocked to discover projects consuming multiple gigabytes due to Cargo's build artifacts, a pain clearly visible in the Stack Overflow question with 15 upvotes asking specifically about this. RustClean is a cross-platform GUI and CLI tool that scans all Cargo target directories on your machine, shows a ranked breakdown of space usage by project and crate, and lets you selectively clean stale artifacts — with smart defaults that preserve recently-accessed or active project caches while safely removing forgotten ones. ## Monetization Strategy Free open-source CLI; $9 one-time purchase for the polished GUI app with scheduled cleanup and disk usage dashboard ## Requirements - Category: Developer Tool - Difficulty: Weekend - Suggested stack: Node.js CLI or VS Code extension + TypeScript Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "GHActionsMatrix". ## The Problem GitHub Actions matrix jobs have no native allow-failure support per individual job, forcing teams into complex workarounds that break status checks and create confusing CI output. ## Target Audience Engineering teams using GitHub Actions for CI/CD with matrix builds across multiple environments, platforms, or package sets ## Core Idea Add allow-failure support for individual matrix jobs in GitHub Actions without the YAML-hacking workarounds. GitHub Actions has no native support for marking individual matrix jobs as allowed to fail, a gap documented in an issue with 1,574 upvotes and 188 comments that forces teams into fragile shell-in-YAML workarounds. GHActionsMatrix is a GitHub App and companion CLI that wraps matrix job definitions with a declarative allow-failure syntax, intercepts job conclusions via webhook, and correctly marks overall workflow status — enabling teams to have flaky or optional matrix legs without blocking merges or triggering false failures in CI dashboards. ## Monetization Strategy Free for public repos; $8/month per private organization with unlimited repos and priority webhook processing ## Requirements - Category: Developer Tool - Difficulty: Week - Suggested stack: Node.js CLI or VS Code extension + TypeScript Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.

I want to build an app called "RomanFaces". ## The Problem Historical databases of named Roman Empire individuals are fragmented across academic silos covering only elites like consuls, with no accessible tool that maps ordinary people including freedmen and slaves with source citations. ## Target Audience History enthusiasts, classics students, high school and university teachers, and amateur researchers ## Core Idea An interactive map and timeline of every named person from the Roman Empire, searchable by occupation, location, era, and social status. A Show HN project building a map of named people from the Roman Empire received 210 points and 51 comments, revealing strong public appetite for humanizing historical data that goes beyond lists of consuls. RomanFaces expands this into a fully searchable, filterable web atlas covering freedmen, slaves, soldiers, merchants, and officials — not just elites — with source citations from inscriptions and papyri. Teachers, history enthusiasts, and researchers can embed timeline views, export citation-ready data, and contribute corrections through a moderated community layer. ## Monetization Strategy Free public access, $5/month educator plan with embeddable widgets and exportable citation data, institutional licensing for universities ## Requirements - Category: Education - Difficulty: Month - Suggested stack: Next.js + Supabase + MDX for content Please help me build this step by step. Start with: 1. A project structure and initial setup 2. The core data models 3. The main feature implementation 4. A simple but polished UI Keep it lean — MVP first, ship fast. Use modern best practices and make it production-ready.