acost1a
UserFuture-you interrogates today's architecture decision, then files the regret before you commit it.
Categories
Indexed Skills (2)
future-regret
Use when the user is about to commit to an architecture, data-model, dependency, or design decision on an existing codebase (picking a database or schema shape, build vs buy, adopting a library or pattern, locking an API contract, or "let's just do X for now"), or asks what they'll regret later ("will I regret this", "what will bite us", "future-proof this"). Run BEFORE writing the code or agreeing. Do NOT use for brand-new product ideas, routine bug fixes, or trivially reversible choices.
murderboard
Use when the user pitches a new idea — a product, SaaS, startup, app, feature, side project, or business ("I have an idea", "what if I built", "I want to make", "thinking of building") — or explicitly asks to stress-test one ("murderboard this", "what could go wrong", "poke holes in this"). Run BEFORE agreeing, praising, planning, or implementing. Do NOT use for routine work on an existing codebase (bug fixes, refactors, code review, or building a feature the user already committed to).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.