after-hours

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 test this", "write a pre-mortem", "show me how this fails", "what would the support tickets look like", "pressure test this flow", or any request to make abstract risk viscerally real before or during design.

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 the onboarding", "is this obvious to a newcomer", "what would a stranger see here", "ghost user this", or any request to check whether the product relies on inside knowledge.

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 project values", "give this project a spine", "build a lorebook", or any moment when naming, tone, scope, or product identity feel undefined or are starting to drift.

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 terminology", "what should we call this", "the API and UI use different words", or any situation where muddy, overlapping, or conflicting names are distorting the user's mental model.

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 principles", "distill the taste", "what rules is this obeying", or any request to learn from a reference without copying it.