aihxp

De-slop AI-sounding prose and rewrite a draft so it reads as genuinely human, and when a writer's voice sample or style profile is available, rewrite it in that author's actual voice instead of generic neutral prose. Removes the recurring generative-AI tells: inflated significance, delve/landscape/tapestry vocabulary, rule-of-three padding, em dash overuse, negative parallelisms, sycophantic hedging, signposting, formulaic conclusions, and listicle scaffolding, while preserving meaning and the markers of real human writing. Use this whenever a user wants to humanize, de-AI, de-slop, or de-robotify text; to fix writing that sounds like ChatGPT or a machine; to make a draft sound like them or like a named author; or to edit prose for authentic voice and rhythm. Reach for it even when the user only says the text feels off, sounds corporate, reads like AI, or is too generic, without naming this skill or the word humanize.

Take a software project from raw idea through PRD, architecture, roadmap, stack pick, repo scaffolding, application build, deploy pipeline, observability, launch, and adversarial hardening. The full arc, mechanically enforced, in one skill. Triggers on 'kickoff,' 'I have an idea,' 'walk me through idea to launch,' 'orchestrate the whole arc,' 'help me ship it end-to-end,' 'new project from scratch,' 'write a PRD,' 'product spec,' 'design the architecture,' 'system design,' 'monolith or microservices,' 'C4 diagram,' 'ADR,' 'build a roadmap,' 'milestone plan,' 'quarterly plan,' 'sequence the work,' 'Now-Next-Later,' 'Shape Up cycle,' 'what stack should I use,' 'pick a database,' 'which framework,' 'set up a repo,' 'add CI,' 'GitHub Actions,' 'configure linting,' 'add a README,' 'adopt Pillars,' 'task-routed agent memory,' 'dashboard,' 'admin panel,' 'internal tool,' 'back office,' 'CRUD app,' 'deploy this,' 'CI/CD pipeline,' 'promote to staging,' 'zero-downtime migration,' 'expand-contract,' 'rollback,' 'canary

Score how authentically a piece of text reads as the work of a real human author, and flag the specific spans that read as AI-generated, AI-templated, or generically derivative. This is a diagnostic: it returns an authenticity band, a 0-100 score, and span-level flags with reasons. It never rewrites, edits, or "fixes" the prose; rewriting is the humanizer skill's job, and the split is deliberate. Use this whenever a user wants to know if text is authentic, whether a draft reads like AI or like a bot, how human a passage sounds, which parts sound machine-written, or whether their own draft still sounds like them. Reach for it on evaluative cues like "is this AI," "does this read like a person," "rate the AI-ness of this," "score how human this is," "audit this for AI tells," or "check if this still sounds like my voice," even when the user does not name this skill. Do not trigger this skill on transformative requests (humanize, de-slop, de-AI, rewrite, fix, make it sound like X); those belong to the separate h

A test skill with security issues

Generate a "DNA profile" of a codebase's coding style (naming conventions, formatting, comment voice, structural habits, error-handling philosophy, and idioms), then use it so new or AI-written code is indistinguishable from the existing author's code. Use this skill whenever the user wants to match a codebase's existing style, make AI contributions "blend in", "mimic" or "fingerprint" a coding style, capture house conventions, build a style guide from existing code, onboard to an unfamiliar repo's conventions, or check whether code "looks AI-generated" / has tells. Triggers on phrases like "match my coding style", "make it look like I wrote it", "codedna", "capture the conventions", "style guide from the code", "why does this read as AI-generated", "genetic map of the code", "mimic the codebase", and on any request to contribute significant code to an existing repo where matching house style matters.