← ClaudeAtlas

deailisted

Keep a product and its codebase from reading as AI-made. Audits an existing app, website, landing page, README, UI copy, or repo for "AI smell" (em dashes, cliche copy, purple gradients, default favicons, fake stats, duplicated logic, dead code, narration comments, five different fetch patterns) and removes it without changing functionality. Also sets up project rules so new code gets built clean, systematic, and readable by other engineers. Use whenever the user says a product "looks AI-made", "feels like AI slop", or "looks vibe-coded"; wants to "humanize" or "de-AI" an app, site, copy, or code; asks why their site looks generic; wants a pre-launch polish pass; wants AI-written code cleaned up, deduplicated, or made maintainable; or is starting a new app/website/product and wants it built properly so it doesn't look or read like AI output.
parasvishwa/deai-skill · ★ 0 · Code & Development · score 67
Install: claude install-skill parasvishwa/deai-skill
# deAi: Remove the AI Smell From a Product and Its Code AI-built products get detected and distrusted, on two levels: - **Users see the surface.** A "Vite + React" tab title, a purple gradient, an "Oops! Something went wrong." Research shows labeling something "AI" lowers trust and purchase intent, and users read each tell as *nobody cared enough to look at this*. Once they spot one, they assume the rest is careless too, including how their data is handled. - **Engineers see the inside.** The same logic pasted into six files, abstractions nobody uses, comments narrating every line, and a different pattern in every file because each prompt started fresh. It runs, but nobody can maintain it. This skill handles both. It finds the tells, removes them **without changing functionality**, and installs project rules so new work comes out clean from the start. ## The two iron rules 1. **Never change functionality.** Behavior, routing, data flow, business logic, and public APIs stay exactly as they were. Renaming a button label is in scope; changing what the button does is not. Extracting an exact duplicate into a shared function is in scope; changing how errors propagate is not. Anything that would change behavior goes in the report as an Observation and is never implemented. 2. **Audit first, ask permission, then act.** Never edit a file before the user has seen the full issue list and approved what to change. The order is always **Audit → Present findings → Wait for approval →