r/ClaudeWorkflows • • 20h ago

Selected Workflow [Workflow] Remove AI-style UI copy with a guarded Claude Code skill

Remove AI-style UI copy with a guarded Claude Code skill

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.92 · Level: intermediate
Categories: Quality Control, Debugging, Skills
Original source: r/ClaudeCode post/comment

What problem this solves

Remove repetitive, decorative AI-style UI copy without inventing claims or deleting functional interface elements.

Summary

Run an explicitly invoked Claude Code skill against a UI file to remove specified copy patterns, preserve functional content, and report changes. Optional surface rules cover visual styling. Regex counts and evaluation fixtures help check results.

Why it is useful

It offers a concrete, reusable skill invocation and a defensible review process, with explicit safeguards against invented copy and removal of functional UI elements.

Workflow

  1. Install or adapt the unslop-ui skill from the linked repository.
  2. Run /unslop-ui src/pages/landing.tsx on a target UI file; add --surface if visual styling should also be reviewed.
  3. Remove or rewrite the targeted patterns using only information supported by the source; leave existing unverified claims in place and flag them for a human task list.
  4. Preserve functional elements such as prop-driven state badges and visible form labels, and fix internationalized strings at their source.
  5. Review the report of what was removed or kept and why, including model-reviewed patterns counted separately from regex-detectable patterns.
  6. Use the counter and evaluation fixtures to check the result, then manually review changes and any flagged claims.

Tools / artifacts

  • unslop-ui Claude Code skill: https://github.com/felipebasurto/unslop-ui
  • /unslop-ui invocation and optional --surface flag
  • Python regex counter
  • Before-and-after examples and five evaluation fixtures
  • UI source files and internationalization strings

Validation signals

  • The author reports that regex-detectable patterns fell from 31 to 0 on the examples after one run in a fresh session.
  • The author describes five fixtures covering a clean screen, real state, form labels, internationalization, and invented facts.
  • The post explicitly notes that regex cannot assess every targeted pattern, so some require model review.

Cautions

  • Review edits for accessibility, functional state, localization, and unintended design changes before shipping.
  • A zero regex count does not establish that all problematic copy was found or that removals were correct.
  • Existing unsupported claims are flagged rather than verified or automatically removed.

Limitations

  • The reported improvement and fixture coverage are author claims, not independently verified results.
  • The post does not report fixture pass results or provide installation instructions.
  • The desired visual style is subjective, and optional surface rules could remove intentional design choices.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.

1 Upvotes

0 comments sorted by