slurpyb/writing
Writing and content-craft toolkit: draft long-form articles and guides in a distinctive voice (article-writing), develop personal/analytical essays (developing-essays), write and audit persuasive marketing copy (persuasive-copywriting), learn and reproduce a writer's voice from exemplars (style-learner), shape raw material into articles conversationally or beat-by-beat (writing-shape, writing-beats), mine and collect raw fragments before structuring (writing-fragments), apply Strunk's rules for clear concise prose (writing-clearly-and-concisely), strip AI tells from text (writing-humanizer), extract the functional DNA and trope maps from source works for adaptation (dna-extraction), and build a DDD-style ubiquitous-language glossary (ubiquitous-language).
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
Methodology for developing personal statements and analytical essays. Use when helping identify throughlines, resolve "too many ideas" paralysis, or clarify essay themes.
Extract the functional DNA from existing works (TV, film, books, plays). Use when adapting a source work, when analyzing what makes something work, when creating trope maps for reuse, or when you need to separate structural necessity from stylistic choice.
Build hands-on, code-first tutorials from any primary source - technical documentation, codebases, APIs, tools, or other complex material. Extract real examples, working code, and concrete scenarios. Create tutorials using markdown (text-heavy summaries) or React artifacts (complex interactive workflows). Keywords - tutorial, codebase, API, hands-on, code-first, copy-paste, interactive, real examples, primary source
Use when writing something public-facing about this project's engineering. A release announcement, a how-we-built-X deep-dive, a retrospective. Not tied to a release event, and not the mechanical changelog (that's changeset-writing's job).
Create, configure, build, and deploy documentation books with mdBook (Rust Markdown book generator). Use when: (1) starting/structuring an mdBook book (SUMMARY.md, chapters, parts), (2) configuring book.toml (themes, search, playground, renderers, preprocessors), (3) using mdBook markdown features (file includes, anchors, runnable Rust, admonitions, hidelines), (4) running the mdbook CLI (init/build/serve/test), (5) setting up CI/CD deployment to GitHub Pages, or (6) writing custom preprocessors/backends.
Write, audit, and analyze persuasive marketing copy using an evidence-based tactics library (framing, scarcity, social proof, CTAs, numeric framing), sentence craft (AIDCA structure, benefits-vs-features, power words, readability gates), and a linguistics-of-voice toolkit (stance/appraisal vocabulary, five-layer Voice DNA model, marker lexicons). Use when: (1) writing or improving landing pages, product descriptions, CTAs, emails, headlines, or ad copy; (2) auditing/critiquing copy — detecting buzzwords/AI-slop, weak framing, hedging, or poor readability and proposing fixes; (3) characterizing or reproducing a writer's voice; (4) researching a product's competitive landscape and adapting copy to win in it (pairs with firecrawl-shop). Triggers: "write copy", "make this more persuasive", "improve this CTA/headline", "critique this copy", "is this on-brand", "match this voice", "does this sound like AI".
Learn and extract writing style patterns from exemplar text for consistent application. Use when creating a style guide from existing content, ensuring consistency across documents, learning a specific author's voice, customizing /AI output style. Do not use when detecting AI slop - use slop-detector instead. just need to clean up existing content - use doc-generator with --remediate. Use this skill to build style profiles from exemplar text.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
Write or revise prose for humans. Use for documentation, code comments and API references in any language, UI and error text, reports, explanations, and project communication. Preserve exact meaning while replacing vague, metaphorical, anthropomorphic, hedged, or inflated language with literal statements.
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.