Software how-to guide from basic steps
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.
Drafting, editing, tone and plain-language rewrites. 60 reviewed prompts for writing.
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.
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.
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.
Corrects spelling, grammar and punctuation in your text while keeping your voice, and shows what was changed and why. Use before sending, publishing or submitting any text.
Turns your real numbers and stories into a clear, credible impact section for a page, report or funding update. Use it when you need to show what a project achieved.
Drafts a clear email from your context, purpose and tone, with a subject line and an optional shorter version. Use for requests, follow-ups, apologies, announcements and replies.
Gives a writer focused coaching on a story or chapter: what works, the biggest craft issues, and targeted exercises, while keeping the writer's own voice. Use for fiction, memoir, or scripts in progress.