after-hours

Plugin after-hours from marketplace limitless in pyros-projects/limitless. Commands read from the repo's manifest — 8 days ago.

Skills (7)

• failure-postcards

  This skill should be used when the user wants to pressure-test a feature, flow, or product idea by generating emotionally concrete future failure artifacts such as support tickets, angry emails, user complaints, one-star reviews, or postmortem fragments. Responds to "what could go wrong", "stress te

• ghost-user

  This skill should be used when the user wants a first-time user simulation — a cold-start walkthrough from the perspective of someone with zero context, zero author knowledge, and zero sympathy for what the builders intended. Responds to "pretend you're a new user", "do a first-contact pass", "test

• local-mythology

  This skill should be used when the user wants to define a project's identity, build a lorebook, articulate what a product believes and refuses to become, or capture the implicit rules a project lives by. Responds to "what is this project trying to be", "the product is drifting", "write down the proj

• naming-as-design

  This skill should be used when the user wants to audit, clean up, or redesign the naming in a product, workflow, or system — treating names as structural design decisions, not editorial polish. Responds to "the naming is a mess", "we call the same thing three different names", "clean up the terminol

• taste-distiller

  This skill should be used when the user wants to understand why a product, interface, writing style, or codebase feels unusually good, or to extract the hidden governing rules behind a reference. Responds to "I like this but I can't explain why", "what makes this work", "extract the design principle

• the-courage-to-delete

  This skill should be used when the user wants help subtracting — identifying what to cut, delete, or deprioritize so the core product can breathe again. Responds to "what should I cut", "this is too bloated", "what can I delete", "simplify this", "what's diluting the core", "what would this look lik

• vibe-checker

  This skill should be used when the user wants to check whether a product, prototype, or workflow feels emotionally coherent — whether it seems like one mind made it, or whether different parts pull in different tonal directions. Responds to "does this feel coherent", "check the vibe", "this feels of