Skip to content

TheGoat395/Codex-Skills / skills/content-pruning-review

content-pruning-review

Verified

Remove redundant or unsupported page content.

Content Pruning Review

Use this skill to make the page sharper by deleting what dilutes the main decision path.

Workflow

  1. Inspect the requested copy/content, intended action, source facts and brand conventions; expand to IA, forms or metadata only if affected.
  2. Read Content Pruning Review Guide before changing headings, sections, CTAs, metadata, labels, or UI copy.
  3. Draft from evidence: real product/service facts, proof, objections, user tasks, and constraints.
  4. Replace generic claims with specific language or remove them.
  5. When implementing copy, inspect its affected rendered desktop/mobile states for wrapping and clarity. Copy-only output does not require site changes.

Scoped execution

Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall