Saturday, July 4, 2026

I want to build an app called "VibeOne". ## The Problem Users want a music app with a single-tap play button and vibe customization by activity and mood rather than having to select a specific playlist — a gap explicitly identified in a Software Recommendations request citing Yandex Music's unique features unavailable elsewhere. ## Target Audience Busy professionals and students who want ambient music without decision fatigue ## Core Idea One tap to music that matches your exact mood and activity — no playlists required. VibeOne lets users set their current activity (working, commuting, exercising) and mood with two quick taps, then instantly starts playing a curated stream without requiring playlist selection. Unlike Spotify or Apple Music, there is no browsing or choosing — just press play and the app figures it out. Inspired directly by Yandex Music's vibe feature which has no equivalent in Western streaming apps. ## Monetization Strategy $4.99/month subscription after 7-day free trial; annual plan at $39.99 ## Requirements - Category: Productivity - Difficulty: Month - 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 "AgentFlow". ## The Problem Developers cannot enter flow state when using AI coding agents because they require constant interruption and babysitting, negating the productivity benefit — explicitly raised in a 159-upvote HN thread asking about different ways of using LLMs for coding. ## Target Audience Software developers using Claude Code, Codex, or Cursor who feel their concentration is constantly broken ## Core Idea Enter true flow state while coding with AI by replacing constant interruptions with async handoffs. AgentFlow wraps AI coding agents like Claude Code and Codex with a queue-based interaction model where you define tasks upfront, the agent works independently, and you review batched results on your own schedule instead of being interrupted every 30 seconds. It monitors agent progress and only pings you when genuinely blocked rather than for every micro-decision. Directly addresses the complaint in a 159-upvote HN thread that AI coding assistants make flow state impossible. ## Monetization Strategy $15/month SaaS subscription; free tier limited to 3 concurrent tasks ## 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 "CodePulse". ## The Problem Developers are becoming so dependent on AI that they cannot write code independently, with multiple Stack Overflow questions asking how to code without AI assistance, representing a growing crisis of skill atrophy among junior and mid-level engineers. ## Target Audience CS students, junior developers, and mid-level engineers who feel their foundational coding skills eroding ## Core Idea Rebuild your coding instincts with daily practice sessions that deliberately keep AI out of the loop. CodePulse is a structured practice app for developers who have become over-reliant on AI and want to recover their ability to write code independently. It presents progressively harder problems with documentation references but no AI hints, tracks your independence score over time, and uses spaced repetition to reinforce concepts you struggled with. Validated by three separate Stack Overflow questions scoring 119, 23, and 14 upvotes asking how to code without AI dependence. ## Monetization Strategy $9.99/month subscription; university/bootcamp bulk licensing at $5/seat ## 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.

I want to build an app called "BurnSignalOS". ## The Problem Open-source contribution graphs gamify over-commitment and maintainers have no tool to detect when contributors are heading toward burnout before they disappear — validated by 1,789 upvotes and 202 comments on the isaacs/github issue. ## Target Audience Open-source project maintainers, engineering managers at companies with large FOSS contributions ## Core Idea Detect open-source contributor burnout patterns before your best maintainers silently disappear. BurnSignalOS connects to GitHub repositories and analyzes contribution velocity, PR response times, comment sentiment, and commit frequency to generate a burnout risk score for each contributor before they disengage. It sends gentle, private nudges to at-risk contributors and optional summary digests to project leads so they can check in proactively. Validated by a 1,789-upvote GitHub issue on the isaacs/github repo documenting how contribution graphs actively harm contributor wellbeing. ## Monetization Strategy Free for public repos up to 5 contributors; $12/month per organization for private repos and advanced analytics ## Requirements - Category: Health - Difficulty: Month - Suggested stack: Next.js + Supabase + PWA + Chart.js 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 "BuddyRevive". ## The Problem Claude Code's /buddy companion feature was silently removed on April 9 with no changelog entry, generating 2,030 upvotes and 262 emotionally charged comments from developers who had formed genuine attachment to it. ## Target Audience Claude Code users who relied on /buddy for morale, focus, and pair-programming feel ## Core Idea Restore the Claude Code /buddy companion with a customizable, persistent AI pair-programming partner that lives in your terminal. When Anthropic silently removed /buddy from Claude Code with no changelog entry, over 2,000 developers voiced genuine grief and attachment in one of the most emotionally charged GitHub issues in the repo's history. BuddyRevive is a lightweight terminal daemon that hooks into Claude Code's session lifecycle and injects a configurable companion persona — complete with memory, personality, and status-line presence — so developers can reclaim the morale boost and emotional continuity that /buddy provided. It runs locally, requires no Anthropic account changes, and persists across sessions. ## Monetization Strategy Free core with a $5/month Pro tier for custom personas, memory persistence, and multi-agent buddy switching ## 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 "WeightAudit". ## 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 — validated by 471 upvotes and 247 comments on the Show HN post. ## Target Audience Privacy-conscious individuals, public figures, researchers, and organizations concerned about AI data exposure ## Core Idea Audit what frontier AI models know about you and track how that knowledge changes across model releases. As more internet traffic flows into LLMs instead of search engines, individuals and organizations have no systematic way to discover what AI models have memorized about them, compare recognition across model families, or submit structured removal or correction requests. WeightAudit queries a configurable set of frontier and open-weight models in parallel using standardized probe prompts, clusters and diffs the responses across releases, and produces a personal knowledge-drift report showing what changed between GPT-4o, Claude 3.5, Llama 3, and others. A scheduled monthly re-audit emails you whenever your 'footprint' in the weights materially changes. ## Monetization Strategy Freemium — 3 models free, $9/month for full multi-model auditing and monthly drift 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 "ChromeStoreLens". ## The Problem Chrome extension developers face opaque and inconsistent rejections from the Chrome Web Store with vague reasons and no clear path to understand what changes are needed or how to successfully appeal. ## Target Audience Indie developers and small teams building and publishing Chrome extensions ## Core Idea Decode why your Chrome extension was rejected and get a concrete checklist of changes needed to get approved. Chrome Web Store rejections arrive with vague labels like 'spam' or 'additional functionality' that give developers no actionable path forward, forcing them to guess at what changed, post frustrated questions on forums, and resubmit blindly. ChromeStoreLens lets developers paste their rejection email and upload their extension manifest and source zip, then uses pattern matching against a curated database of known rejection reasons, policy interpretations, and successful appeal examples to produce a prioritized fix checklist. It also provides templated appeal letters tailored to each rejection category, dramatically reducing the back-and-forth with Google's review team. ## Monetization Strategy $7/month subscription or $15 one-time per rejection analysis; free for first analysis to drive acquisition ## 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 "MentorFOSS". ## The Problem Early CS students and career-changers with no formal employment history have no centralized resource for finding FOSS internships and mentored contribution opportunities — highlighted in a 51-upvote Lobsters thread with active discussion. ## Target Audience CS students in their first two years, self-taught developers seeking their first open-source contribution credit ## Core Idea A curated, searchable directory of FOSS internships and mentored contribution programs for students and career-changers with no professional experience. Early CS students and career-changers face a chicken-and-egg problem: they need experience to get internships but need internships to get experience. FOSS programs like GSoC, Outreachy, and dozens of smaller project-specific opportunities exist but are scattered across individual project wikis, mailing lists, and Discord servers with no central discovery layer. MentorFOSS aggregates these opportunities, tags them by required skill level (true beginner through intermediate), programming language, and time commitment, and sends personalized weekly digests matched to a user's self-reported skills and availability. Projects can submit their own mentorship openings for free, creating a self-sustaining supply side. ## Monetization Strategy Free for job seekers; $49/month for organizations to feature their programs and receive applications through the platform ## Requirements - Category: Education - Difficulty: Week - 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.

