プロンプト

A short announcement, detailed changelog and upgrade notes.

A rewritten text, key editorial changes and unresolved ambiguities.

Three rewrites, tone differences and a factual consistency check.

A revised translation, terminology suggestions, issue list and verification checklist.

A bilingual glossary, usage rules, examples and open questions.

A short summary, main claims, evidence structure and comprehension questions.

An agenda summary, decision log, action table and confirmation list.

A synopsis, scene list, script excerpt and production notes.

A character profile, relationship map, arc milestones and scene ideas.

An interview guide, feature outline, fact checks and missing material.

A reasoned edit list, revised draft and publication checklist.

Ten headlines, three openings, use cases and recommendation rationale.

Translates a business email and adapts it to the recipient's business culture (directness, formality, greetings, sign-offs), noting each adjustment. For professionals writing across languages.

Translates SRT or VTT subtitles keeping timing and numbering, respecting reading speed and line limits, condensing where needed and flagging puns and cultural references.

Translates a research abstract, title and keywords in the field's established terms, keeps hedging and statistics exact, follows journal conventions and lists term choices to confirm.

Translates a technical manual section or work instruction with consistent terminology, short controlled sentences, safety messages in standard signal-word form, and units and part numbers kept exact.

Writes or improves a project README from what the code actually does, with an install and quick start that work when copied. Use for a new project or a README that has drifted.

Writes an architecture overview of an existing system from its code and notes, covering context, components, boundaries, key decisions and trade-offs, with diagrams and short decision records.

Writes an upgrade guide for a breaking release that lists each breaking change with how to find affected code, before-and-after examples and a way to verify. Use when shipping a major version.

Writes a troubleshooting guide organised by symptom, with likely causes in order, diagnostic commands, fixes and when to escalate, from support tickets or issue threads.

Outlines a nonfiction book with a reader promise, a thesis, a chosen structure, chapter-by-chapter summaries with claims, evidence and stories, an overlap check and a list of research gaps.

Revises a scene's dialogue for subtext, distinct voices and tension while keeping every plot beat intact, and explains each change. Use when dialogue reads stiff or expository.

Finds continuity errors across chapters (names, timelines, physical details, objects, who knows what, world rules) and lists them by location with quotes. Use before beta readers or submission.

Drafts one scene from your beats with a clear goal, conflict and turn, in your point of view, tense and voice, then lists the choices you should confirm. Use when you know what happens but not how.