AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Miniapp User Facing Copy Trim

skill-sun-sunshine06-miniprogram-skills-miniapp-user-facing-copy-trim · by Sun-sunshine06

Simplify on-page WeChat Mini Program copy so main surfaces become shorter, more action-first, and more user-facing. Use when Codex needs to trim verbose labels, mixed implementation detail, over-explained settings, or long empty-state and status text without changing the underlying business flow.

↗ Repository
— No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-sun-sunshine06-miniprogram-skills-miniapp-user-facing-copy-trim

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Miniapp User Facing Copy Trim? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Miniapp User Facing Copy Trim

Overview

Use this skill when the structure and interaction model are mostly acceptable, but the page sounds like internal documentation instead of a product surface. The goal is to keep only the copy users need in the moment.

Quick Start

  1. Read references/copy-trim-playbook.md.
  2. Inventory the longest labels, subtitles, empty states, banners, and toasts on the target surfaces.
  3. Classify each text block as keep, shorten, move, or delete.
  4. Replace explanation-heavy paragraphs with concise labels, summaries, and status text.
  5. If the real blocker is page ownership or navigation, use miniapp-center-hub-refactor instead.

Core Rules

  • Main surfaces should answer:
  • what can I do here
  • what is the current state
  • what is blocking me
  • Prefer one strong label plus one short supporting line over a paragraph.
  • Remove implementation detail from user copy unless the user must act on it directly.
  • Keep terminology consistent across page titles, section labels, buttons, banners, and toasts.
  • Prefer concrete verbs over abstract management nouns.
  • Keep mixed-language copy intentional:
  • preserve proper nouns or official platform names when needed
  • avoid mixing two languages inside the same short label unless the product requires it
  • Move maintainer explanation, technical caveats, and long rationale into docs, help surfaces, or detailed pages.
  • Validate copy at small-surface level: tab text, title, button, chip, empty state, error banner, and toast.

Output Format

  1. high-friction copy to cut
  2. replacement labels and summaries
  3. what to move out of the page
  4. copy validation pass

Resources

  • references/copy-trim-playbook.md: rewrite patterns, bilingual guidance, and review checklist
  • references/example-prompts.md: reusable trigger and non-trigger prompts

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills