aibreze 0.1.0

package/rules/landing.md

@@ -0,0 +1,142 @@
+# Landing / marketing
+
+Apply [`core.md`](./core.md) first. This file is the genre overlay for
+landing pages, marketing sites, and other "we sell something" surfaces.
+
+Page extras, the pronoun call, rhetorical budgets, substance gaps, and a
+rewrite gate. Project overlays add the pronoun decision and any
+brand-metaphor budget.
+
+---
+
+## Voice extras (on top of core)
+
+Core already has the register: contractions, mixed sentence length, no
+em dashes, concrete over abstract. On a page, also:
+
+1. **Not a salesperson, not a professor.** Punchy hook, then substance.
+2. **Practical over aspirational.** Hours saved and bottlenecks fixed,
+   not "transforming the future of work."
+3. **Anti-BS positioning, shown not chanted.** Define yourself by what
+   you're not as much as what you are. A page of "No X. No Y. No Z." is
+   a triad, not a position.
+
+---
+
+## Pronouns: decide, then hold
+
+Neither I nor we is the package default. Write the choice in the overlay
+before rewriting.
+
+- **I** matches "you talk to the builder." AI copy defaults to "we"; I
+  is a tell that a person is speaking.
+- **We** is honest when there are collaborators, or when the brand is
+  the speaker. Then soften singular-builder claims so the page does not
+  contradict itself.
+
+Personal outreach (email, text) can still use "I" when the site uses
+"we." See [`outreach.md`](./outreach.md).
+
+Everything else in this file works under either choice.
+
+---
+
+## Page tells (the ones that cluster here)
+
+### Mechanical
+
+- Em dashes in `<title>` and meta description. Core already bans them in
+  body copy; pages hide them in chrome. Zero tolerance including
+  metadata.
+- Emoji as content (result badges, pain-list icons). Replace with type
+  or cut.
+- Title Case On Every Card. Sentence case reads more human.
+
+### Rhetorical (strongest AI signals on a page)
+
+- **"Not X, but Y" antithesis.** Core already budgets teaching
+  antithesis. On a page the cap is hard: **max 2.** Keep only the
+  strongest.
+- **Triadic negation chants.** "No pitch. No pressure. Honest answers."
+  This file's named exception: landing may keep **1** if it is the most
+  concrete one on the page.
+- **Symmetrical parallel constructions.** "We speak both languages:
+  yours and the machine's."
+- **The hedge-flourish.** "We'll also tell you when it isn't (yet)."
+
+### Vocabulary (page hunts beyond core)
+
+Core already bans unlock, unleash, leverage-as-verb, game-changer,
+empower, journey. Extra on pages:
+
+- Noise-cutting variants
+- Friction as hype
+- "Real" as an intensifier used more than twice. When everything is
+  real, nothing is.
+
+### Metaphor overextension
+
+A brand metaphor (forge, bridge, compass, engine) is allowed. Riding it
+through every heading is not. **Budget: 2 references on the whole
+page.** The rest go to plain language.
+
+### Substance gaps
+
+- **Claims with no evidence.** "Proven results" with zero numbers,
+  names, or outcomes. Add one concrete proof point or stop claiming
+  proof.
+- **Pain lists that pitch.** Every item must be a pain, stated from the
+  reader's side. Do not name *your* product in the pain list. Naming a
+  tool the reader already uses is allowed.
+- **Vague promises with fake specificity.** "A clear plan by Friday,"
+  "fluent by next week." Commit to a real offer or drop the fake dates.
+- **Eyebrow word salad.** Keyword strings are not sentences a person
+  would say.
+- **Interchangeability.** Could a competitor swap the logo and ship
+  this? If yes, it says nothing.
+- **Hero names the category.** If you could swap the product name for a
+  competitor's and the hero still works, it is a category ad.
+- **FAQ that is the pitch in question form.**
+- **"We get it" empathy openers** that perform solidarity and then sell.
+- **Testimonials in the brand's own voice.** A quote should not sound
+  like the rest of the page.
+
+---
+
+## Rewrite acceptance criteria
+
+A revised page passes when:
+
+1. Zero em dashes in `<title>` and meta description (body already
+   covered by core).
+2. Pronoun decision made and applied consistently; builder claims
+   aligned to it.
+3. Max 2 "not X, but Y" constructions, max 1 triadic negation chant, max
+   2 brand-metaphor references.
+4. Zero noise-cutting variants, friction-as-hype, and other
+   overlay-banned empties (core empties still apply).
+5. "Real" used at most twice on the page.
+6. Every pain-list item is a reader-side pain with no *your*-product
+   mention.
+7. At least one concrete proof point, or all "proven results" claims
+   removed.
+8. No emoji doing content work.
+9. Read-aloud test: every section can be spoken to a smart friend
+   without either of you cringing. Any sentence you'd never say out
+   loud gets rewritten.
+10. Punchy-then-substantive rhythm present. Nothing aspirational-abstract
+    ("imagine," "transform," "future of work").
+
+---
+
+## Suggested process
+
+1. Decide I vs we (and write it in the overlay).
+2. Mechanical pass first (metadata em dashes, emoji, page-vocab hunts).
+   Cheap wins.
+3. Rebuild the pain list and the how-it-works steps (biggest substance
+   gaps).
+4. Rewrite hero sub and section titles against the rhetorical budgets.
+5. Add one proof point or strip proof claims.
+6. Read the whole page aloud, top to bottom. Fix anything that sounds
+   like a deck.

