Community: add bangers

Community/bangers/DISPLAY.json

@@ -0,0 +1,9 @@
+{
+  "specVersion": "0.2.0",
+  "icon": "megaphone",
+  "tags": [
+    "content",
+    "marketing",
+    "research"
+  ]
+}

Community/bangers/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: bangers
+description: >
+  Social-media content system. Use whenever the request is about making content: what to post,
+  content ideas, hooks, titles, thumbnails, YouTube or short-form video scripts, X/Bluesky threads,
+  LinkedIn or Substack or newsletter posts, Facebook Group posts, Instagram or LinkedIn carousels,
+  technical explainers and tutorials, video edit plans and captions, repurposing one source across
+  platforms, or checking whether a draft reads as AI-written and how to disclose AI use. Studies
+  public creator and platform mechanics and adapts them to the author's own audience and voice.
+homepage: https://github.com/Jeff-Kazzee/bangers
+license: MIT
+metadata:
+  author: Jeff Kazzee
+  generated: scripts/build-zo-skill.mjs
+  source: https://github.com/Jeff-Kazzee/bangers
+  suite: bangers
+  version: "1.1.0"
+---
+
+# BANGERS
+
+A research-backed social-media content system. It studies public creator and
+platform behavior, extracts reusable mechanics, and turns real source material
+into native assets without copying anyone's voice.
+
+This is the Zo Computer build. Zo has no plugin system, so the twelve
+procedures live under `references/procedures/` instead of as separate skills.
+Load one procedure at a time. Do not read them all.
+
+## Router
+
+Pick one procedure, read it completely, then load only the references it names.
+
+| Request | Procedure |
+| --- | --- |
+| Research a creator, platform, format, or writing pattern | `references/procedures/banger-research.md` |
+| Ideas, angles, or a content calendar | `references/procedures/banger-ideas.md` |
+| Hooks, titles, thumbnails, or packaging | `references/procedures/banger-hooks.md` |
+| Technical explainer, tutorial, build log, or how-it-works teaching content | `references/procedures/banger-explainer.md` |
+| YouTube or long-form video script | `references/procedures/banger-script-longform.md` |
+| Short vertical script | `references/procedures/banger-script-shorts.md` |
+| X, Twitter, or Bluesky post or thread | `references/procedures/banger-threads.md` |
+| LinkedIn, Substack, newsletter, or Facebook Group post | `references/procedures/banger-longform-written.md` |
+| Instagram or LinkedIn carousel | `references/procedures/banger-carousels.md` |
+| Cut sheet, captions, markers, reframe, or recording plan | `references/procedures/banger-edit.md` |
+| One source adapted to several platforms | `references/procedures/banger-repurpose.md` |
+| AI detector check, authenticity verification, or AI-use disclosure | `references/procedures/banger-detector.md` |
+
+## Before drafting anything
+
+1. Start from a real source, observation, result, or a clearly named audience
+   question. Never invent proof, experience, metrics, quotes, or current
+   platform facts.
+2. Read `references/frameworks/voice-and-audience.md` to fix who is speaking
+   and who they are speaking to, then
+   `references/frameworks/writing-quality.md` for the failure list.
+3. When the piece teaches a mechanism the reader must repeat, also read
+   `references/frameworks/technical-clarity.md` and apply the frame/payload
+   split: the author's voice carries the hook, story, and judgment, while the
+   explanation takes one name per concept, one idea per sentence, and active
+   voice.
+
+## Suite rules
+
+1. Research updates need dated sources, observed examples, a confidence label,
+   and a reusable mechanic. One viral post does not establish a law. Treat any
+   platform claim without a current entry in
+   `references/research/source-ledger.md` as unverified and research it first.
+2. Borrow mechanics, not phrasing, identity, signature jokes, or an imitation
+   voice.
+3. Adapt every output to its native platform. Never paste identical copy
+   everywhere.
+4. Detector results are weak adversarial evidence. Never damage a true, clear
+   passage to move a score, and never claim output passes AI detection. Route
+   detector and disclosure work through
+   `references/procedures/banger-detector.md`.
+5. Keep private client, identity, health, financial, and unpublished business
+   context out of anything reusable.
+
+## Checking a draft
+
+The deterministic writing checker runs in the Zo terminal. It reads UTF-8 files
+and can enforce an author's em-dash ban:
+
+```
+node scripts/check-writing.mjs --no-em-dash draft.md
+```
+
+It prompts human review. It does not prove authorship or quality.
+
+## Output
+
+Lead with the strongest ready-to-use asset. Then give only the source
+assumptions, platform notes, and the approval needed next. Drafting is free.
+Publishing, scheduling, and outreach need the author's explicit per-item
+approval.
+
+## Credit
+
+Creator playbooks study public work by Fireship, Matt Pocock, Theo, and
+ThePrimeagen. The technical-clarity standard is adapted from ASD-STE100
+Simplified Technical English and Orwell's six rules, and reached this project
+through @geogristle, @Voxyz_ai, and @mikehostetler on X. Full credit in
+`references/frameworks/technical-clarity.md`.
+
+MIT licensed. Source and updates: https://github.com/Jeff-Kazzee/bangers

