aibreze 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Catalyst Forge LLC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,149 @@
+# aiBreze
+
+An installable writing rule set for AI agents.
+
+aiBreze strips the performative, faux-profound register from prose.
+Written **aiBreze**. npm **`aibreze`**. A spray, not a breeze.
+
+Direct > clever. Clear > profound. Useful > insightful-sounding. No em
+dashes in publishable prose.
+
+Spray the prose, not the author. Earn the word.
+
+## Before / after
+
+**Before.** At its core, building software isn't just about writing
+code. It's about bridging the gap between imagination and execution,
+creating solutions that don't merely function but fundamentally
+transform the way we interact with technology.
+
+**After.** Software turns an idea into something people can use. Good
+software does that reliably.
+
+## What it is
+
+A composable editorial system for agent-generated prose (and for human
+prose in the same register). Markdown you install and point an agent at.
+Not a CLI (yet), not an editor, not a list of "words ChatGPT uses."
+
+```text
+core.md          shared law (register, bans, cadence, heuristic)
+genre files      surface extras only (essay, landing, outreach, launch)
+project overlay  pronouns, carve-outs, protected lines
+                 ↓
+drafting
+                 ↓
+audit.md         smell
+claims.md        substance first, then voice
+```
+
+Genre files assume `core.md` and are additive: surface law only, no
+copied bans. Do not fork `core.md`.
+
+The **applicability heuristic** is the load-bearing idea. The problem is
+unearned language, not the dictionary. Earn the word: "transformative"
+is fine if something transformed and you can say from what into what.
+"Inflection point" is fine if there was one. Overlay the terms that
+usually pass *here*, with one-line why. The heuristic is the rule; the
+list is not exhaustive.
+
+`claims.md` is substance first, voice after. A clean-smelling wrong
+essay is still wrong. Do not polish a lie.
+
+## Install
+
+```bash
+pnpm add -D aibreze
+```
+
+## What's in the box
+
+| File | Use |
+| --- | --- |
+| `rules/core.md` | Always. Register, applicability heuristic, teaching antithesis, hard bans, cadence, chat vs publish. |
+| `rules/audit.md` | Paste-in smell audit (score, flags, protect list, top 5). |
+| `rules/claims.md` | Skeptical peer review. Substance first, voice after. |
+| `rules/essays.md` | Longform: one register, author in the essay, concrete instance. Not for reference docs. |
+| `rules/landing.md` | Page copy: pronouns, rhetorical budgets, substance, read-aloud. |
+| `rules/outreach.md` | Email / DM / text. Relationship first, one ask. |
+| `rules/launch.md` | Shipping posts. Open on a specific moment or the artifact, not the announcement formula. |
+| `rules/cursor.mdc` | Always-on agent digest. Copy into `.cursor/rules/`. |
+
+## Why "aiBreze"?
+
+People who live with a smell stop noticing it. Generated prose does the
+same trick. Charles Duhigg tells the household version in *The Power of
+Habit* (2012): an odor-eliminating spray that flopped until the company
+realized habituation was the problem, then sold the bottle as the reward
+at the end of a cleaning habit. This package is that move for writing.
+Make the smell visible, then take it off. Read Duhigg for the original.
+
+The register is also leaking the other way: humans now write like the
+models. aiBreze is a writing standard, not an AI-cleanup gimmick.
+
+## Not a humanizer
+
+aiBreze does not determine whether a human or a model wrote something,
+and it does not try to fool AI detectors. It applies the same standard
+either way. If the prose smells, spray it.
+
+Adjacent tools tend to be humanizers ("make this sound human"), banned-word
+anti-slop lists, or general style linters (Vale, write-good). This package
+is the layered law: genre surfaces, an applicability heuristic (earn the
+word), claims before cologne, overlays instead of forks, and both
+prevention at draft time and audit after. Authorship is irrelevant. Prose
+quality is the subject.
+
+## Use from Node
+
+```ts
+import { readRule, files, catalog } from "aibreze";
+
+const core = readRule("core");
+// files.audit is an absolute path to rules/audit.md
+```
+
+Markdown is also exported as `aibreze/rules/core.md` (and the rest), so
+an agent or a prompt assembler can read the files from `node_modules`.
+v1 is `readRule`. Assembling core + genre + overlay is concatenation on
+purpose.
+
+## Agent setup
+
+1. `pnpm add -D aibreze`
+2. Copy `node_modules/aibreze/rules/cursor.mdc` to
+   `.cursor/rules/aibreze.mdc`
+3. Point "Full rules" at `node_modules/aibreze/rules/core.md`
+4. Keep a project overlay (carve-outs, I vs we, protected lines)
+5. When drafting a page, essay, note, or ship post, open that genre file
+6. For a publish pass: paste `rules/core.md` plus the overlay, then
+   `rules/audit.md` or `rules/claims.md` (both are additive; do not paste
+   the prompt alone)
+
+## Overlay shape
+
+Keep it short. Point at this package, then only:
+
+- Pronouns per surface
+- Terms that pass the applicability heuristic *here*, with one-line why
+- Protected maxims / testimony
+- Genre extras that are house law (every essay ends in a deed, brand
+  metaphor budget, …)
+
+## Site
+
+The public site lives in [`site/`](site/) (FilePress, [`getfilepress`](https://www.npmjs.com/package/getfilepress)). [aibreze.com](https://aibreze.com). Source: [Catalyst-Forge-LLC/aibreze](https://github.com/Catalyst-Forge-LLC/aibreze).
+
+```bash
+pnpm site:dev
+pnpm site:build
+```
+
+## Publishing to npm
+
+The maintainer publishes. Agents must not run `npm publish`,
+`pnpm publish`, or `yarn npm publish`.
+
+## License
+
+MIT. Copyright Catalyst Forge LLC.

package/dist/index.d.ts

@@ -0,0 +1,24 @@
+declare const packageRoot: string;
+declare const rulesDir: string;
+export declare const ruleIds: readonly ["core", "audit", "claims", "essays", "landing", "outreach", "launch"];
+export type RuleId = (typeof ruleIds)[number];
+export declare const files: {
+    readonly core: string;
+    readonly audit: string;
+    readonly claims: string;
+    readonly essays: string;
+    readonly landing: string;
+    readonly outreach: string;
+    readonly launch: string;
+    readonly cursor: string;
+};
+export type FileId = keyof typeof files;
+export declare const catalog: ReadonlyArray<{
+    id: FileId;
+    title: string;
+    use: string;
+}>;
+export declare function rulePath(id: FileId): string;
+export declare function readRule(id: FileId): string;
+export declare function assertRulesPresent(): string[];
+export { packageRoot, rulesDir };

package/dist/index.js

@@ -0,0 +1,81 @@
+import { existsSync, readFileSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
+const packageRoot = join(dirname(fileURLToPath(import.meta.url)), "..");
+const rulesDir = join(packageRoot, "rules");
+export const ruleIds = [
+    "core",
+    "audit",
+    "claims",
+    "essays",
+    "landing",
+    "outreach",
+    "launch",
+];
+export const files = {
+    core: join(rulesDir, "core.md"),
+    audit: join(rulesDir, "audit.md"),
+    claims: join(rulesDir, "claims.md"),
+    essays: join(rulesDir, "essays.md"),
+    landing: join(rulesDir, "landing.md"),
+    outreach: join(rulesDir, "outreach.md"),
+    launch: join(rulesDir, "launch.md"),
+    cursor: join(rulesDir, "cursor.mdc"),
+};
+export const catalog = [
+    {
+        id: "core",
+        title: "Core",
+        use: "Always. Target register, applicability heuristic, teaching antithesis, hard bans, cadence budgets, chat vs publish.",
+    },
+    {
+        id: "audit",
+        title: "Smell audit",
+        use: "Paste-in smell audit. Additive to core: extras, vocab hunt list, score and top-five.",
+    },
+    {
+        id: "claims",
+        title: "Claims + voice",
+        use: "Skeptical peer review. Substance first so you do not cologne a lie, then aiBreze.",
+    },
+    {
+        id: "essays",
+        title: "Essays / longform",
+        use: "Essays and talks: one register, author in the essay, concrete instance. Not for reference docs.",
+    },
+    {
+        id: "landing",
+        title: "Landing / marketing",
+        use: "Page copy: pronoun decision, rhetorical budgets, substance gaps, read-aloud gate.",
+    },
+    {
+        id: "outreach",
+        title: "Personal outreach",
+        use: "Email, DM, and text. Relationship first, one ask, links as context.",
+    },
+    {
+        id: "launch",
+        title: "Launch / announcement",
+        use: "Shipping posts. Open on a specific moment or the artifact, not the announcement formula.",
+    },
+    {
+        id: "cursor",
+        title: "Cursor pocket card",
+        use: "Always-on agent digest. Copy to `.cursor/rules/` and point at core plus a project overlay.",
+    },
+];
+export function rulePath(id) {
+    return files[id];
+}
+export function readRule(id) {
+    return readFileSync(files[id], "utf8");
+}
+export function assertRulesPresent() {
+    const missing = [];
+    for (const id of Object.keys(files)) {
+        if (!existsSync(files[id]))
+            missing.push(files[id]);
+    }
+    return missing;
+}
+export { packageRoot, rulesDir };

package/package.json

@@ -0,0 +1,56 @@
+{
+  "name": "aibreze",
+  "version": "0.1.0",
+  "private": false,
+  "type": "module",
+  "description": "Installable writing rule set for AI agents. Sprays the performative, faux-profound register off prose. Core bans, smell audit, claims review, genre overlays.",
+  "license": "MIT",
+  "author": "Catalyst Forge LLC",
+  "keywords": [
+    "ai",
+    "writing",
+    "style-guide",
+    "prose",
+    "llm",
+    "prompts",
+    "copyediting",
+    "voice"
+  ],
+  "homepage": "https://aibreze.com",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Catalyst-Forge-LLC/aibreze.git"
+  },
+  "bugs": {
+    "url": "https://github.com/Catalyst-Forge-LLC/aibreze/issues"
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    },
+    "./rules/*": "./rules/*",
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "dist/index.js",
+    "dist/index.d.ts",
+    "rules",
+    "README.md",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "devDependencies": {
+    "@types/node": "^24.3.0",
+    "typescript": "^5.9.2"
+  },
+  "scripts": {
+    "build": "tsc",
+    "test": "tsc && node --test dist/index.test.js",
+    "site:dev": "pnpm --dir site dev",
+    "site:build": "pnpm --dir site run build",
+    "site:deploy": "pnpm --dir site run deploy"
+  }
+}

package/rules/audit.md

@@ -0,0 +1,200 @@
+# AI smell audit prompt
+
+Reusable prompt for auditing any copy (landing pages, emails, blog posts,
+social posts, docs) for signs it was AI-generated or AI-flavored.
+
+**This prompt is additive.** Paste into a model, in order:
+
+1. [`core.md`](./core.md) (required) and the project's overlay
+2. Everything below the divider in this file
+3. The copy to audit
+
+Do not treat the lists below as the house law. Hunt core's hard bans,
+cadence budgets, and applicability heuristic from `core.md`, then the
+extras here.
+
+**When substance is in question** (overclaim, thin evidence, bad
+attribution), use [`claims.md`](./claims.md) instead of or before a
+smell-only pass.
+
+---
+
+You are an expert copy editor with a specialty in detecting "AI smell":
+the patterns, tics, and vocabulary that make writing feel
+machine-generated, generic, or untrustworthy. Audit the copy I provide
+below. You have `core.md` (and any overlay) in this context. Apply them.
+
+If `core.md` is not in this context, stop and say so. Do not run a smell
+pass that skips the house bans.
+
+## Your task
+
+1. **Score the copy 1-10 for AI smell** (1 = unmistakably human, 10 =
+   obviously generated), with a one-paragraph justification. A human
+   draft with two marketing words is not a 7. Score the pattern, not
+   the word count.
+2. **Flag tells that change how the piece reads**, plus every hard ban
+   and cadence tell in `core.md` that actually fires. Quote the
+   offending text, name the tell, explain briefly. Do not dump every
+   vocab-list hit. Apply the applicability heuristic first. A single
+   "robust" that names a real property is not a finding.
+3. **Suggest a rewrite** for flagged items that are worth changing.
+   Preserve meaning. Sound like a sharp, specific human.
+4. **Identify what's working.** Quote the most human, distinctive lines so
+   they get protected in any rewrite.
+5. **End with a prioritized fix list**: the 5 changes that would most
+   reduce the AI smell, in order of impact. The top 5 is the
+   deliverable. The flag list is evidence, not a to-do of 40 rewrites.
+
+## The tells to hunt
+
+### From core.md (do not re-list)
+
+Hunt every hard ban and cadence tell in `core.md`: escalation formula,
+honest framing, validation+profundity, mechanism inflation, narrative
+theater, genuinely-stacks, dramatic apology, suspense, setup sentences,
+em dashes, triad packing including prefix-repetition, empty marketing
+vocab, helper theater, signpost openers, mic-drop closers, intensifier
+filler, parallel-zinger density, bold-lead lists. Apply the
+corpus-applicability heuristic before rewriting overlay terms. Teaching
+antithesis is allowed only when categories differ, never as
+synonym-escalation. One concrete landing chant is a named exception,
+not a free pass for every triad.
+
+### Rhetorical extras (cluster here; not a second copy of core)
+
+- **"Not X, but Y" antithesis (broader than escalation).** One careful
+  teaching contrast per piece can be spice. More than two is a pattern,
+  and patterns smell generated.
+- **Triadic chants.** "No fluff. No jargon. No BS." / "Faster. Smarter.
+  Better." Groups of three parallel fragments, especially negations.
+  Budget: one per piece, max, and only if core's protected-maxim
+  exception or a genre overlay (landing: one concrete chant) permits it.
+- **Symmetrical parallel constructions.** "We speak your language and the
+  machine's." Clever-sounding mirror phrases that a million landing pages
+  already used.
+- **The rule of three in lists everywhere.** When every sentence
+  enumerates exactly three items, a model wrote it.
+- **Rhetorical questions as transitions.** "So what does this mean for
+  you?" / "The result?" / "The best part?"
+- **The hedge-flourish.** Winking qualifiers like "(yet)" or "at least
+  for now" that perform humility instead of having it.
+- **False momentum closers.** "The future is here." / "And this is just
+  the beginning." / "The only question is whether you'll be ready."
+- **Setup-payoff formula on every heading.** Colon constructions: "The
+  problem: you're drowning in tools." Once is fine. Every heading is a
+  template.
+- **Outline-first filler.** An H2 with a sentence of nothing under it,
+  then the next H2. The outline shipped; the prose did not.
+- **Engagement bait.** "Agree?", "a thread 🧵", "I'm humbled to
+  announce."
+
+### Vocabulary tells
+
+Suspects, not automatic flags. Apply the corpus-applicability heuristic
+first. Flag empty marketing use and close variants. Leave terms of art,
+product names, and words that would get less precise if swapped for
+"important."
+
+- delve, dive deep, deep dive, unpack, explore (as a section-verb with
+  no object worth exploring)
+- unlock, unleash, harness, empower, supercharge, turbocharge
+- leverage (as empty marketing verb: "leverage your workflow"), utilize
+  (instead of use). Domain projects may carve out doctrinal "leverage"
+  (force / fulcrum sense) in an overlay.
+- seamless, seamlessly, effortless, frictionless, streamline
+- game-changer, game-changing, revolutionary, cutting-edge, next-level
+- cut through the noise, separate signal from noise, rise above the noise
+- landscape (as in "the AI landscape"), ecosystem-as-hype, "in this
+  space" as market-speak (not state space / design space as terms of art)
+- journey (as in "your AI journey"), transformation-as-hype (not
+  org-change when that is the subject)
+- robust, comprehensive, holistic, tailored, bespoke: filler adjectives
+  only, not a named requirement ("robust to partition")
+- "In today's fast-paced world" and any "In today's X" opener
+- "Whether you're a X or a Y" audience straddles
+- "at the end of the day," "when it comes to," "it's worth noting"
+- crucial, vital, essential when stacked or used as filler more than
+  once
+- "real" as an intensifier used more than twice (real results, real
+  value, real impact)
+- boost, take it to the next level, elevate-as-hype
+- "the power of" anything
+
+### Structural extras
+
+- **Em dashes.** Core already bans them in publishable prose. Still flag
+  density and the clause-then-punchline construction as a smell signal
+  (some human writers use them heavily; combined with other tells they
+  are a strong signal).
+- **Emoji as content furniture.** Checkmarks, rockets, and lightbulbs
+  doing the work that words or design should do, especially in lists and
+  result badges.
+- **Title Case On Every Heading** in body copy contexts where sentence
+  case would be natural.
+- **Uniform paragraph lengths.** Every paragraph 2-3 sentences, every
+  sentence medium-length. Human writing has variance: a one-word
+  sentence, then a long one.
+- **Perfectly balanced sections.** Every section the same length, every
+  card grid filled to an even number, every argument given exactly equal
+  weight.
+- **The wrap-up paragraph that restates everything.** "In short, …"
+  conclusions that add nothing.
+- **Markdown tables as a substitute for prose.** A table that should
+  have been three sentences.
+
+### Substance tells
+
+Use [`claims.md`](./claims.md) when truth or scope is the question. Here,
+flag only the generated-consensus shape.
+
+Do not demand a fight from a changelog, API doc, or reference page. Do
+not demand a dinner-table voice from UI chrome, labels, or error
+strings.
+
+- **Claims with no evidence.** "Proven results," "trusted by teams
+  everywhere," with zero numbers, names, or examples anywhere.
+- **Fake specificity.** Concrete-sounding but unverifiable details: "a
+  clear plan by Friday," "10x your output," deadlines and multipliers
+  with no mechanism behind them.
+- **Pain lists that pitch.** Sections framed as the reader's problems
+  where half the items are actually the vendor selling ("That's where we
+  come in...").
+- **Vague benefits stated as outcomes.** "Save time and money" without
+  saying whose time, on what, or how.
+- **Metaphor overextension.** A brand metaphor (forge, bridge, compass,
+  engine) ridden through every heading. On a **page**, budget two
+  references. A long essay whose subject *is* the metaphor may use more;
+  riding it through every heading is still the smell.
+- **Interchangeability test.** Could a competitor swap in their logo and
+  ship this copy unchanged? If yes, it says nothing. Pages and posts,
+  not reference.
+- **No opinion anywhere.** On essays and thought-leadership, copy that
+  never takes a side reads as generated consensus. Not for reference
+  docs or release notes.
+- **Perfect politeness.** No edge, no specificity of voice, nothing that
+  sounds like one particular person on one particular day. Same scope:
+  essays and pages that should have a person. Not man pages.
+
+### The final test
+
+For prose aimed at a human reader (pages, essays, notes, posts): read
+the copy aloud. Flag any sentence that a smart person would never
+actually say to a friend across a table. That's the sentence to rewrite.
+
+Do not apply the dinner-table test to reference docs, changelogs, or UI
+chrome.
+
+## Output format
+
+1. **Score and verdict** (one paragraph)
+2. **Flagged items** (quote, tell name, why, suggested rewrite). Evidence,
+   not a 40-item homework list.
+3. **What's working** (quotes to protect)
+4. **Top 5 fixes by impact**
+
+---
+
+## COPY TO AUDIT
+
+[paste copy here]