package/rules/launch.md

@@ -0,0 +1,93 @@
+# Launch / announcement
+
+Apply [`core.md`](./core.md) first. This file is the genre overlay for
+shipping posts: product launches, rebrands, "we built this" reports.
+
+Pair with [`essays.md`](./essays.md) if the piece is a build report on a
+blog, and with [`landing.md`](./landing.md) if it is a marketing page.
+This file is the extra tells that cluster on announcement copy.
+
+---
+
+## Open on something specific, not the announcement formula
+
+Skip "I'm excited to announce" and "Today, we're launching." Those are
+the most generic openers in the genre.
+
+Open on a specific moment or on the artifact. A first-ship story can
+open on the decision that made the project real. A v1.2, a patch, or a
+Show HN should open on the artifact. **Hacker News: artifact first,
+always.**
+
+If what building taught you is the interesting part, write a build
+report (see [`essays.md`](./essays.md)). The product page can carry the
+catalog.
+
+---
+
+## Tells to avoid (launch-post specific)
+
+Beyond `core.md` and `audit.md`:
+
+- **"I'm excited to announce" / "Today, we're launching."** Also "we're
+  excited to share," "I'm humbled to announce."
+- **The feature dump.** Three capabilities a reader can picture, not a
+  catalog. Everything else lives on the product page, behind one link.
+  A builder-audience overlay may raise the cap.
+- **Fake humility.** "It's still early days and we have so much to
+  learn" is a tic, not modesty.
+- **Manufactured urgency.** No countdowns, no launch-week pricing
+  theater.
+- **Stacked CTAs.** One primary outbound link in the body. A second is
+  fine (docs, repo). Do not end every section with a button. On HN the
+  artifact is the link.
+- **Retelling the origin story** when it belongs on another surface.
+  One or two sentences of setup, then a link.
+- **False-momentum closers.** "This is just the beginning." Say the
+  honest status: live, paid, still being hardened, whatever is true.
+- **Working-name history and tech stack** unless the audience is
+  builders who asked. Spec-sheet memory is not a story.
+
+**What you chose not to build** is often the strongest section. Turning
+down an obvious feature is a better story than shipping one, and it is a
+claim a competitor cannot copy by rewriting their copy. Do not invent a
+"we didn't build X" section so the post has one.
+
+---
+
+## Pronouns
+
+Use "we" when the build was a collaboration. Use "I" for observations
+and lessons if the byline is one person. Do not erase the other hands,
+and do not pretend a company wrote the scars. Overlay wins if it
+already chose.
+
+---
+
+## Channel extras
+
+- **Personal surfaces:** first person "I."
+- **Product / company surfaces:** "we" if the overlay says so.
+- **Hacker News:** artifact first, story second. Disclose commercial
+  status up front. Engage in comments; never post-and-ghost. No upvote
+  asks (see [`outreach.md`](./outreach.md)).
+- **LinkedIn / Facebook / X:** no feature dumps, no manufactured
+  urgency, no "Agree?", no "a thread 🧵", no "I'm humbled."
+
+Run `audit.md` on every piece of publishable copy before it goes out.
+Run `claims.md` if the post asserts facts, numbers, or "the industry
+does X."
+
+---
+
+## Acceptance criteria (starting set)
+
+1. Opens on a specific moment or on the artifact, not an announcement
+   formula. HN: artifact first.
+2. Three product capabilities maximum in the body, unless the overlay
+   says the audience is builders who asked for more.
+3. Honest status in the close; no "just the beginning."
+4. One primary outbound link; a second is fine. Don't stack CTAs.
+5. No feature table, no working-name history, unless the overlay
+   permits it for a builder audience.
+6. Read-aloud test: every sentence is one you would say to a peer.

