dude-with-sign-writer
Creates punchy, conversational one-liners in "Dude With Sign" style - bold statements that challenge norms, validate feelings, or poke fun at everyday truths. Use when creating short social captions, easel reveal messages, or single-sentence hooks. Not for long-form content or formal messaging.
What this skill does
# Dude With Sign One-Liner Writer Creates bold, conversational one-liners that stop scrolling. These are punchy statements designed for maximum shareability - not polished essays. **Voice:** Confident, direct, slightly irreverent. Like texting a friend who tells it like it is. **Not for:** Professional communications, long captions, formal announcements, anything requiring nuance or disclaimers. --- ## The 12 Core Patterns ### 1. Normalize Statements **Format:** "Normalize [behavior/thing people feel guilty about]" Challenges social pressure, gives permission. **Examples:** - "Normalize going to the movies alone" - "Normalize Irish exit" - "Normalize taking your lunch break away from your desk" **When to use:** Validating something your audience does but feels judged for. --- ### 2. Stop + Complaint **Format:** "Stop [annoying behavior everyone experiences]" Direct command. No explanation needed. The complaint IS the hook. **Examples:** - "Stop showing sold-out items on your website" - "Stop making burgers wider, not taller" - "Stop scheduling meetings that could be emails" **When to use:** Calling out universal frustrations. Works best when it's petty but relatable. --- ### 3. Everyday Observations **Format:** "[Simple truth no one says out loud]" Observational comedy meets social commentary. No command, just stating facts. **Examples:** - "January is the Monday of the year" - "Finding something to watch shouldn't take longer than watching it" - "Your inbox isn't a to-do list" **When to use:** When you want to sound smart without being preachy. --- ### 4. Relationship & Social Rules **Format:** "[Relationship expectation/boundary stated as law]" Universal agreements about how people should behave. Works for friendships, dating, work. **Examples:** - "If we start a show together, you don't get to watch episodes without me" - "If she says she's not hungry, get her extra food anyway" - "If you're gonna vent, don't get mad when I offer solutions" **When to use:** Creating solidarity around unspoken social contracts. --- ### 5. Pop Culture Commentary **Format:** "[Take on pop culture that connects to your topic]" Reference something trending, make it relevant to your message. **Examples:** - "Jolene, home wrecking" - "Not everything is an era" - "Your morning routine is not a personality" **When to use:** When you can hijack a cultural moment for your message. --- ### 6. Mock Instructions / Petty Commands **Format:** "[Absurdly specific instruction]" Like a PSA but sassier. Targets niche frustrations. **Examples:** - "The concert is over, take off your wristband" - "Empty liquor bottles are not home decor" - "Reply to emails on the same day, not same week" **When to use:** When the complaint is so specific it becomes funny. --- ### 7. Wordplay & Puns **Format:** "[Play on words that makes your point]" Language twist that's clever without being groan-worthy. Keep it tight. **Examples:** - "A dozen roses is less than a dozen rosés" - "It's supposedly not supposubly" - "Espresso yourself" **When to use:** When you have a genuinely good pun. Bad puns damage credibility. --- ### 8. Existential / Rhetorical Questions **Format:** "[Question that makes people think]" Not expecting an answer. The question IS the point. **Examples:** - "How do y'all keep plants alive?" - "WTF are y'all running from?" - "Why does 5pm feel like an eternity on Friday?" **When to use:** Pointing out absurdity without stating it directly. --- ### 9. Aspirational / Motivational **Format:** "[Permission or encouragement to do the thing]" Positive spin. Less sarcastic, more empowering. **Examples:** - "This is your sign to do that thing you've been wanting to do" - "To me, you are perfect" - "Your side project deserves your main character energy" **When to use:** When you want to inspire action, not just complain. --- ### 10. Calendar & Time Commentary **Format:** "[Observation about time/seasons/schedules]" Everyone relates to calendar weirdness. Universal truth about timing. **Examples:** - "February 29th should be a holiday" - "Next weekend means the weekend after this one coming up" - "Sunday night dread shouldn't be a thing" **When to use:** Seasonal content or pushing back on arbitrary schedules. --- ### 11. Everyday Struggles & Complaints **Format:** "[Small struggle stated dramatically]" Over-the-top about something minor. Self-deprecating but relatable. **Examples:** - "My tummy hurts, but I'm being brave about it" - "You're not going to wake up early to finish packing" - "I need a vacation from my vacation" **When to use:** When you want to be vulnerable and funny at the same time. --- ### 12. Values & Bigger Themes **Format:** "[Core belief stated simply]" Philosophical but still punchy. Your worldview in one line. **Examples:** - "Talking shit together is a love language" - "Earth Day is greater than every day" - "Work smarter, not longer" **When to use:** When you need to state your position clearly without being preachy. --- ## The Writing Process ### Step 1: Pick Your Pattern Don't overthink. Choose based on: - **Normalize** = Validating something taboo - **Stop** = Universal complaint - **Observation** = Stating the obvious cleverly - **Rules** = Setting boundaries - **Pop Culture** = Hijacking a moment - **Commands** = Petty but specific - **Wordplay** = You have a good pun - **Questions** = Pointing out absurdity - **Aspirational** = Positive motivation - **Calendar** = Time-based complaint - **Struggles** = Relatable vulnerability - **Values** = Core belief ### Step 2: Write It Conversationally Type like you're texting. Short sentences. Fragments okay. Read it out loud. **Test:** - Would you actually say this to a friend? - Is it under 15 words? (ideal: 5-10) - Does it sound natural, not "written"? ### Step 3: Make It Specific Vague = forgettable. Specific = shareable. Bad: "Stop being annoying at concerts" Good: "The concert is over, take off your wristband" Bad: "Working too much is bad" Good: "Your out-of-office should actually be out of office" ### Step 4: Remove Unnecessary Words Every word must earn its place. Cut ruthlessly. **Before:** "I really think we should normalize the idea of going to the movies by yourself" **After:** "Normalize going to the movies alone" **Before:** "Can we please stop scheduling so many unnecessary meetings?" **After:** "Stop scheduling meetings that could be emails" ### Step 5: Add Edge (Optional) If it feels too safe, add a little bite. But don't force it. **Safe:** "Taking breaks is okay" **Edge:** "Your hustle culture is someone else's burnout story" **Safe:** "Boundaries are important" **Edge:** "No is a complete sentence" --- ## Adapting for Your Brand When using this skill for your brand: ### Define Your Voice - What's your brand's attitude? (Snarky? Empowering? Irreverent?) - What are you challenging? (Status quo? Industry norms? Assumptions?) - What are you validating? (Your audience's feelings? Their choices?) ### Suggested Tone Balance: - 40% snarky commentary (the edge) - 30% validation/permission (the heart) - 20% truth-telling (the insight) - 10% brand-specific wordplay (the signature) ### Topic Clusters Identify 5-7 topics your audience cares about deeply: - Universal frustrations in your industry - Myths you want to bust - Behaviors you want to normalize - Values you stand for ### The McDonald's Test (Always) Would someone working at McDonald's understand this instantly? Bad: "Normalize asynchronous communication modalities" Good: "Normalize replying tomorrow" Bad: "Implement iterative feedback loops" Good: "Stop waiting for perfect. Ship it." --- ## Quality Checklist Before finalizing, check: - [ ] **Under 15 words?** (Ideal: 5-10) - [ ] **Conversational?** (Would you text this?) - [ ] **Specific?** (Not vague generalities) - [ ] **Immediately understandable?** (McDonald's Test) - [ ] **Pattern clear?** (Fits one of the 12) -
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.