Community/bangers/references/creators/_synthesis.md

@@ -0,0 +1,32 @@
+# THE SYNTHESIS — What All Four Creators Share (the meta-playbook)
+The four reference creators look different but run the SAME underlying machine. When you produce anything in this suite, these are the shared laws. Pair with `voice-and-audience.md` to retarget them at YOUR audience.
+
+## 1. THE FIRST 3 SECONDS ARE THE WHOLE GAME
+All four kill the intro. Fireship: first word is the topic. Theo/Prime: open on the stakes/the spicy take. Pocock: the hook line IS a curiosity gap. No "hey guys," no throat-clearing, no channel bumper. **Lead with the payoff or the promise.** On every short-form platform the first 1–3 seconds decide distribution (swipe-away kills reach); on long-form the first 30 seconds decide retention.
+
+## 2. RIDE SOMETHING THAT'S ALREADY MOVING
+None of them start from a blank page every time. Fireship trend-jacks the week's news. Theo reacts to what happened. Prime reacts to a submitted article. Pocock answers real questions people are asking. **Borrow a skeleton with existing heat** (a trending AI tool, a viral demo, a question everyone has) and add your layer on top. The internet supplies infinite raw material; your reaction/teaching is the only original part.
+
+## 3. ONE THING, DENSELY
+Fireship = one idea per sentence, no filler. Pocock = one concept per post. Both refuse to waste the viewer's time. **Every sentence must add information OR a laugh — cut everything else.** For beginners, "dense" means no wasted words, not more concepts.
+
+## 4. A REAL OPINION / VERDICT (the value-add)
+Theo and Prime never just report — they tell you what to think and back it with lived experience, then leave you with a verdict ("here's what I'd actually do"). Pure reaction with no take is the failure mode. **Have a spine.** Be the trusted filter.
+
+## 5. SHOW, DON'T TELL
+Pocock reveals the invisible on screen (the type, the error, the result). Fireship shows real code being typed. Prime pulls the artifact up live. **Put the actual thing on screen** — the prompt and its output, the before/after, the real result — not a description of it.
+
+## 6. MANUFACTURE ENERGY / PERSONALITY
+Prime swings volume and engineers spikes. Theo brings "chat" energy. Fireship uses deadpan comedy. Pocock uses warm enthusiasm. The topic rotates; **YOU are the format.** Personality is what makes it un-clonable.
+
+## 7. BE CORRECTABLE + AUTHENTIC
+Theo publicly says "I was wrong." Prime self-deprecates ("I broke prod"). Pocock punctures his own guru status. **Confidence + humility = trust.** Anti-corporate, anti-gatekeeping, real.
+
+## 8. VOLUME VIA THE FUNNEL, NOT VIA MORE WORK
+Prime and Theo go long once, then shred one session into a video + many clips. Pocock and Fireship keep a fixed template so only the topic research is new. **Produce one rich source asset, then atomize it** (see the repurposing waterfall). Don't make ten things from scratch — make one thing and cut it ten ways.
+
+## 9. PACKAGING > EVERYTHING
+Theo: "obsess over whether the packaging makes it worth clicking." Fireship's titles/thumbnails are engineered. **The title + thumbnail (or first line + first frame) is a separate craft from the content** — and often decides whether the content is ever seen. Plan it before you make the thing.
+
+## 10. CLARITY IS THE MOAT
+"What sets them apart isn't editing skills — it's their writing and unique perspective." The tools are commodities; **the clear explanation and the real point of view are the product.**

