Drafting, editing, tone and plain-language rewrites. 67 reviewed prompts for writing.
Generates a range of accurate, attention-earning titles for an article, post or report, each in a different style, with a recommended pick. Use it when your draft is done but the headline is not.
Standing rules for writing and revising technical or business prose so it is specific, plain and honest about certainty. Use when drafting or editing documentation, reports, specs, release notes or explanations.
Expands a bare list of steps for a software feature into a clear, friendly how-to article with screenshot placeholders and troubleshooting tips. Use it for help-center pages and customer guides.
Writes three distinct versions of a networking profile About section from your real background and goal, with notes on who each style suits. Use when you update your profile or start a job search.
A way of working for reviewing copy for exclusionary wording, blaming tone and clarity barriers. Use when polishing product text, emails, help articles or announcements.
Turns your own notes or chapter text into a structured book summary with main ideas, key takeaways and open questions. Use it to review a book for study, book club or a team reading list.
Edits drafts so they read as if a person wrote them: cuts filler, stock phrases and mechanical rhythm while keeping every fact. Use when writing or revising any prose meant for human readers.
Writes an honest first-person story explaining why you maintain open source work and how sponsorship would sustain it. Use it for a sponsor profile, grant application or funding page.
Reviews documentation for errors, unclear wording, broken references and inconsistent terms, with a reason for each fix. Use it before publishing guides, READMEs or help pages.
Strips stray symbols, decorative borders, duplicate lines and leftover markup from pasted text while keeping the wording and structure intact. Use on text copied from chats, terminals or exports.
Drafts or rebuilds one section of a research paper from your claim, evidence and limits, with calibrated wording, an argument map and marked gaps. Use it when writing or revising a journal manuscript.
Creates a documentation strategy for a software product or API: audiences, information architecture, priority gaps, workflow, style rules, and success metrics. Use when launching docs, overhauling messy docs, or scaling a docs team.
