Rewrite Humanizer in Plain Language

.claude-plugin/marketplace.json

@@ -5,12 +5,12 @@
     "name": "blader",
     "url": "https://github.com/blader"
   },
-  "description": "The humanizer skill, installable as a Claude Code plugin.",
+  "description": "Install Humanizer as a Claude plugin.",
   "plugins": [
     {
       "name": "humanizer",
       "source": "./",
-      "description": "Remove signs of AI-generated writing from text, making it sound more natural and human. Based on Wikipedia's \"Signs of AI writing\" guide.",
+      "description": "Rewrite text that sounds AI-generated while keeping the writer's facts, meaning, and voice.",
       "license": "MIT",
       "keywords": ["writing", "editing", "ai-detection", "humanize", "prose", "style"]
     }

.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "humanizer",
-  "description": "Remove signs of AI-generated writing from text, making it sound more natural and human. Based on Wikipedia's \"Signs of AI writing\" guide.",
-  "version": "2.10.2",
+  "description": "Rewrite text that sounds AI-generated while keeping the writer's facts, meaning, and voice.",
+  "version": "2.11.0",
   "author": {
     "name": "blader",
     "url": "https://github.com/blader"

.github/workflows/validate.yml

@@ -1,4 +1,4 @@
-name: Validate package
+name: Check package
 
 on:
   pull_request:
@@ -9,7 +9,7 @@ permissions:
   contents: read
 
 jobs:
-  validate:
+  check:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
@@ -19,11 +19,11 @@ jobs:
       - uses: actions/setup-python@v5
         with:
           python-version: "3.12"
-      - name: Validate synchronized package metadata
+      - name: Check package files
         run: python3 scripts/validate-package.py
-      - name: Verify Agent Skills discovery
+      - name: Check skill discovery
         run: npx --yes skills@1.5.20 add . --list
-      - name: Validate Claude Code marketplace
+      - name: Check Claude marketplace
         run: |
           npm install --global @anthropic-ai/claude-code
           claude plugin validate .

AGENTS.md

@@ -1,31 +1,50 @@
-# AGENTS.md
+# Guide for agents
 
-Guidance for AI coding agents (Claude Code, Codex, Warp, etc.) working in this repository.
+This file explains how to change Humanizer without breaking its package or prompt.
 
-## What this repo is
+## What this repo contains
 
-A portable agent skill implemented entirely as Markdown. The runtime artifact is `SKILL.md`: the agent reads its YAML frontmatter and editor prompt. There is no build step, and the repo should avoid wording that limits support to one or two harnesses.
+Humanizer is an agent skill written in Markdown. `SKILL.md` is the prompt that agents read. The repo has no build step.
+
+Keep the skill portable. Do not write instructions that limit it to one or two agent tools.
 
 ## Key files
 
-- `SKILL.md` — the skill itself. Portable YAML frontmatter (`name`, `description`, `license`, `metadata.version`) followed by the canonical, numbered pattern list with before/after examples. **This is the source of truth.**
-- `skills/humanizer/SKILL.md` — relative link to the canonical root skill for Claude Desktop and older plugin loaders. Never replace it with a second copy or edit it as a separate authority.
-- `README.md` — for humans: installation, usage, a summary table of the patterns, and a version history.
-- `.claude-plugin/plugin.json` — optional Claude Code plugin manifest.
-- `.claude-plugin/marketplace.json` — optional single-repo marketplace entry so `/plugin marketplace add blader/humanizer` works.
-- `scripts/validate-package.py` — dependency-free package and synchronization checks used locally and in CI.
+- `SKILL.md` is the source of truth. It contains portable YAML metadata, 35 numbered patterns, and their examples.
+- `skills/humanizer/SKILL.md` links to the root skill for Claude Desktop and older plugin loaders. Do not replace the link with a copy or edit it as a separate file.
+- `README.md` explains installation, use, patterns, and version history.
+- `.claude-plugin/plugin.json` describes the Claude plugin.
+- `.claude-plugin/marketplace.json` lets users add this repo as a Claude marketplace.
+- `scripts/validate-package.py` checks package files and shared values.
+
+## Rules for changes
+
+Keep `SKILL.md` and `README.md` in sync.
+
+- **Patterns:** The skill has 35 numbered patterns. If you add, remove, or renumber a pattern, update the README table, heading, validator, and every pattern reference.
+- **Version:** Keep the same version in `SKILL.md` under `metadata.version`, the first README version entry, and `.claude-plugin/plugin.json`. Do not add a top-level `version` field to the skill.
+- **Compatibility:** Keep install and use instructions neutral across agents. Names such as Claude Code, OpenCode, and Codex are examples, not limits.
+- **History:** Add a short README version note for any behavior change or non-obvious fix.
+- **Checks:** Before publishing, run `python3 scripts/validate-package.py`, `npx skills add . --list`, and `claude plugin validate .`.
 
-## The maintenance contract
+## Writing style
 
-`SKILL.md` and `README.md` must stay in sync. When you change behavior or content:
+Use Plain Language in code comments, prompts, documentation, descriptions, validation messages, and progress reports.
 
-- **Patterns:** the skill currently defines **35 numbered patterns**. If you add, remove, or renumber any, update the README pattern table, its "N Patterns Detected" heading, and every cross-reference in the same change. Keep numbering stable unless you are deliberately renumbering.
-- **Version:** `SKILL.md` frontmatter stores the version under `metadata.version`, `README.md` has a "Version History" section, and `.claude-plugin/plugin.json` has a `version` field. Bump them together so package metadata matches the skill. Keep the skill version under `metadata`; a top-level `version` key is not portable across Agent Skills hosts. (`marketplace.json` intentionally omits a version so `plugin.json` stays the package source of truth.)
-- **Compatibility:** keep install and usage language harness-neutral. The skill should work in any agent harness that can load Markdown skill instructions; Claude Code, OpenCode, Codex, and other harnesses are examples, not limits.
-- **Validation:** run `python3 scripts/validate-package.py`, `npx skills add . --list`, and `claude plugin validate .` before publishing.
-- **Non-obvious fixes:** if you change the prompt to handle a tricky failure mode (a repeated mis-edit, an unexpected tone shift), add a short note to the README version history explaining what was fixed and why.
+- Lead with the main point.
+- Use common words and active voice.
+- Keep sentences and paragraphs short.
+- Use one term for the same item.
+- Use `must` for requirements.
+- Use headings, lists, and tables when they help the reader.
+- Remove repeated or unnecessary words.
+- Limit acronyms and explain technical terms.
+- Avoid double negatives.
+- Keep exact identifiers, commands, paths, schema fields, quotations, watched phrases, and behavior-bearing examples.
+- Keep the full technical meaning.
 
-## Editing SKILL.md
+## Editing the skill
 
-- Preserve valid YAML frontmatter (formatting and indentation).
-- The prompt below the frontmatter is the product. Edit it like a careful instruction document, not code.
+- Keep the YAML metadata valid.
+- Treat the prompt below the metadata as the product.
+- Prefer a short, clear instruction over another exception or repeated explanation.