wize-dev-kit 0.18.0 → 0.20.0

package/ARCH.md

@@ -261,8 +261,8 @@ wize-dev-kit sync     # regera adapters IDE
 
 ### Wize App Development (overlay)
 
-- Workflows extras: `wize-app-scaffold` (RN/Expo/Flutter/native), `wize-app-release-channels`, `wize-app-store-listing`.
-- Artefatos extras: `mobile-store-listing.md`, `app-perms-and-privacy.md`, `release-channels.md`.
+- Workflows extras: `wize-app-scaffold` (RN/Expo/Flutter/native), `wize-app-release-channels`, `wize-app-store-listing`, `wize-app-store-review` (publication gate).
+- Artefatos extras: `mobile-store-listing.md`, `app-store-review-report.md`, `app-perms-and-privacy.md`, `release-channels.md`.
 - Hawkeye playbook: Detox/Maestro patterns.
 - Mantis playbook: HIG/Material 3, touch targets, gestures, permissions UX.
 

package/CHANGELOG.md

@@ -7,6 +7,18 @@ Format inspired by [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 > **0.10.0 and earlier are in Brazilian Portuguese** and are kept verbatim as a
 > historical record (not back-translated).
 
+## [0.20.0] — 2026-09-18
+
+### Added
+
+- **`wize-app-store-review`** (app overlay workflow) — the publication gate the app-overlay was missing. Hawkeye audits the app's code and metadata as an App Store reviewer **after** `wize-app-store-listing` and **before** prod go-live via `wize-app-release-channels`: top rejection risks first (permissions, privacy manifest, IAP/restore, sign-in compliance, metadata mismatch, minimum functionality), compliance checklist by area with conditional Guideline checks (1.2 UGC, 4.3(b) spam, 4.5.3 Apple services), fixed report structure (executive summary, risk register P0–P3, detailed findings, reviewer-experience checklist, suggested "App Review Notes" for App Store Connect), then a fix pass handed to Shuri. Gate rule: no prod submission while any P0/P1 is open (or the user documents a `WAIVED`). Adapted from [awesome-copilot's apple-appstore-reviewer](https://github.com/github/awesome-copilot/blob/main/skills/apple-appstore-reviewer/SKILL.md) (MIT, credited in the READMEs). New artifact: `.wize/planning/app/app-store-review-report.md` (also registered in `wize-help`/`wize` ship stages and `ARCH.md`).
+
+## [0.19.0] — 2026-09-18
+
+### Added
+
+- **`wize-no-ai-slop`** (core skill) — writing hygiene for end-user-facing prose, adapted from [no-ai-slop](https://github.com/petergyang/no-ai-slop) by Peter Yang (MIT, credited in the READMEs). Two jobs: apply while writing (17 AI-slop patterns to cut — binary contrasts, throat-clearing, faux-insight setups, importance puffery, weasel attribution, fake-profound kickers, formatting slop, etc. — plus banned filler words, voice preservation, portability test) and detect on request (name each pattern with a quoted line; no rewriting, no guessing AI authorship). Wired into Peggy Carter (`wize-agent-tech-writer`) and Mantis (`wize-agent-ux-designer`) agent skills + persona styles; registered in the core module catalog; rendered by all 11 harness adapters.
+
 ## [0.18.0] — 2026-09-18
 
 ### Added

package/README.es.md

@@ -33,7 +33,7 @@ Es **file-first y zero-runtime**: los agentes son skills en Markdown que tu IDE
 |---|---|
 | **Wize Dev Core** | Ciclo completo (análisis → plan → solución → implementación) + Test Architect + UX Whiteport + Agent Builder. Siempre instalado. |
 | **Wize Web Dev** *(overlay)* | Scaffolds web, SEO, analytics, playbook WCAG para Mantis, Playwright/Vitest para Hawkeye. |
-| **Wize App Development** *(overlay)* | Scaffolds móviles, ficha de tienda, directrices de plataforma (HIG / Material 3), Detox/Maestro para Hawkeye. |
+| **Wize App Development** *(overlay)* | Scaffolds móviles, ficha de tienda, gate de revisión de App Store (auditoría de rechazo al publicar), directrices de plataforma (HIG / Material 3), Detox/Maestro para Hawkeye. |
 | **Wize Security** *(overlay)* | **Pentester de IA.** Pipeline de pentest file-first (recon → enumerate → SAST → DAST → report) conducido por **Natasha Romanoff**, la persona `red-teamer`, con gate de alcance, clasificación OWASP/CVSS e informe ejecutivo. |
 
 ---
@@ -161,6 +161,9 @@ Transversales:
                                 changelog, confirma y aplica la actualización.
     /wize-grill                 Entrevista-hasta-entendimiento antes de cualquier
                                 paso de autoría.
+    /wize-no-ai-slop            Higiene de escrita para texto de usuario final:
+                                elimina patrones de "AI slop" y palabras de relleno
+                                preservando la voz del autor. También detecta slop.
     /wize-quick-dev             Shuri toma un arreglo pequeño sin el ciclo completo.
     /wize-pre-pr-check          Corre lint/format/build/tests unitarios localmente
                                 antes de abrir un PR — falla rápido, cero costo de runner.
@@ -268,6 +271,8 @@ npx wize-dev-kit version-check [--json]  # instalada vs. más reciente (con cach
 
 - [BMAD Method](https://github.com/bmad-code-org/BMAD-METHOD) por Brian (BMad) Madison — ciclo ágil de IA, personas de agentes, patrón de instalador, sistema de módulos.
 - [Whiteport Design Studio expansion](https://github.com/bmad-code-org/bmad-method-wds-expansion) — metodología UX-first, panteón nórdico (Saga, Freya), estructura de fases.
+- [No AI Slop](https://github.com/petergyang/no-ai-slop) por Peter Yang — higiene de escrita que elimina patrones de AI slop sin aplanar la voz del autor; la inspiración para `/wize-no-ai-slop`.
+- [apple-appstore-reviewer (awesome-copilot)](https://github.com/github/awesome-copilot/blob/main/skills/apple-appstore-reviewer/SKILL.md) — auditoría con mentalidad de reviewer para la submisión a App Store; la inspiración para `wize-app-store-review` (gate de publicación del overlay).
 
 Wize Development Kit es una **adaptación independiente** — no afiliada ni respaldada por los autores de BMAD o WDS. Los nombres de personas Marvel se usan como referencias creativas bajo uso nominativo justo.
 

package/README.md

@@ -33,7 +33,7 @@ It is **file-first and zero-runtime**: the agents are Markdown skills your IDE r
 |---|---|
 | **Wize Dev Core** | Full lifecycle (analysis → plan → solution → implementation) + Test Architect + Whiteport UX + Agent Builder. Always installed. |
 | **Wize Web Dev** *(overlay)* | Web scaffolds, SEO, analytics, WCAG playbook for Mantis, Playwright/Vitest for Hawkeye. |
-| **Wize App Development** *(overlay)* | Mobile scaffolds, store listing, platform guidelines (HIG / Material 3), Detox/Maestro for Hawkeye. |
+| **Wize App Development** *(overlay)* | Mobile scaffolds, store listing, App Store review gate (rejection-risk audit at publication), platform guidelines (HIG / Material 3), Detox/Maestro for Hawkeye. |
 | **Wize Security** *(overlay)* | **AI Pentester.** File-first pentest pipeline (recon → enumerate → SAST → DAST → report) driven by **Natasha Romanoff**, the `red-teamer` persona, with a scope gate, OWASP/CVSS classification, and a stakeholder report. |
 
 ---
@@ -161,6 +161,9 @@ Cross-cutting:
     /wize-eli5                  Explain anything to anyone — vocabulary, analogies,
                                 tone, depth and framing calibrated to the audience
                                 (age, role, relationship).
+    /wize-no-ai-slop            Writing hygiene for end-user-facing prose: removes
+                                AI-slop patterns and filler while preserving the
+                                writer's voice. Detects slop on request.
     /wize-quick-dev             Shuri takes a small fix without the full ride.
     /wize-pre-pr-check          Run lint/format/build/unit tests locally before
                                 opening a PR — fail fast, zero CI runner cost.
@@ -267,6 +270,8 @@ npx wize-dev-kit version-check [--json]  # installed vs latest (cached; scriptab
 - [BMAD Method](https://github.com/bmad-code-org/BMAD-METHOD) by Brian (BMad) Madison — agile AI lifecycle, agent personas, installer pattern, module system.
 - [Whiteport Design Studio expansion](https://github.com/bmad-code-org/bmad-method-wds-expansion) — UX-first methodology, Norse pantheon (Saga, Freya), phase structure.
 - [ELI5](https://github.com/dreambigou/eli5) by Andrew Ou — audience-calibrated explanations; the inspiration for `/wize-eli5`.
+- [No AI Slop](https://github.com/petergyang/no-ai-slop) by Peter Yang — writing hygiene that removes AI-slop patterns without flattening the writer's voice; the inspiration for `/wize-no-ai-slop` (Peggy Carter & Mantis apply it to end-user-facing prose).
+- [awesome-copilot's apple-appstore-reviewer](https://github.com/github/awesome-copilot/blob/main/skills/apple-appstore-reviewer/SKILL.md) — reviewer-mindset audit for App Store submission; the inspiration for `wize-app-store-review` (the app-overlay publication gate).
 
 Wize Development Kit is an **independent adaptation** — not affiliated with or endorsed by BMAD or WDS authors. Marvel persona names are used as creative references under nominative fair use.
 

package/README.pt-BR.md

@@ -33,7 +33,7 @@ O Wize Development Kit (WDK) é uma **stack de agentes de IA** instalável que r
 |---|---|
 | **Wize Dev Core** | Ciclo completo (análise → plano → solução → implementação) + Test Architect + UX Whiteport + Agent Builder. Sempre instalado. |
 | **Wize Web Dev** *(overlay)* | Scaffolds web, SEO, analytics, playbook WCAG para o Mantis, Playwright/Vitest para o Hawkeye. |
-| **Wize App Development** *(overlay)* | Scaffolds mobile, listagem em loja, diretrizes de plataforma (HIG / Material 3), Detox/Maestro para o Hawkeye. |
+| **Wize App Development** *(overlay)* | Scaffolds mobile, listagem em loja, gate de revisão da App Store (auditoria de rejeição no momento da publicação), diretrizes de plataforma (HIG / Material 3), Detox/Maestro para o Hawkeye. |
 | **Wize Security** *(overlay)* | **Pentester de IA.** Pipeline de pentest file-first (recon → enumerate → SAST → DAST → report) conduzido por **Natasha Romanoff**, a persona `red-teamer`, com gate de escopo, classificação OWASP/CVSS e relatório executivo. |
 
 ---
@@ -160,6 +160,12 @@ Transversais:
                                 changelog, confirma e aplica o update.
     /wize-grill                 Entrevista-até-entendimento antes de qualquer passo
                                 de autoria.
+    /wize-eli5                  Explique qualquer coisa a qualquer um — vocabulário,
+                                analogias, tom, profundidade e framing calibrados
+                                para o ouvinte (idade, papel, relação).
+    /wize-no-ai-slop            Higiene de escrita para texto de usuário final:
+                                remove padrões de "AI slop" e palavras de enchimento
+                                preservando a voz do autor. Também detecta slop.
     /wize-quick-dev             Shuri pega uma correção pequena sem o ciclo completo.
     /wize-pre-pr-check          Roda lint/format/build/testes unitários localmente
                                 antes de abrir um PR — falha cedo, zero custo de runner.
@@ -266,6 +272,8 @@ npx wize-dev-kit version-check [--json]  # instalada vs. mais recente (com cache
 
 - [BMAD Method](https://github.com/bmad-code-org/BMAD-METHOD) por Brian (BMad) Madison — ciclo ágil de IA, personas de agentes, padrão de instalador, sistema de módulos.
 - [Whiteport Design Studio expansion](https://github.com/bmad-code-org/bmad-method-wds-expansion) — metodologia UX-first, panteão nórdico (Saga, Freya), estrutura de fases.
+- [No AI Slop](https://github.com/petergyang/no-ai-slop) por Peter Yang — higiene de escrita que elimina padrões de AI slop sem achatar a voz do autor; a inspiração para `/wize-no-ai-slop`.
+- [apple-appstore-reviewer (awesome-copilot)](https://github.com/github/awesome-copilot/blob/main/skills/apple-appstore-reviewer/SKILL.md) — auditoria com mentalidade de reviewer para submissão na App Store; a inspiração para `wize-app-store-review` (gate de publicação do overlay de app).
 
 O Wize Development Kit é uma **adaptação independente** — não afiliada nem endossada pelos autores do BMAD ou do WDS. Os nomes de personas Marvel são referências criativas sob uso nominativo justo.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "wize-dev-kit",
-  "version": "0.18.0",
+  "version": "0.20.0",
   "description": "Full-lifecycle AI-assisted development kit with Test Architect and Whiteport Design Studio embedded. Inspired by BMAD Method and WDS.",
   "keywords": [
     "ai",

package/src/app-overlay/module.yaml

@@ -1,6 +1,6 @@
 code: app-overlay
 name: "Wize App Development (overlay)"
-description: "Mobile-stack extension: scaffolds (RN/Expo/Flutter/native), store-listing, release channels, HIG/Material 3 playbook for Mantis, Detox/Maestro playbook for Hawkeye."
+description: "Mobile-stack extension: scaffolds (RN/Expo/Flutter/native), store-listing, App Store review gate, release channels, HIG/Material 3 playbook for Mantis, Detox/Maestro playbook for Hawkeye."
 default_selected: false
 required: false
 overlay_of: method
@@ -17,6 +17,7 @@ stack_catalog:
 # Extra artifacts:
 artifacts:
   - ".wize/planning/app/mobile-store-listing.md"
+  - ".wize/planning/app/app-store-review-report.md"
   - ".wize/planning/app/app-perms-and-privacy.md"
   - ".wize/planning/app/release-channels.md"
 
@@ -27,6 +28,8 @@ skills:
     description: "Define release channel strategy (dev/preview/prod, EAS branches, beta tracks)."
   - code: wize-app-store-listing
     description: "Draft store listing copy + screenshots brief + ASO keywords."
+  - code: wize-app-store-review
+    description: "Publication gate: audit the app as an App Store reviewer, prioritize rejection risks (P0–P3), draft reviewer notes; block prod channels while P0/P1 stay open."
 
 agent_playbooks:
   wize-agent-ux-designer:

package/src/app-overlay/wize-app-store-review/workflow.md

@@ -0,0 +1,75 @@
+---
+
+code: wize-app-store-review
+description: "Use no momento da publicação do app (antes de submeter para a App Store): audita código e metadados como um reviewer da Apple, prioriza riscos de rejeição e redige as reviewer notes."
+name: App Store Review Gate
+overlay: app
+owner: wize-agent-test-architect   # Hawkeye is the gatekeeper; Shuri owns the fix pass
+status: ready
+---
+
+# App Store Review Gate
+
+**Goal.** Audit the app's source code and metadata from an **App Store reviewer's** point of view and produce a prioritized rejection-risk report — so the submission passes fast approval with minimal re-review risk. Fits in the publication flow: run **after** `wize-app-store-listing` (listing drafted) and **before** going live in prod via `wize-app-release-channels`.
+
+Adapted to the Wize method from the [awesome-copilot apple-appstore-reviewer skill](https://github.com/github/awesome-copilot/blob/main/skills/apple-appstore-reviewer/SKILL.md) (MIT) — credited in the README.
+
+## Rules of the pass
+
+- **Change no code in this pass.** Hawkeye reviews and reports; fixes land after, via Shuri.
+- Never invent features or claim something exists without evidence in code/config.
+- Distinguish **assumptions** from **Unverified** items that need the smallest specific evidence.
+- The [App Store Review Guidelines](https://developer.apple.com/app-store/review/guidelines/) change — verify current wording when network is available before quoting a guideline.
+
+## Output
+
+- `.wize/planning/app/app-store-review-report.md`
+
+## Steps
+
+### 1. Identify the app's core
+
+- What is the app's primary purpose? Top 3 user flows?
+- What's required to use it (account, permissions, purchase)?
+- Build system: SwiftUI/UIKit, RN/Expo/Flutter, iOS min version, dependencies.
+
+### 2. Flag top rejection risks first (P0/P1)
+
+Scan for:
+
+- Missing/wrong `NS*UsageDescription` strings for permissions actually requested; vague justifications ("need camera"); launch-time permission asks without context.
+- Privacy: data collection without disclosure, tracking/fingerprinting, missing PrivacyInfo.xcprivacy, missing privacy policy link.
+- Broken IAP flows: subscription without visible restore purchases, misleading pricing, digital features gated behind external payments.
+- Login walls without justification; "Sign in with Apple" compliance when third-party social logins exist; account deletion accessible in-app where applicable.
+- Metadata mismatch with `wize-app-store-listing` output (listing copy vs actual behavior — misaligned copy is a rejection magnet).
+- Claims needing substantiation (health, medical, financial, safety) without proper framing.
+- Minimum functionality: empty states, placeholder screens, dead ends, broken network flows.
+
+### 3. Compliance checklist by area
+
+Systematically check: **Privacy & tracking → Permissions & entitlements → Monetization (IAP/Subscriptions) → Account & authentication → Content/UGC/external links → Technical stability → UX & reviewability.**
+
+Conditional checks, only when relevant: **UGC (Guideline 1.2)** — filtering, reporting, blocking, published contact info, effective content-removal path; **Spam/differentiation (Guideline 4.3(b))** — only when the shipped experience appears indistinguishable from widely available products; **Apple services (Guideline 4.5.3)** — inspect actual triggers/content/stop controls for Live Activities used in messaging, never infer violation from API use alone. Report only applicable findings.
+
+### 4. Write the report (fixed structure)
+
+1. **Executive summary** (5–10 bullets): app purpose in one line, top 3 approval risks, top 3 fast wins.
+2. **Risk register** (table): Priority (P0 blocker / P1 high / P2 medium / P3 low) · Area · Finding · Why review might reject · Evidence (file, symbol, screen, config) · Recommendation · Effort (S/M/L) · Confidence (High/Med/Low).
+3. **Detailed findings** grouped by the areas above; each with what you saw, why it's an issue, concrete change, and how to verify.
+4. **Reviewer experience checklist:** install & launch, first-run clarity, required permissions, core feature access, purchase/restore path, links/support/legal pages, edge cases (offline, empty state).
+5. **Suggested "App Review Notes"** draft for App Store Connect: steps to reach key features, test account credentials (placeholders), unusual permission justifications, gated content + how to test IAP, demo mode.
+
+### 5. Fix pass (after the report, on request)
+
+- Hawkeye hands the prioritized register to **Shuri** for concrete fixes: code changes, permission-prompt/paywall/privacy wording samples, and a pre-submission checklist before re-riding the gate.
+
+## Severity definitions
+
+- **P0 — blocker:** very likely rejection, or app is non-functional for review.
+- **P1 — high:** common rejection reason or serious reviewer friction.
+- **P2 — medium:** risky pattern, unclear compliance, or quality concern.
+- **P3 — low:** polish and improvements.
+
+## Gate rule
+
+No submission to production channels (`wize-app-release-channels` prod) while any **P0 or P1** is open in the register. Re-run or swipe-pass with `WAIVED` (documented in the report) if the user accepts the residual risk. **Unverified** items are not violations — list the minimal evidence needed.

package/src/core-skills/module.yaml

@@ -19,6 +19,9 @@ skills:
   - code: wize-eli5
     name: "ELI5"
     description: "Explain anything to anyone — adapts vocabulary, analogies, tone, depth and framing to the audience (age, role, relationship)."
+  - code: wize-no-ai-slop
+    name: "No AI Slop"
+    description: "Writing hygiene for end-user-facing prose — removes 17 AI-generated patterns and banned words while preserving the writer's voice; also detects slop without rewriting."
   - code: wize-brainstorming
     name: "Brainstorming"
     description: "Divergent-then-convergent ideation; produces idea-pool.md."

package/src/core-skills/wize-no-ai-slop/skill.md

@@ -0,0 +1,83 @@
+---
+code: wize-no-ai-slop
+description: "Use quando qualquer agente for escrever ou editar texto para usuário final — READMEs, runbooks, microcopy, release notes, UX copy — para remover padrões de 'AI slop' sem achatar a voz do autor. Também detecta slop em rascunhos sem reescrever."
+name: No AI Slop
+module: core
+status: ready
+---
+
+# No AI Slop — human writing hygiene
+
+**Goal.** End-user-facing prose (READMEs, runbooks, release notes, UX microcopy, docs, announcements) that reads like a sharp human wrote it — not like a model's default register. Remove AI-generated patterns without flattening the writer's personal voice. This is a hygiene pass every Wize agent applies when the reader is outside the team; internal artifacts (PRD, ADR, gate) keep their own conventions.
+
+Adapted to the Wize method from [no-ai-slop](https://github.com/petergyang/no-ai-slop) by Peter Yang (MIT) — credited in the README.
+
+## Two jobs
+
+**Apply while writing (default for Peggy & Mantis).** When drafting or editing end-user text, run the rules below as you write — not as a retrospective cosmetic pass. Produce the text plus, on request, a short **What changed** section.
+
+**Detect.** When asked whether a piece "reads like AI", name each pattern found with a quoted line and a short fix. Do not rewrite, do not score, and do not guess whether AI wrote it — named patterns are evidence the reader can check. Offer to edit after.
+
+## Voice first
+
+- **Preserve the writer's real voice.** Notice vocabulary, cadence, bluntness, humor, uncertainty, digressions, polish. Keep the traits that feel personal. Do not make every paragraph equally tidy.
+- **Minimum effective edit.** Fix patterns, errors, repetition, unclear passages. Leave strong human sentences alone.
+- **Keep the meaning.** Never invent claims, examples, stats, or opinions. If something is unclear, ask.
+- **Preserve useful edge.** Strong opinions, blunt language, honest admissions ("I think", "maybe") stay when they carry real uncertainty or the writer's spoken rhythm.
+
+## Principles
+
+- **Lead with the point** when the setup adds nothing; keep personal setups that add context, tension, or character.
+- **Front-load only where it helps** — never force every section into the same point-detail-background shape.
+- **Every sentence earns its place.** Cut empty qualifiers and throat-clearing.
+- **Active voice, human subjects.** "The team shipped it Tuesday" beats "the decision emerged". Never let inanimate things do human verbs.
+- **Verbs do the work.** "Made a decision" → "decided". "Has the ability to" → "can". Prefer plain `is`/`has` over fake-strong verbs ("serves as a hub").
+- **Concrete beats abstract.** "Improved efficiency" → "cut deploy time from 40 min to 4". Names, numbers, dates, mechanisms, examples.
+- **Portability test.** A sentence that could move unchanged to another company or product is filler — cut it or replace it with something specific to this subject.
+- **Show, don't label.** Make facts carry the emphasis; delete commentary that tells the reader a point is important, surprising, or obvious.
+- **Protect the specific fact.** Don't smooth a real detail into generic importance.
+- **Untangle without flattening cadence.** Split genuinely hard sentences; keep clear spoken rhythm and fragments that belong to the voice.
+
+## Words to cut
+
+- **Banned:** delve, foster, leverage, utilize, facilitate, empower, streamline, robust, cutting-edge, paradigm shift, game changer, this is huge, this changes everything, tapestry, realm, beacon, multifaceted, meticulous, intricate, paramount, transformative, elevate, embark, supercharge, harness, ever-evolving.
+- **Often-empty adverbs** (cut unless they carry emphasis or uncertainty): just, literally, honestly, simply, actually, truly, fundamentally, importantly, crucially, inherently, inevitably.
+- **Often-empty phrases** (cut when they delay the point): it's worth noting, at the end of the day, when it comes to, at its core, in today's world, the reality is, in terms of, with regard to, in order to, going forward, let's dive in.
+
+## Patterns to cut
+
+1. **Binary contrasts** — "It's not X. It's Y." State Y directly.
+2. **Throat-clearing openers** — "Here's the thing", "Let me be clear". State the point.
+3. **Faux-insight setups** — "What nobody tells you", "The part everyone misses". Make the claim stand alone.
+4. **Colon reveals** — "The best part: it learns." Use colons for lists and labels, not fake drama.
+5. **Superficial analysis** — trailing "-ing" clauses that pretend to explain ("…, highlighting the team's commitment"). State the actual consequence.
+6. **Importance puffery** — "marks a pivotal moment", "a testament to". State the fact; let the reader judge.
+7. **Interpretive metadiscourse** — "That last part matters", "As you can see", "The key point is". Delete.
+8. **Weasel attribution** — "experts agree", "studies show". Name the source or cut; ask before inventing one.
+9. **Synonym cycling** — if the clear word is right, repeat it.
+10. **Negative listing** — "Not a X. Not a Y. A Z." → just say Z.
+11. **Dramatic fragments** — "That's it. That's the whole thing." Use complete sentences.
+12. **Robotic rhythm** — vary repeated sentence shapes and paragraph structures only when it helps the point.
+13. **Rhetorical setups** — "What if I told you…", "Think about it:", self-answered "Question? Answer."
+14. **Fake-profound kickers** — delete the cute final line; end on the clearest concrete sentence, takeaway, or next action.
+15. **Summary-recap endings** — "In conclusion", "Ultimately", restating the piece.
+16. **Formatting slop** — emoji in headings, bold sprinkled mid-sentence, bullets where two sentences of prose read better, headers over two-sentence sections.
+17. **Em dashes as a rhythm crutch** — none in short copy; 1–2 in long drafts only when they clearly beat commas or parentheses.
+
+## Self-check (eval)
+
+Before handing off end-user prose, answer:
+
+- Does it preserve the writer's point, voice, and useful edge — without invented claims? (pass/fail)
+- Is cutting proportional, leaving strong human sentences alone? (pass/fail)
+- Does every generic sentence survive the portability test? (pass/fail)
+- Are banned words, filler phrases, and the 17 patterns absent? (pass/fail)
+- Would the writer recognize it as their own voice when read to a sharp colleague? (pass/fail)
+
+If any check fails, fix and re-check before returning the draft.
+
+## When NOT to use
+
+- Internal Wize artifacts (PRD, ADR, story, gate) — they have their own editorial skills (`wize-editorial-review-prose` / `wize-editorial-review-structure`).
+- Spelling/grammar — use a linter.
+- The user wants audience calibration (age, role, depth) → that's `wize-eli5`; combine both when writing for a tuned audience.

package/src/method-skills/1-analysis/wize-agent-tech-writer/agent.yaml

@@ -17,6 +17,7 @@ style:
   approach: "structure > prose; audience-first"
 
 skills:
+  - wize-no-ai-slop             # hygiene pass on every end-user-facing draft
   - wize-editorial-review-prose
   - wize-editorial-review-structure
   - wize-document-project   # paired with Pepper in brownfield

package/src/method-skills/1-analysis/wize-agent-tech-writer/persona.md

@@ -16,6 +16,7 @@ I am **Peggy Carter**. I make the team's writing sound like one team. Structure,
 
 - I never write "this comprehensive solution." I cut filler.
 - Audience first: who reads this? what do they need? cut everything else.
+- I run the `wize-no-ai-slop` rules on everything end users will read: no AI slop patterns, no banned filler words — but I never flatten the writer's voice. Minimum effective edit; strongest human sentences stay.
 - Structure before sentences: I outline, then I write.
 - I quote sources. I show diagrams. I prefer a table over a paragraph.
 

package/src/method-skills/2-plan-workflows/wize-agent-ux-designer/agent.yaml

@@ -23,6 +23,7 @@ skills:
   - wize-ux-scenarios
   - wize-ux-design
   - wize-design-system
+  - wize-no-ai-slop             # UX copy and scenario prose that end users read
 
 inputs:
   - ".wize/planning/prd.md"

package/src/method-skills/2-plan-workflows/wize-agent-ux-designer/persona.md

@@ -12,9 +12,12 @@ I am **Mantis**. I feel what the user is going to feel before they feel it. Then
 
 ## Style
 
+- Empathy before pixels: feel the user, then design.
+- I show, I don't tell — in specs and in copy. No "revolutionary", no "game changer"; the interface demonstrates the value.
+- UI copy and scenario prose end users will read goes through the `wize-no-ai-slop` rules: concrete, active voice, writer's voice preserved.
 - Quiet, attentive. I ask what hurts before I propose.
 - I prefer scenarios over personas. People act; they aren't archetypes.
-- I show, then I tell. ASCII wireframes first, prose second.
+- ASCII wireframes first, prose second.
 - I cite research. If I don't have research, I say "this is a hypothesis."
 
 ## What I won't do

package/src/orchestrator-skills/wize/skill.md

@@ -91,7 +91,7 @@ When intent is ambiguous or no intent phrase matches, apply this heuristic top-d
 | 20 | All stories gated PASS/CONCERNS, no `ready-for-dev` left | Sprint ended → **Wizer / `wize-retrospective`** + **Pepper+Peggy / `wize-refresh-knowledge`** |
 | 21 | All gated, no new epic pulled | Plan next epic (Tony + Maria Hill), or a roadmap session |
 
-**Overlay ship stages** (when the profile is active): web-overlay adds `wize-web-deploy` / `wize-web-seo-audit`; app-overlay adds `wize-app-release-channels` / `wize-app-store-listing`; security-overlay adds `wize-sec-pentest` (recon → enumerate → SAST → DAST → report, gated by `.wize/security/scope.md`).
+**Overlay ship stages** (when the profile is active): web-overlay adds `wize-web-deploy` / `wize-web-seo-audit`; app-overlay adds `wize-app-release-channels` / `wize-app-store-listing` / `wize-app-store-review` (publication gate, after listing, before prod go-live); security-overlay adds `wize-sec-pentest` (recon → enumerate → SAST → DAST → report, gated by `.wize/security/scope.md`).
 
 ### Intent routing table
 

package/src/orchestrator-skills/wize-help/skill.md

@@ -104,7 +104,7 @@ When intent is ambiguous or no intent phrase matches, apply this heuristic top-d
 | 21 | Release tagged, retrospective not done | **Wizer / `wize-retrospective`** + **Pepper+Peggy / `wize-refresh-knowledge`** |
 | 22 | All gated, no new epic pulled | Plan next epic (Tony + Maria Hill), or a roadmap session |
 
-**Overlay ship stages** (when the profile is active): web-overlay adds `wize-web-deploy` / `wize-web-seo-audit`; app-overlay adds `wize-app-release-channels` / `wize-app-store-listing`; security-overlay adds `wize-sec-pentest` (recon → enumerate → SAST → DAST → report, gated by `.wize/security/scope.md`).
+**Overlay ship stages** (when the profile is active): web-overlay adds `wize-web-deploy` / `wize-web-seo-audit`; app-overlay adds `wize-app-release-channels` / `wize-app-store-listing` / `wize-app-store-review` (publication gate, after listing, before prod go-live); security-overlay adds `wize-sec-pentest` (recon → enumerate → SAST → DAST → report, gated by `.wize/security/scope.md`).
 
 ### Intent routing table