rospocroccante
- 6 skills
- 0 followers
- 5 hours ago last updated
- ▌ Gauntlet Loop · rospocroccante bundleUse when the work has to beat an external standard rather than merely satisfy the person asking, and "good enough" is the failure mode. Triggers include a build or redesign or audit where quality matters more than speed, an artifact that will be judged by someone who did not commission it, or the user naming the gauntlet loop directly.
- ▌ Anti Slop Writing · rospocroccante bundleWrite prose that does not read as machine-generated, in English and Italian. Use this skill EVERY time you generate or edit text meant to be read as writing, including documents, reports, emails, posts, articles, presentations, UX copy, translations, rewrites, and chat answers the user will paste elsewhere. Trigger it also whenever the user mentions AI slop, robotic or artificial tone, em dashes, "sembra scritto da un'AI", "troppo AI", or asks for natural, human, or clean writing. If you are about to produce more than one paragraph of prose for any deliverable, consult this skill first.
- ▌ Futurismo Writing Skill · rospocroccanteUse when the user asks for meeting talking points, dev-meeting bullets, standup notes, or any brief they will read aloud (Italian or English), and when they push back that a draft sounds robotic, like an NPC, or like a changelog.
- ▌ Functional And Technical Design · rospocroccanteProduce a functional design and/or technical design document for a feature, system, or change. Use when the user asks to draft, scaffold, or structure a design doc, spec, RFC, or architecture write-up covering user-facing behavior, requirements, components, data model, APIs, or rollout.
- ▌ Simpler · rospocroccanteUse when explaining an abstract or technical concept to someone who is confused, asks to "explain it simpler / more simply / clearly", asks for an analogy or "explain like I'm five", says they keep losing the thread, or when the audience is neurodivergent (ADHD, autistic, dyslexic). Any time a concept must land concretely instead of as a wall of jargon.
- ▌ Model Roles · rospocroccanteUse when spawning subagents or splitting work across models, when an adversarial verdict on code or candidates is needed, or when the user names the setup (Fable as judge, Opus as executor, "model roles", "fable giudice", "opus esecutore", "solo opus", "senza fable"). Encodes the standing division of labour in both variants, with and without a Fable-capable account.