I want to build an app called "ForgeBridge". ## The Problem Jujutsu and other non-Git VCS users have no forge that supports change-centric workflows — GitHub and GitLab assume branch-based PRs that map poorly to how these tools actually work, as discussed extensively in the Lobsters forge feature request thread. ## Target Audience Developers using Jujutsu, Pijul, or Mercurial who need a collaboration platform that matches their mental model ## Core Idea A code forge built for Jujutsu and change-centric VCS workflows that GitHub and GitLab fundamentally cannot support. ForgeBridge replaces branch-based PRs with change-based review units, letting Jujutsu and Pijul users submit, discuss, and merge changes in a way that maps naturally to how their tools actually work rather than forcing an awkward Git branch metaphor. It supports offline-first collaboration, per-change comments that survive rebases, and a GitHub-compatible API so CI integrations keep working. Validated by a 59-upvote Lobsters thread with 91 comments from users frustrated that no forge natively supports these workflows. ## Monetization Strategy $10/month per team; self-hosted open-core with paid cloud offering ## 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 "MultiGitSwitch". ## The Problem Developers working with both personal and work GitHub accounts must manually switch credentials every time they change repositories, leading to accidental wrong-identity commits and constant friction with no automatic per-repo identity solution. ## Target Audience Developers who maintain separate personal and work GitHub accounts and switch between them daily ## Core Idea Automatically apply the right GitHub identity per repository so you never accidentally push personal commits to work projects. MultiGitSwitch is a lightweight background utility that watches your current working directory and silently switches your git config identity, SSH key, and credential helper based on which repository you are in. It integrates with GitHub Desktop and the CLI, requires a one-time setup mapping directories to identities, and shows a subtle menu bar indicator of which account is currently active. Addresses a 1,349-upvote GitHub Desktop issue that has received no official resolution despite years of requests. ## Monetization Strategy Free open-source core; $5 one-time Mac/Windows app purchase for the GUI and menu bar indicator ## 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 "APIVersionLint". ## The Problem Developers frequently debate how to version public web APIs and make structural mistakes like mixing route versioning with semantic versioning or shipping breaking changes silently — a recurring pain discussed in the Lobsters API versioning thread. ## Target Audience Backend developers and API platform teams maintaining public or partner-facing APIs ## Core Idea Lint your API design decisions against versioning best practices and catch breaking changes before they reach production. Developers repeatedly make the same structural mistakes when versioning public APIs — mixing route versioning with semantic versioning, embedding version numbers in resource names, or shipping breaking changes silently without a major version bump. APIVersionLint is a CLI and CI action that compares two versions of an OpenAPI or JSON Schema spec, flags breaking changes according to configurable severity rules, and explains why specific patterns (like /api/v1 alongside SemVer headers) are considered anti-patterns with links to relevant guidance. It integrates into GitHub Actions as a required check so breaking changes require an explicit override comment before merging, making versioning discipline automatic rather than aspirational. ## Monetization Strategy Free open-source CLI, $12/month SaaS for hosted diff history, team dashboards, and Slack breaking-change 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 "FlowTerminal". ## The Problem Developers cannot enter flow state with AI coding agents because they require constant babysitting, and tools like gemini-cli overwrite terminal tab titles making it impossible to track which tab is which across many sessions. ## Target Audience Developers running multiple concurrent AI coding agent sessions ## Core Idea A distraction-free terminal wrapper that lets AI coding agents run unattended without hijacking your tab labels or requiring babysitting. Developers using Claude Code, Gemini CLI, and similar agents face two compounding frustrations: the agents constantly overwrite terminal tab titles making multi-session management impossible, and they require frequent interruptions that shatter flow state. FlowTerminal is a thin terminal multiplexer layer that freezes your custom tab labels regardless of what the underlying agent writes to the title escape sequence, queues agent check-in prompts into a non-interrupting notification tray, and surfaces a single ambient status bar showing all running agent states at a glance. It works with any terminal emulator and any agent via a simple wrapper script. ## Monetization Strategy Free open-source core, $8/month cloud sync tier for shared session configs across machines ## 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 "MailRescue". ## The Problem Gmail silently routes messages to Trash rather than Spam due to conflicting filter rules, and users struggle to write syntactically correct body-matching filter search strings — both pain points appear across multiple Web Apps Stack Exchange questions. ## Target Audience Gmail power users, developers who receive high volumes of automated email, mailing list subscribers ## Core Idea Visually debug your Gmail filters to find why messages are landing in Trash instead of Spam, and write body-matching search strings without syntax guesswork. Gmail silently routes messages to Trash instead of Spam when filter rules conflict, and separately, constructing syntactically correct search strings for body-text matching is so undocumented that even power users get it wrong. MailRescue provides a two-part tool: a filter conflict visualizer that ingests your exported Gmail filter XML and draws a dependency graph highlighting rules that shadow or override each other, and an interactive search string builder with live syntax validation and example-driven autocomplete for body-matching operators. Together these let users fix the Trash routing bug and write correct filters without trial and error or reading impenetrable documentation. ## Monetization Strategy Free tier for up to 20 filters, $5/month Pro for unlimited filters and a filter migration assistant ## 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 "AccessibilityReplay". ## The Problem Developers working with blind users discover invisible accessibility gaps too late because there is no automated tool that replays real user flows through a screen reader and reports exactly where the experience breaks down. ## Target Audience Web developers, QA engineers, and product teams who need to ship WCAG-compliant products without a full-time accessibility specialist ## Core Idea Automatically replay your web app's user flows through a screen reader and surface the exact moments where a blind user gets stuck. The HN post about accessibility gaps discovered while working with a blind client resonated deeply — developers rarely discover screen reader failures until a real user hits them, because manually testing with VoiceOver or NVDA requires specialist knowledge and is time-consuming to set up. AccessibilityReplay records Playwright or Cypress test scripts and replays them through a headless screen reader simulation, generating a timestamped report of every navigation dead-end, unlabeled control, focus trap, and announcement gap encountered along the way. Each issue links directly to the offending DOM element and suggests a WCAG-compliant fix, making accessibility auditing a routine part of CI rather than an afterthought. ## Monetization Strategy $19/month for up to 5 projects, $79/month for teams with CI integration and priority support ## 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 "LobsterGems". ## The Problem Lobsters has years of high-quality technical discussion but no way to search or surface the best historical comments — users explicitly asked for a way to find old gems they have missed in a 172-upvote thread. ## Target Audience Lobsters regulars, technical researchers, and developers who want to mine years of curated programming discussions ## Core Idea Surface the best Lobsters comments and threads you missed across years of high-quality technical discussion. LobsterGems indexes the full Lobsters archive by comment score, thread depth, and semantic similarity so you can search for insights on any technical topic and find the best historical discussion in seconds. It surfaces hidden gems through a daily digest of top-voted older comments on topics you follow, and lets users curate personal collections of their favorite threads. Validated by a 172-upvote Lobsters thread where users explicitly asked for a way to find old gems from the site's history. ## Monetization Strategy Free web access; $3/month for personal digest emails, saved collections, and full semantic search ## Requirements - Category: Social - Difficulty: Week - 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 "TerraGraph". ## The Problem Terraform teams consistently complain that infrastructure documentation falls out of sync with no automated solution that reads actual state, and the backend variable limitations force additional manual workaround files — validated by 1,301 and 1,551 upvotes across two GitHub issues. ## Target Audience DevOps engineers and platform teams using Terraform in production ## Core Idea Auto-generate always-current infrastructure diagrams and runbooks directly from your live Terraform state — no YAML, no manual updates. Terraform's long-standing inability to use variables in backend config blocks forces teams into brittle per-environment workarounds, and separately, infrastructure documentation perpetually drifts out of sync because no tool reads actual Terraform state to generate it. TerraGraph solves the documentation side of this pain: it runs as a post-apply hook, reads your state file, and produces a versioned Mermaid or draw.io diagram plus a Markdown runbook with resource counts, dependency chains, and change diffs from the previous apply. The output commits automatically to your repo so documentation is always in sync with reality without any human effort. ## Monetization Strategy Free CLI open-source, $15/month SaaS for hosted diagram storage, shareable links, and Slack/Confluence push integration ## 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 "SyntaxKeep". ## The Problem Users copying syntax-highlighted code from ChatGPT and other AI tools lose all color formatting when pasting into Google Docs — a frustrating daily friction point with no clean solution despite users trying every obvious approach. ## Target Audience Developers, students, and technical writers who document code in Google Docs ## Core Idea Copy syntax-highlighted code from any AI chat and paste it into Google Docs with full color formatting intact. SyntaxKeep is a lightweight browser extension that intercepts code copy events from ChatGPT, Claude, and other AI tools and converts the syntax highlighting into Google Docs-compatible rich text formatting before it hits your clipboard. It requires zero configuration — install and copy as normal, but the colors survive the paste. Directly addresses the frustrating daily friction described on Web Apps Stack Exchange where users report exhausting every obvious solution with no success. ## Monetization Strategy One-time purchase at $4.99 via Chrome Web Store; optional $2.99/month for multi-browser sync ## Requirements - Category: Productivity - Difficulty: Weekend - 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 "ScopeBlaster". ## The Problem Configuring a Slack app with ~30 OAuth scopes requires clicking through a dropdown 30 separate times with no bulk-add option, wasting significant developer time on pure UI friction with no workaround found. ## Target Audience Developers building Slack apps and integrations ## Core Idea Paste a list of Slack OAuth scopes and add them all to your app in one click instead of selecting them one by one. Configuring a Slack app that needs 30 OAuth scopes currently requires 30 separate dropdown interactions — click Add Scope, type the name, select it, repeat. ScopeBlaster is a browser extension that adds a bulk-import textarea to the Slack app configuration page, parses a newline or comma-separated list of scope names, and injects them all in a single automated sequence using the existing UI so no unofficial API calls are needed. It also lets you export your current scope list as a shareable text file so your team can reproduce the configuration instantly on a new app. ## Monetization Strategy Free browser extension with a $3 one-time tip-jar purchase; upsell to a $5/month team license for shared scope presets ## Requirements - Category: Productivity - Difficulty: Weekend - 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 "OfflineLingo". ## The Problem Users on completely offline Windows 10 machines with no admin rights need self-contained translation software with no internet dependency — a gap explicitly raised on Software Recommendations Stack Exchange with no viable free solution found. ## Target Audience Researchers, government workers, and contractors operating in air-gapped or highly restricted computing environments ## Core Idea A fully self-contained offline translator that runs on air-gapped Windows machines with no admin rights required. OfflineLingo is a portable executable that bundles a compact local translation model and runs entirely from a USB drive or user directory on Windows 10, requiring no installation, no internet, and no admin privileges. It supports French-to-English and other common language pairs via quantized ONNX models small enough to fit on a flash drive. Directly responds to a Software Recommendations Stack Exchange question where no viable free solution was found for this specific constrained environment. ## Monetization Strategy Free core app with a $19 one-time pro upgrade for additional language pairs and batch document translation ## 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 "ActionsUnlock". ## The Problem GitHub Actions matrix jobs have no native allow-failure support per individual job and no multi-choice input type, forcing teams into brittle workarounds that break status checks and create confusing CI output. ## Target Audience DevOps engineers and platform teams using GitHub Actions for monorepo or multi-target CI pipelines ## Core Idea Add per-job allow-failure and multi-select inputs to GitHub Actions without wrestling with brittle YAML workarounds. ActionsUnlock is a GitHub App that extends Actions with two missing primitives: per-job allow-failure flags in matrix builds and a multi-choice input type for manual workflow triggers. It works by injecting a thin post-processing step into your pipeline that handles the status logic cleanly, letting you mark specific matrix jobs as non-blocking without contaminating your overall workflow status. Validated by 1,575 and 1,321 upvotes across two separate GitHub issues that have gone unresolved for years. ## Monetization Strategy $8/month per organization; free for open-source public repositories ## 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.