anti-default

Un-Default

One thoughtful-language check for every way you build.

Formerly Anti-Default. Same tool — the name shifted so it reads as undoing defaults, not opposing people. Old URLs under darkai.ca/anti-default redirect here. npx anti-default still works as an alias for npx -y anti-default.

Un-Default reviews copy, docs, UI strings, and live pages for colonial defaults, gendered assumptions, ableist metaphors, and documented dogwhistles. It explains what it noticed and offers clearer alternatives.

No account. No AI required for matching. Open rules you can tune.

After Claude writes UI copy · Try the web app · Add the Chrome extension · Star on GitHub

After Claude / Cursor writes UI copy

One command — skill + MCP + PR check. This is the habit that sticks:

npx -y anti-default init

Paste-ready MCP JSON, Claude Project instructions, and a LinkedIn draft:

https://darkai.ca/un-default/for-agents/

Paste MCP config (Cursor · Claude Desktop · Claude Code)

{
  "mcpServers": {
    "un-default": {
      "command": "npx",
      "args": ["-y", "anti-default", "mcp"]
    }
  }
}

Host	Where it goes
Cursor	.cursor/mcp.json (written by init) or Settings → MCP
Claude Desktop	Settings → Developer → Edit Config → claude_desktop_config.json (merge, quit, relaunch)
Claude Code	.mcp.json at repo root (written by init) or claude mcp add

Tools: un_default_scan · un_default_fix · un_default_feedback

Add it in under a minute

npx -y anti-default .

That is the whole local setup. It prints findings and exits non-zero on clear hits. Ambiguous or quoted matches stay advisory.

To pin it in a team project:

npm install --save-dev anti-default

Want the complete project setup?

npx -y anti-default init

init adds an ignore file, changed-files GitHub workflow, Cursor + Claude skills, .cursor/mcp.json + .mcp.json, and inclusive-check / inclusive-fix scripts. Existing files are never overwritten.

AI-copy habit (definition of done)

npx -y anti-default fix .          # safe 1:1 autofixes only
npx -y anti-default .              # remaining findings

Agents should not mark UI/docs work done until hard findings are cleared or explicitly marked fine in context. Soft/coded hits stay advisory.

# Preview autofixes without writing
npx -y anti-default fix . --dry-run

# Intentional language — suppress locally + share structured feedback
npx -y anti-default feedback --kind fine_in_context \
  --rule guys-generic --match "guys" --context "…snippet…" \
  --note "Quoted lyric" --open-issue

MCP server

npx -y anti-default mcp

See for-agents for host-specific paste steps.

Scan the way you work

# Paths
npx -y anti-default ./src ./docs README.md

# CI formats
npx -y anti-default . --format json  -o report.json
npx -y anti-default . --format sarif -o results.sarif

# Batch URLs — no Review UI
npx -y anti-default --urls https://example.com https://example.com/about
npx -y anti-default --urls-file urls.txt --format json

# Only files changed in this branch
npx -y anti-default . --changed-from origin/main

# Keep existing findings quiet; report only new ones
npx -y anti-default baseline .

Ignore what doesn’t matter

Commit a .undefaultignore so day-two noise doesn’t drown the team (example):

node_modules/
vendor/
*.min.js
rule:guys          # turn off one rule for this repo

GitHub Action

Keep inclusive language in the PR loop. This scans only changed files, fails on clear new findings, and leaves a checklist comment:

# .github/workflows/un-default.yml
name: Un-Default
on: [pull_request]
permissions:
  contents: read
  pull-requests: write
  security-events: write

jobs:
  scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - uses: NomadBuilder/un-default@v1
        with:
          changed-from: ${{ github.event.pull_request.base.sha }}
          format: json
          comment-on-pr: "true"

Prefer SARIF for Code Scanning? Set format: sarif and output-file: un-default.sarif. Full inputs: action.yml.

Agent skill

npx -y anti-default init installs .cursor/skills/un-default/SKILL.md — the definition-of-done workflow for AI-generated copy: fix → scan → ask or feedback → re-scan.

Source: skills/un-default/SKILL.md · feedback model: feedback/README.md

Use it as a library

The npm package has no runtime dependencies and exposes the same analyzer used by the CLI and web app:

import { analyzeText, LANGUAGE_RULES } from "anti-default";

const result = analyzeText("Welcome, you guys.");
console.log(result.findings);

Chrome extension

Same rules as the app — on the page you’re already looking at.

Add to Chrome →

Runs offline from a bundled rule list. No tracking. No AI calls.
Dev / unpacked: npm run extension:pack → Load unpacked → extension/ · details in extension/README.md

Web app — try, learn, tune

darkai.ca/un-default

• Review — paste, upload, or scan a URL; export Markdown, CSV, or a checklist
• Swap — turn one phrase into clearer alternatives
• Dogwhistles — learn what a phrase can signal and when context matters
• Rules — tune the open rule catalog for your project

npm install && npm run dev   # localhost:3000

Why teams reach for it

• Before publish — catch defaults in marketing, docs, and product copy
• In the PR — Action + SARIF/JSON so machines and humans both get a signal
• On the live page — extension for writers who never open a terminal
• Without a lecture — suggestions are invitations; context always wins

Every suggestion cites the style guides and references behind it → /sources

Customize & self-host

• Tune in the UI: /rules · edit code: src/lib/rules.ts
• Practice corpus: npm run corpus
• Static export: npm run build → out/
  Subpath (DarkAI): STATIC_EXPORT=true BASE_PATH=/un-default npm run build

Production lives at darkai.ca/un-default and is also vendored in DarkAI.

License

MIT