Community/bangers/references/creators/fireship.md

@@ -0,0 +1,36 @@
+# FIRESHIP — Maximum-Density + Deadpan-Comedy Playbook
+
+> Jeff Delaney (Fireship). Thesis: **max information density + deadpan self-aware comedy + zero dead air + cheap-but-precise visuals**, riding whatever's hot this week. The video is "already sped up — you have to slow it down to keep up." **Adapt it:** keep the density, pacing, humor, and visual discipline — but calibrate concept count to YOUR audience. Density = "no wasted words," NOT "more concepts." If your audience is less expert than his (developers who already code), cut concept count, keep the tightness, and don't skip fundamentals; if your audience is expert, you can compress harder.
+
+## Two engines
+Evergreen "**X in 100 Seconds**" (timeless intros) + trend-jacking "**The Code Report**" ("CNN for software" — breaking news framing). Blend timeless + reactive for compounding growth. The TEMPLATE never changes, only the topic — that's what enables rapid cadence.
+
+## The hook (first word is the topic — NEVER a greeting)
+No "hey guys," no face-cam, no bumper, no "in this video," no "so." The clock starts on information at word one.
+- **Definition-first:** "[Topic] — a [category] for [doing X], built by [who], released in [year]." ("React — a JavaScript library for building user interfaces, developed at Facebook and released in 2013.")
+- **Problem-provocation:** name the pain as a jab, then present the fix.
+- **Spicy claim (news):** open on the most dramatic-but-true framing, deadpan.
+Copy templates: "[X] — the [tool] that finally [solves annoying problem]." / "Yesterday, [company] did something that [breaks/ends] [thing everyone assumed]." / "There are [N] ways to [do X]. Most are wrong. Here's the one that isn't." / "You've been [doing thing] wrong your entire life. In [N] seconds I'll fix that."
+
+## Density: the no-filler law (the core mechanic)
+Physically produced by: **voiceover recorded sentence-by-sentence**, then razored together so every pause/um/gap is cut → wall-to-wall narration, zero dead air. **Every on-screen asset lives 1–5 seconds** then cuts. One new idea per sentence, chained not nested, never re-explained. Compress with "just / basically / literally" ("it's just a function") then move on.
+DENSITY CHECKLIST: first word = topic; zero dead air; no sentence survives that doesn't add info OR a laugh; visual changes every 1–5s; one new idea per sentence; audio quality non-negotiable ("low quality audio is the quickest way to drop a viewer"); one-line sign-off, no begging outro.
+
+## Script skeletons
+**"X in 100 Seconds"** (~100–140s, 250–350 words): (1) definition hook → (2) the problem it solves + jab → (3) origin (optional) → (4) core mechanism / "it's just a ___" + smallest real example → (5) hands-on micro-demo → (6) the catch / why you'd actually use it → (7) one-line sign-off. Arc: concrete → deeper → caveat → out.
+**"The Code Report" / news:** (1) title card + date, black bg, breaking-news framing → (2) spiciest lede → (3) 2–3 compressed context sentences → (4) rapid takes + roast → (5) one genuinely useful technical payload → (6) deadpan anticlimactic verdict → (7) sign-off.
+
+## Humor & voice
+Deadpan, dry, ironic, self-aware; never laughs at its own jokes; jokes buried inside informative sentences so they reward attention. Devices: self-deprecation ("the personality of a carrot"), roasting industry churn ("every week there's a new JavaScript framework"), rename bits ("they call it a [X], but it's really just a [blunt name]"), meme cutaways timed to the punch word (no face → the meme carries the joke), deadpan over/understatement ("developers are not okay"), meta fourth-wall breaks, ironic flat subscribe ask. Put the joke ON the informative sentence, not in a separate bit.
+
+## Visuals & editing (cheap but precise)
+Minimalist black background, code/subject front-and-center, dense text overlays, emojis/memes timed to the syllable, punchy SFX on cuts. Signature tricks: the **reverse-delete reveal** (write finished code, delete in reverse while recording undo so it re-inserts line-by-line synced to narration — adapt it: the same trick works for revealing any text/UI step-by-step, whatever your subject), emoji/arrow/freeze-frame pointers on the exact line being discussed (a paused viewer always knows the context), jump-cut everything, motion-graphic transitions between beats. Tools: Premiere (edit + VO assembly), After Effects (animation), Figma (graphics), Videohive (transitions), Unsplash/Pexels (stock), Giphy (memes), sub-$100 USB condenser mic. **The polish is writing + editing discipline, not gear.**
+
+## Titles & thumbnails
+"[Topic] in 100 Seconds" (ownable, searchable, promises brevity). "I tried [N] [things]" / "[N] things in [N] minutes" (finite promise). Hot-take titles with the exact buzzword people are searching. Rules: put the searched term in the title; make a concrete finite promise (number/time/verdict); bait mild curiosity, never "Let's learn X." Thumbnail: high-contrast, dark bg, big logo(s), short punchy label, occasional emoji reaction, reads instantly at small size, one clear idea.
+
+## Topic selection (ride the hype cycle)
+Two-track: evergreen (long-tail search) + reactive (news spikes). Surf the peak FAST — biggest wins come from moving immediately at max interest (ChatGPT launch coverage ≈16.9M views). Pick what the audience already argues about. Own a narrow lane. Format reusable, topic fresh.
+
+## THE 10 RULES OF FIRESHIP DNA
+1. First word is the topic — no greeting ever. 2. Zero dead air. 3. Skip everything your audience doesn't need — but if you teach beginners, don't skip fundamentals. 4. One new idea per sentence; delete repeats. 5. Trivialize with "just," then move on. 6. Deadpan, never laugh at your own joke. 7. Roast the industry/yourself, don't hype earnestly. 8. Visual change every 1–5s; reveal step-by-step; pointer on the live line. 9. Cheap assets + precise timing = "expensive" feel. 10. Ride the week's hottest topic through an unchanging template; one flat sign-off.

