Skip to content

Yila-AI/awesome-defensive-writing / skills/yila-clear-writing

yila-clear-writing

Verified

Diagnose and revise AI defensive padding in drafts, reports, emails, research prose and public explanations when the user requests less hedging or clearer claims. Preserve evidence strength and meaningful reader guidance.

references/product-en.md

View on GitHub
# Product writing

**English** | [简体中文](product-zh.md)

Choose a task, copy a prompt and add your material. Follow the case link for supplied facts, a revision and the reasoning behind it.

## DW-031 · Feature description

Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.

Task: State what eligible users can do, then steps and conditions. Use verified
capabilities and retain access, pricing, formats and beta scope without
unverified quality promises.

Output: One sentence describing the user capability, followed by actions and
necessary conditions.

Input material:
Verified feature: [fill in]
Eligible users: [fill in]
Conditions: [fill in]
Placement: [fill in]

Related case: EX-11 in examples-en.md

## DW-032 · Release notes

Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.

Task: Separate released, beta and planned changes. Describe user-visible behavior,
retaining breaking changes and migration steps instead of vague upgrade
claims.

Output: Release notes grouped by availability, with required migration actions.

Input material:
Changes: [fill in]
Release status: [fill in]
Impact: [fill in]
Migration steps: [fill in]

Related case: EX-11 in examples-en.md

## DW-033 · Product comparison

Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.

Task: Compare the same task under consistent conditions and dates. Report
verifiable differences and unknowns; avoid fabricated competitor claims or
unfair setups.

Output: A like-for-like comparison, a use-case choice and missing information.

Input material:
Products: [fill in]
Task: [fill in]
Comparable facts: [fill in]
Date: [fill in]

Related case: EX-22 in examples-en.md

## DW-034 · Direct FAQ answer

Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.

Task: Answer the specific question first, then conditions and actions. Identify
unknowns rather than evading with generic disclaimers; retain material costs
and deletion consequences.

Output: The direct answer first, followed by conditions and next steps.

Input material:
Question: [fill in]
Confirmed rules: [fill in]
Instructions: [fill in]

Related case: EX-24 in examples-en.md

## DW-035 · Landing-page value

Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.

Task: Connect features to users and concrete tasks with verifiable value. Remove
empty value language without inventing efficiency gains, guarantees or
endorsements.

Output: A headline, subheadline and three supported value points.

Input material:
Audience: [fill in]
Task: [fill in]
Feature: [fill in]
Evidence: [fill in]

Related case: EX-12 in examples-en.md

## DW-036 · Customer case study

Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.

Task: Distinguish quotes, verified process and outcome data. Avoid unsupported
attribution and universal results; use approved anonymization for identities
without permission.

Output: A case narrative with the authorized quote, actual workflow, recorded result
and measurement definition.

Input material:
Permission: [fill in]
Quotes: [fill in]
Process: [fill in]
Measurement definition: [fill in]

Related case: EX-12 in examples-en.md
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall