aibreze 0.1.16 → 0.1.17

package/README.md

@@ -1,55 +1,11 @@
-<p align="center">
-  <img src="site/static/logo.svg" alt="aiBreze" width="128" />
-</p>
+# aibreze
 
-# aiBreze
-
-An installable writing rule set for AI agents.
-
-Editorial rules for prose that says something instead of sounding like it.
-AI-assisted or not. Written **aiBreze**. npm **`aibreze`**. A spray, not a
-breeze.
-
-Spray the prose, not the author. Earn the word.
-
-**Docs:** [aibreze.com/docs](https://aibreze.com/docs) · **Site:** [aibreze.com](https://aibreze.com)
-
-## Install
-
-```bash
-pnpm add -D aibreze
-```
-
-Copy `node_modules/aibreze/rules/cursor.mdc` to `.cursor/rules/aibreze.mdc`.
-Keep a short overlay. Full wiring: [docs](https://aibreze.com/docs/install).
-
-Or skip npm and [install the skill](https://aibreze.com/skill) as a folder.
-
-## Not a humanizer
-
-aiBreze does not determine whether a human or a model wrote something, and it
-does not try to fool AI detectors. Same standard either way. If the prose
-smells, spray it.
-
-<!-- xfacts-nutrition-label -->
-
-## Nutrition label
-
-- **AppFacts:** [viewer](https://appfacts.dev/v#af1.eNp1kU1rAyEQhv_KMmeTpVePDRRa0l42t1LKrE6Mjaui4xYb8t-Lu6GQQ29-PO_H6AVmkA8CPE4EEtA-JvohEMA1tgNnx4SpgoDMyCU3RrGdG-KsIp8b9fp8WAl1BnkBh94UNO3mUCMNKtnIonvBGdc1CEjFs10y34Km7VdeDKqz3oCE3TCAgFPIfNu7UPTRYWq5EdUZDX1O6NFQAgnRxwmuAjTFDPL9Ah4kfCf0xlFqijuLTlN0oU7kGa5ihQ3x0TqKiXK-CXRQpTHINvhuDVs1HwLyrP6C7sq1OrfeHXrdkTbUqTDFsozStGOxTrd3-n-QRDFkyyHVZsccs-x7Y_lUxq0KU79DRlczb55CMrTZ73c92nH5uusvQqie3Q) · [raw](https://github.com/Catalyst-Forge-LLC/aibreze/blob/main/APP_FACTS.md)
-- **SkillFacts:** [viewer](https://skillfacts.dev/v#sf1.eNqdU8Fu2zAM_RVDZydZdsxOQ7EBQbNTeyuGQpFom4gsCSTlIAvy76O8dtmhB2Mny09Pj-Lj09VMZrdtTbQjmJ2xeCT4BaY1HiYIKQMp-mDFhgtL8z1RXzcnIMYUdevTerveflaIxUrhKuEEp0oK6CByVf2xf9b_E0avP64QJ1rxCUNQNBfKaWZ98yiJ0IaGSgBuukRNLseAPNhjgCaT8r40nMle2sYWpesn-nfSKlvm5pzo1IV0_nP-636lILKAb86EgrGvNSlNEG10WvZqOBWqKzOIZN5tNj3KUI5rl8bNe-erufPV4fCwuVv0Vvcji26twchCRc1IkV8JrBvmYgNo2zsTU6wSEaReWAEcc0DwinWo3asUjArrQV_VJKVQZTog0HurkS8_W3Ms0Qfwr5YEOzVe_X-5mmxFa5mnx_3hsB793fok9bK39i9lNnrjEsES3mz5IsFgceQlTGC2l0XMoJPW6S2hpiKz38tkS1zGdDihW2STsx7Gj7k6M-hJu65ZEAgwgtDlngcPrBm1c2jqiHXyQxoh2_7fgL5FsCZUzxDoA6pP5_IfGdaIRmelBkqXcPsNuYxlHQ) · [raw](https://github.com/Catalyst-Forge-LLC/aibreze/blob/main/skills/aibreze/SKILL_FACTS.md)
-
-
-## Development
+This package was renamed to **[smellcheck](https://www.npmjs.com/package/smellcheck)**.
 
 ```bash
-pnpm install
-pnpm test
-pnpm site:dev
+pnpm add -D smellcheck
 ```
 
-Site (FilePress + docs mount): `pnpm ship`. The maintainer publishes to npm.
-Agents must not run `npm publish`.
-
-## License
+Site and docs: [smellcheck.dev](https://smellcheck.dev)
 
-MIT. Copyright Catalyst Forge LLC.
+Do not install this name. The rule files, skill, and pocket card now live on `smellcheck`.

package/package.json

@@ -1,62 +1,31 @@
-{
-	"name": "aibreze",
-	"version": "0.1.16",
-	"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/*",
-		"./skills/*": "./skills/*",
-		"./package.json": "./package.json"
-	},
-	"files": [
-		"dist/index.js",
-		"dist/index.d.ts",
-		"rules",
-		"skills",
-		"README.md",
-		"LICENSE"
-	],
-	"scripts": {
-		"build": "tsc",
-		"test": "tsc && node --test dist/index.test.js dist/publish-gate.test.js",
-		"prepare": "tsc",
-		"prepublishOnly": "tsc && node dist/publish-gate.js && pnpm test",
-		"ship": "pnpm --dir site run ship",
-		"site:dev": "pnpm --dir site dev",
-		"site:build": "pnpm --dir site run build",
-		"site:deploy": "pnpm --dir site run ship"
-	},
-	"engines": {
-		"node": ">=20"
-	},
-	"packageManager": "pnpm@10.30.1",
-	"devDependencies": {
-		"@types/node": "^24.3.0",
-		"typescript": "^5.9.2"
-	}
-}
+{
+	"name": "aibreze",
+	"version": "0.1.17",
+	"private": false,
+	"type": "module",
+	"description": "Renamed to smellcheck. pnpm add -D smellcheck",
+	"license": "MIT",
+	"author": "Catalyst Forge LLC",
+	"homepage": "https://www.npmjs.com/package/smellcheck",
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/Catalyst-Forge-LLC/smellcheck.git"
+	},
+	"bugs": {
+		"url": "https://github.com/Catalyst-Forge-LLC/smellcheck/issues"
+	},
+	"files": [
+		"LICENSE",
+		"README.md"
+	],
+	"keywords": [
+		"smellcheck",
+		"deprecated"
+	],
+	"engines": {
+		"node": ">=20"
+	},
+	"publishConfig": {
+		"access": "public"
+	}
+}

package/dist/index.d.ts

@@ -1,26 +0,0 @@
-declare const packageRoot: string;
-declare const rulesDir: string;
-export declare const ruleIds: readonly ["core", "audit", "claims", "essays", "landing", "outreach", "launch", "civic", "academic"];
-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 civic: string;
-    readonly academic: 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

@@ -1,95 +0,0 @@
-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",
-    "civic",
-    "academic",
-];
-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"),
-    civic: join(rulesDir, "civic.md"),
-    academic: join(rulesDir, "academic.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: "civic",
-        title: "Civic / institutional",
-        use: "Filings, testimony, legal-adjacent memos. Ceremony is earned; colleague voice is wrong here.",
-    },
-    {
-        id: "academic",
-        title: "Academic / scholarly",
-        use: "Papers and methods. Precision and citations, not the academic costume.",
-    },
-    {
-        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/rules/academic.md

@@ -1,114 +0,0 @@
-# Academic / scholarly
-
-Apply [`core.md`](./core.md) first. This file is the genre overlay for
-journal articles, working papers, methods sections, literature reviews,
-and dissertation chapters that are papers.
-
-It is not the file for essays or talks ([`essays.md`](./essays.md)),
-filings ([`civic.md`](./civic.md)), or product pages. Reference docs
-and textbooks that are really manuals still get core only.
-
-The colleague voice is close. Precision and citations are the shift.
-Do not put on the academic costume.
-
----
-
-## Register
-
-Write for a peer who already knows the field. Say what you did, what
-you found, and where the claim stops. Full forms more often than the
-default. Contractions are rare, not banned. One is not a finding.
-
-First person is allowed when the field or the overlay uses it ("we
-measured," "I argue"). Passive is not required. Do not convert every
-sentence to "it was found that."
-
-Hedging is earned when it names a limit, a method bound, or a claim
-the data cannot support. "In this sample," "we did not observe,"
-"suggests" stay when they are true. "It could perhaps be argued that"
-is hiding.
-
-The read-aloud test is a careful colleague in the field, not a tired
-product person and not a quarterly from 1987.
-
-Pronouns follow the overlay or the journal. Do not invent "the authors"
-to sound impersonal if the venue uses we.
-
-Hard bans still hold. Insight theater does not become allowed because
-the bibliography is long. Earn the word: "robust," "novel," and
-"seminal" need a measurement, a contrast, or a cite that actually
-carries that weight.
-
----
-
-## What earns its place
-
-- Citations, operational definitions, method, limitations
-- Field terms of art (applicability heuristic)
-- The journal's sections (IMRaD or whatever they print)
-- An abstract that states the finding, not a teaser
-
-Repeating a defined term is not hand-holding. Numbered hypotheses and
-result rows are not triad packing.
-
----
-
-## The costume (do not reach for it)
-
-These are the stereotypical academic tells. Ban them as furniture.
-Leave a word if it is doing a real job in the sentence.
-
-- "Moreover," "Thus," "Furthermore," "Indeed" opening clause after
-  clause
-- "This paper seeks to" / "this study aims to" / "the present work"
-- "It has been shown that" with no cite, or with a cite that does not
-  show it
-- "The extant literature," "a growing body of work," "little attention
-  has been paid"
-- "It is worth noting that" / "it is important to note"
-- Nominalization stacks ("the utilization of the implementation")
-- Forced passive when the actor is known and the field allows we
-- A literature review that only announces a gap
-- A last sentence that winks or mic-drops
-
-Do not inject an essay scene to "humanize" the paper. A worked example
-or a named dataset is an instance, not a memoir. Do not apply essay
-law here.
-
-Do not apply civic captions or landing pain lists.
-
----
-
-## Claims
-
-This genre lives on citations. Run [`claims.md`](./claims.md) when the
-paper asserts effects, magnitudes, or what prior work showed.
-
-A clean-smelling wrong paper is still wrong. Do not cologne a missing
-cite or an overclaim in the abstract.
-
----
-
-## Audit extras for this genre
-
-On top of `core.md` and `audit.md`:
-
-- Costume density (Moreover / Thus / seeks to / extant literature)
-- Hedging that hides a claim instead of naming a limit
-- Forced impersonal voice against the overlay or the venue
-- Abstract that teases and never states the finding
-- Essay anecdote or landing structure
-- A claim that needs a cite and has none
-
----
-
-## Acceptance criteria
-
-1. Overlay or venue named the speaker (we, I, or the paper's convention).
-2. Abstract states the finding.
-3. Hedging names a limit or is cut.
-4. No costume furniture in the open or the close.
-5. Claims that need cites have them, or `claims.md` already flagged
-   the gaps.
-6. No essay scene. No civic caption. No landing pain list.
-7. Hard bans still hold.

package/rules/audit.md

@@ -1,212 +0,0 @@
-# AI smell audit prompt
-
-Reusable prompt for auditing any copy (landing pages, emails, blog posts,
-social posts, docs, filings) 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 (including Look / Let's be clear / Here's the thing),
-validation+profundity, mechanism inflation, narrative
-theater, genuinely-stacks, dramatic apology, suspense, cataphoric
-teasers, setup sentences, em-dash furniture, triad packing including
-prefix-repetition and Not X. Not Y. But Z., empty marketing
-vocab, helper theater, signpost openers, mic-drop closers, intensifier
-filler, parallel-zinger density, bold-lead lists, riddle labels, cozy
-machinery, operator notes in the brochure, hand-holding the obvious,
-unparseable sentences, participial afterthoughts, topic-sentence
-pinning. 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 concessions.** "To be fair…", "It's not all bad…", "That said,
-  there is another side." A real limit stays. A performed even-hand
-  before the pitch does not.
-- **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)
-- intricate, realm, tapestry (as atmosphere with no object)
-- unlock, unleash, harness, empower, supercharge, turbocharge
-- leverage (as empty marketing verb: "leverage your workflow"), utilize
-  (instead of use), underscore (as pomp: "this underscores the need").
-  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
-
-- **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.
-- **Bro-etry / short-line stanzas.** Prose broken into one clause per
-  line, with blank lines as drama, when the piece is not a poem. Flag
-  the formatting, then the sentences.
-- **Do not flag Oxford commas** or other house punctuation as AI tells.
-  A serial comma is a style choice. Em dashes are a density budget in
-  `core.md`, not a mark to erase.
-- **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]