Community/bangers/references/creators/matt-pocock.md

@@ -0,0 +1,47 @@
+# MATT POCOCK — Teach-One-Thing / Show-Don't-Tell Playbook
+
+> Matt Pocock (@mattpocockuk, Total TypeScript). Ex-singing teacher → "the TypeScript guy." His edge is PEDAGOGY, not genius: "I could explain things a lot better." Grew via VOLUME of tiny high-frequency free content, not one viral hit. **Adapt it:** swap "advanced TypeScript" for YOUR topic (e.g. AI tools for beginners, fitness, personal finance) — the one-concept-per-post, make-the-invisible-visible teaching method works in any niche.
+
+## Signature format: ONE concept, shown not told
+Atomic unit = a single insight, demonstrated visually, that makes people go 🤯. Skeleton of a tip post:
+1. **Hook line** — a curiosity gap or promise.
+2. **The demo** — a screenshot/clip showing the problem or setup.
+3. **The reveal** — the ONE trick, shown happening (not described).
+4. **One-line "why this matters"** — the payoff sentence.
+5. (Optional) CTA/bridge.
+
+## The one-concept discipline
+Each post solves EXACTLY one problem. **Example-first, not concept-first** — show the situation before naming the abstraction; the learner feels the problem, then gets the tool. The insight must feel like a GIFT, not a lecture ("here's a thing that'll make your life better"). **Isolation test:** if you can't state the takeaway in one sentence, it's not one concept — split it. Titles are tightly scoped, complete, actionable verb-phrases.
+
+## Hook patterns (curiosity gap + specificity + a number)
+- `There are [N] ways to [do thing]. I bet you don't know [2 or 3] of them.`
+- `Here are [N] [things] you HAVE to know about.`
+- `This [thing] will wreck your [outcome].`
+- `The [feature] they didn't tell you about.`
+- `Don't use [popular thing]. Here's what to do instead.`
+- `What does this do? 🤔` (quiz — reveal answer below)
+- `I guarantee if you [do X], you'll [aspirational result].`
+Rules: put a NUMBER in it when you can. Name the reader's pain/aspiration in the first 7 words. Create a gap the demo closes — never give the answer in the hook. Mild stakes ("will wreck," "you HAVE to") but the payoff must always deliver — no clickbait debt.
+
+## Visual style: make the invisible visible
+The killer move — surface what's normally hidden right in the shot (adapt it to your subject: show the actual output, the input→result, the before/after, the setting most people never find). Every screenshot should contain a REVEAL — the thing you can't see in plain text. Short, no-cut screen recordings (<2 min, one take, real screen) were his growth engine. The mistake/error IS the drama: show the broken version, then the fix. The "aha" must be locatable in one glance (arrow/highlight the one thing).
+
+## Growth tactics (his own words)
+Volume + consistency of tiny content. Follow the response signal — watch which posts pop, make more of those. **Reply, reply, reply** — "if you reply, they just ask you more"; replies are the flywheel. Teach-by-answering — answer real questions = endless post ideas + authority. Own a niche until you ARE the niche. Free beginner content as the funnel. Repurpose one insight across X → thread → 2-min video → article → LinkedIn. Build EVERGREEN assets (a running "Ultimate ___ Thread" you keep adding to) that compound.
+
+## Voice/tone: warm, low-ego, "let me show you"
+"Hey, I'm Matt!" energy. Collaborative "let me show you," not "let me explain." Self-deprecating, punctures own guru status. Encouraging + aspirational — cast the reader as a future expert ("turn you into a wizard"). Plain language over jargon; earn advanced terms by grounding in an example first. Real, visible enthusiasm. Phrasings: "This one blew my mind." / "Don't worry if it looks scary — it's simpler than it looks." / "You're going to love this."
+
+## Translating hard → beginner (the scaffolding recipe)
+Concrete broken example → let them feel the pain → reveal the one fix → show the proof it works → name the concept LAST → one-sentence "now you can use this for ___." Also: problem→solve→solution loops; radical scoping (one concept, one sentence); "skim, don't study" permission to lower intimidation; the aspirational "wizard" frame that pulls beginners toward difficulty instead of away.
+
+## THE RULES CHECKLIST
+- [ ] One concept only (state takeaway in one sentence, or split).
+- [ ] Example first — show real/broken situation before the abstraction.
+- [ ] Hook has a curiosity gap; first 7 words name a pain/promise; answer NOT given away; number if possible.
+- [ ] The visual REVEALS the invisible; the "aha" is locatable in one glance.
+- [ ] Payoff delivers on the hook — no clickbait debt.
+- [ ] Reader cast as capable; tone warm + low-ego.
+- [ ] One-sentence "why this matters" closes it.
+- [ ] Repurposable (thread entry / 2-min video / article / LinkedIn) and cheap to produce.
+- [ ] Feeds an evergreen hub; you're ready to reply to every question it generates.