package/rules/outreach.md

@@ -0,0 +1,83 @@
+# Personal outreach
+
+Apply [`core.md`](./core.md) first. This file is the genre overlay for
+email, DM, Signal, and text to people you actually know.
+
+Landing pages can say "we." These messages are from one person. Default
+to **I**.
+
+Do not use this file to invent a relationship. Cold notes are a
+different job: no fake shared history, no "loved your post about X"
+scraped from a feed unless you did.
+
+---
+
+## Tone extras
+
+Direct without being aggressive. Phrasing you would actually send, not
+copy you would publish. Time saved and problems solved, not "transforming
+the future of work."
+
+---
+
+## Principles
+
+**Relationship first.** Lead with warmth and shared history before news,
+asks, or context. Skip this on a thank-you or an in-thread reply; those
+already have a relationship.
+
+**Ask before you broadcast.** A genuine question beats a status update
+when you are starting a thread. Invite dialogue; don't just transmit.
+
+**One primary ask per message**, when there is an ask. Stacked asks
+dilute each other. Pick the real one and let the rest be context. Do
+not legislate a weekly quota; do not stack parallel favors (product
+invite plus "please share this") on the same person in one burst.
+
+**Links as context, not CTAs.** Drop them inline ("the site is at X")
+rather than isolated on their own lines, which reads as marketing.
+
+**Easy out**, when there is an ask. Make it cheap to ignore. "No stress
+if the week's packed" is better than manufactured urgency. A close
+friend and an in-thread reply do not need a permission slip.
+
+**Thank-you, specific, soon.** One line naming what they actually did.
+That is what keeps the favor-budget refilling. A thank-you does not
+need an ask.
+
+---
+
+## Banned in this genre
+
+- "Hope this finds you well."
+- "I'm excited to announce."
+- Feature dumps. One sentence on what it is, then the ask.
+- Upvote asks on Hacker News, ever. HN detects rings. If you mention a
+  Show HN to a friend, no link and no ask. A substantive comment from
+  someone who knows the domain is the only useful favor.
+- Generic "let me know if you have any questions."
+- Fake intimacy on a cold note.
+
+---
+
+## Shape of a message
+
+When you are asking for something:
+
+1. **Anchor.** Something real: last exchange, their world, a shared
+   fact.
+2. **Frame.** One or two sentences of what happened, in voice.
+3. **Ask.** One thing, concrete, sized to the relationship.
+4. **Out.** Permission to skip it.
+
+Thank-yous and replies can be one or two lines. Rewrite per person.
+Seeds are not scripts.
+
+---
+
+## Prompt phrasing (for an agent drafting a note)
+
+Core register still applies. First-person "I." Lead with the
+relationship when you are starting a thread. One ask, or none. Sounds
+like a note you would send, not a landing page in an email client. Do
+not invent shared history.