@azure-id/orc 1.6.0 → 1.7.0

package/templates/skills/_shared/rules/delivery.md

@@ -0,0 +1,114 @@
+<!-- orc-rules:pack id=delivery prefix=OSD layer=core -->
+
+# ORC RULES · Delivery (`OSD`)
+
+> **READ-ONLY.** This file ships with ORC and changes only with `orc update`.
+> Your own rules go in `.claude/orc/rules.md`, and **yours win** wherever the two
+> disagree.
+
+**Applies to** what an agent reports about its own work: a subagent return, a
+phase report, a gate verdict, a ship summary, and what it says in chat.
+
+This pack is in the **`core`** layer, so it rides in every slice of every lane
+that carries rules at all. Prose style is optional in some lanes. Honesty is not.
+
+**Source.** [`ehmo/slopkit`](https://github.com/ehmo/slopkit), the `slopgent`
+skill · Miqdad Badjuber — [`miqdadbadjuber/anti-slop`](https://github.com/miqdadbadjuber/anti-slop) R-35 ·
+[`BioInfo/slopless`](https://github.com/BioInfo/slopless) quality gates.
+Full attribution in `CREDITS.md`.
+
+---
+
+### OSD-01 · HARD · Separate what changed from what is verified
+
+Two different facts, always reported as two facts.
+
+```
+Edited verifyToken at auth.ts:42. Tests not run yet.
+```
+
+Not "fixed the token bug". Editing is an observation. Fixing is a claim, and a
+claim needs a run behind it.
+
+### OSD-02 · HARD · Never report an unrun tool
+
+Never say a command ran, a test passed, a build succeeded, a file was read or a
+page was fetched when it did not happen in this session. Not as a summary, not
+as a plan restated in the past tense, not as an inference from the diff.
+
+This is the single most damaging rule in the pack to break, because everything
+downstream trusts it.
+
+### OSD-03 · HARD · No invented confidence
+
+Cut "this should work now", "definitely fixed", "should be perfect", "that ought
+to do it". Confidence is reported from evidence or it is not reported.
+
+Say what you observed and what remains unknown.
+
+### OSD-04 · HARD · Cut empty hedges, keep load-bearing caveats
+
+The two look alike and are opposites.
+
+- **Empty hedge**, cut it: "this might possibly help", "hopefully that works".
+- **Load-bearing caveat**, keep it: "this only covers the JSON path; the
+  multipart branch is untested", "this assumes the column is already indexed".
+
+The test is whether a reader could act on it. Scope, risk and uncertainty are
+load-bearing. A "be concise" instruction cuts both; this rule cuts one.
+
+### OSD-05 · HARD · No apology theatre
+
+State the cause and the fix. No "I apologise for the confusion", no "you're
+absolutely right, my mistake", no paragraph of contrition before the correction.
+
+One correction, plainly, then continue.
+
+### OSD-06 · LOCK · An estimate names its driving variable
+
+Never anchor on human-effort time ("this would take a developer two days").
+Name what actually creates the uncertainty — file count, test-suite size, build
+repetitions, number of call sites — then pin it with a measurement where one
+exists.
+
+### OSD-07 · LOCK · No trailing recap
+
+No closing paragraph restating what was just done. The user reads the diff and
+the return. A recap is a second copy of information they already have.
+
+Report what is **unfinished**, **unverified** or **decided**. Not what is visible.
+
+### OSD-08 · HARD · An honest partial beats a false done
+
+Report what is unmet. Never round up, never mark a criterion met because
+everything around it is. A task that is 80% done is reported as 80% done with
+the missing 20% named.
+
+Cites house card rule 6.
+
+### OSD-09 · LOCK · One issue at a time
+
+When raising a problem that needs the user, raise one. A list of five concerns
+in one turn gets one answer covering none of them.
+
+Exception: a batch the user explicitly asked to be batched, and a round of
+questions in an interview phase, where the format is the point.
+
+### OSD-10 · HARD · No verification theatre
+
+A PASS with no record of what was actually exercised is not a PASS.
+
+Report the check element by element: the command that ran and its exit code, the
+test names, the click-through if it was a UI, the file and line for each
+criterion. If the deliverable could not be run, say so and say that the check
+was code inspection instead. Never imply a run that did not happen.
+
+---
+
+## Not a ban — keep these
+
+- Every caveat on the `OSD-04` load-bearing list.
+- An explicit "I do not know" or "I did not check".
+- A one-line correction of a real earlier error.
+- The exact command, path, error code and exit status. Those are the evidence,
+  and they are never clutter.

package/templates/skills/_shared/rules/ui.md

@@ -0,0 +1,139 @@
+<!-- orc-rules:pack id=ui prefix=OSU layer=ui -->
+
+# ORC RULES · UI (`OSU`)
+
+> **READ-ONLY.** This file ships with ORC and changes only with `orc update`.
+> Your own rules go in `.claude/orc/rules.md`, and **yours win** wherever the two
+> disagree.
+
+**Applies to** front-end work only. This pack rides **per task**, never per lane:
+the orchestrator adds it to a slice whose declared files are front-end. A UI rule
+in a backend slice is tokens paid for nothing.
+
+**This is a filter, not a style guide.** It prescribes no colour, no typeface and
+no layout. It rejects **technique without purpose**. Where the project has a
+design direction — a `DESIGN.md`, a brand guide, a design system — that
+direction is the identity and this pack only filters on top of it. A bold palette
+is identity. A blue-to-purple gradient chosen because it was the default is slop.
+
+**Source.** Miqdad Badjuber — [`miqdadbadjuber/anti-slop`](https://github.com/miqdadbadjuber/anti-slop), rules R-01 to R-38 (MIT).
+Full attribution in `CREDITS.md`.
+
+---
+
+### OSU-01 · HARD · No dead controls
+
+Every interactive element does something real, or it does not exist:
+
+- a link or button that reaches a destination that exists
+- a modal that opens and closes, and closes on `Escape`
+- a toggle that changes state
+- an external action (`mailto:`, a real URL)
+- a form that submits and shows feedback
+
+A button that does nothing is a defect, not decoration. A nav item pointing at a
+section that does not exist is the same defect. If it cannot have a destination
+yet, remove it, or label it "Coming soon" **and** leave a `TODO` that names the
+task (`OSC-05`).
+
+### OSU-02 · HARD · Three states minimum
+
+Any view that displays data has an **empty** state, a **loading** state and an
+**error** state. A UI built only for the ideal condition is not finished.
+
+These are not extras. They are part of the view.
+
+### OSU-03 · HARD · Accessible by default
+
+- WCAG AA contrast: 4.5:1 for body text, 3:1 for large text (18px+). Test across
+  the whole area the text crosses, not one point.
+- Every interactive element reachable with `Tab` and `Shift+Tab`, in visual
+  order, and operable with `Enter` or `Space`.
+- Every focused element has a visible focus indicator.
+- Never `outline: none` or `outline: 0` without a better replacement.
+
+A UI that needs a mouse is unfinished.
+
+Partly checked by `orc rules lint` (`outline: none` with no replacement).
+
+### OSU-04 · HARD · Real content or an honest placeholder
+
+No fabricated testimonial, statistic, customer logo, team member, review, or
+security or compliance claim. No number without a real source.
+
+A placeholder is written as what it is: `[REAL DATA]`, `[LOGO]`, "Coming soon".
+Never disguised as final.
+
+**An empty section beats a fabricated one.** If there are no testimonials, there
+is no testimonials section.
+
+### OSU-05 · LOCK · No generic CTA
+
+"Get Started", "Learn More", "Try Now", "Explore", "Discover" name no action.
+Name the action: "Start the free trial", "Watch the 2-minute demo", "Create an
+account".
+
+### OSU-06 · HARD · No buzzword UI copy
+
+Never in shipped interface text: "AI Powered" · "Next Generation" ·
+"Revolutionary" · "Seamless" · "Cutting Edge" · "Intelligent" · "Ultimate" ·
+"Powerful" · "Effortless" · "Supercharged".
+
+Say what it does. Show evidence, not adjectives.
+
+Checked by `orc rules lint`.
+
+### OSU-07 · PURPOSE · Decoration needs a written reason
+
+Each of these is **allowed** and fails only as an unexplained default. Write the
+one-line reason it serves hierarchy, identity or readability:
+
+- gradient as a primary colour (blue→purple, blue→cyan, purple→pink especially)
+- glassmorphism · **dose cap: at most two elements**, never navbar + cards +
+  modal + sidebar together
+- glow · **dose cap: at most two elements**
+- capsule badge with no real status behind it
+- a button arrow as every button's identity
+- grid, dot, blueprint or graph-paper background
+- sparkle, star, magic, lightning, diamond, orb or robot as a feature icon
+- an animation stack (fade-up + float + scale + bounce) on everything
+- a generic illustration set with no connection to the product
+
+A gradient that separates one level of hierarchy from another is craft. The same
+gradient covering the page is slop. The technique is not the problem.
+
+### OSU-08 · LOCK · Do not clone a named product
+
+Do not build a visual that copies another product's look unless the user asked
+for it by name. References are inspiration, not a template.
+
+Models default to cloning the products that dominate their training data. Notice
+when that is what is happening.
+
+### OSU-09 · HARD · Mobile is part of the design
+
+No horizontal overflow. Text stays inside its container. Cards do not collide or
+clip. The navbar stays usable. Tap targets meet 44px. Spacing stays consistent
+across breakpoints.
+
+Responsiveness is not an add-on and not a follow-up task.
+
+### OSU-10 · HARD · Every decision has a one-line reason
+
+Before calling a UI done, write one line for each major decision: why this
+colour, this layout, this typeface, this spacing, this card, this icon.
+
+If the reason cannot be written in one line, the decision is not settled. This
+is the keystone of the pack — it is what `OSU-07` checks against, and it is the
+whole mechanism by which "technique with purpose" is distinguishable from
+"technique by default".
+
+---
+
+## Not a ban — keep these
+
+- Anything the project's own design direction specifies. Identity is not slop.
+- A technique with its reason written. That is the pass condition, not an
+  exception to it.
+- A deliberate uniform layout, when uniformity is the stated choice rather than
+  the default that happened.

package/templates/skills/_shared/rules/writing.md

@@ -0,0 +1,223 @@
+<!-- orc-rules:pack id=writing prefix=OSW layer=writing -->
+
+# ORC RULES · Writing (`OSW`)
+
+> **READ-ONLY.** This file ships with ORC and changes only with `orc update`.
+> Your own rules go in `.claude/orc/rules.md` (`orc rules add --priority P0
+> --text "…"`), and **yours win** wherever the two disagree.
+
+**Applies to** every word an agent writes: wiki docs, analysis reports, plans,
+requirement specs, commit bodies, PR descriptions, and what it says in chat.
+
+**Source.** Peter G. Yang — [`petergyang/no-ai-slop`](https://github.com/petergyang/no-ai-slop) (MIT) ·
+Miqdad Badjuber — [`miqdadbadjuber/anti-slop`](https://github.com/miqdadbadjuber/anti-slop), the `antislop-copywriting` skill (MIT) ·
+Matty Cartwright — [The Anti-Slop Writing Rules](https://mattycartwright.com/blog/the-anti-slop-writing-rules).
+Full attribution in `CREDITS.md`.
+
+**Tiers.** `HARD` absolute · `PURPOSE` allowed with a written one-line reason ·
+`LOCK` a consistency requirement, reported but never blocking.
+
+---
+
+### OSW-01 · HARD · Lead with the point
+
+No throat-clearing opener. Cut "Here's the thing", "Here's what I mean", "Let me
+be clear", "I'll be honest", "The uncomfortable truth is". State the point.
+
+Keep a personal aside, a story or an admission when it creates context or
+tension. The ban is on the empty run-up, not on character.
+
+### OSW-02 · HARD · No binary contrast
+
+Cut "It's not X, it's Y", "The question isn't X, it's Y", "It's not just X but
+Y", and negative listing ("Not a X. Not a Y. A Z."). State Y directly.
+
+"The question isn't the model. It's the eval." becomes "The eval matters more
+than the model."
+
+### OSW-03 · HARD · No faux-insight setup
+
+Cut "What nobody tells you", "the part everyone misses", "what most people get
+wrong", "this is the part most people skip". The setup flatters the writer and
+carries no information. Make the claim stand on its own.
+
+### OSW-04 · LOCK · No colon reveal
+
+A noun phrase, a colon, then a dramatic lowercase reveal is a generated shape:
+"The detail that makes it work: a separate agent grades it." Rewrite as a plain
+sentence. Colons are for lists, labels and quotes.
+
+### OSW-05 · HARD · No fake-profound kicker, no summary recap
+
+Cut the final "deep" line that turns the point into an aphorism or a mic drop.
+Do not rewrite it into a better metaphor. Delete it.
+
+Cut "In conclusion", "Ultimately", "Overall" and the closing paragraph that
+restates the piece. End on the last concrete point, the takeaway, or the next
+action.
+
+### OSW-06 · HARD · No importance puffery
+
+Cut "marks a pivotal moment", "underscores its significance", "plays a vital
+role", "stands as a testament", "solidifies its position". State the fact and
+let the reader judge whether it matters.
+
+"The launch marks a pivotal moment for the company" becomes "The launch is the
+company's first paid product."
+
+### OSW-07 · HARD · No `-ing` pseudo-analysis
+
+Cut trailing clauses that pretend to explain meaning: "highlighting",
+"underscoring", "reflecting", "showcasing", "demonstrating". Replace with the
+actual consequence.
+
+"The launch adds file search, highlighting the team's commitment to workflows"
+becomes "The launch adds file search, so users find old drafts without leaving
+the editor."
+
+### OSW-08 · HARD · No weasel attribution
+
+Cut "experts agree", "studies show", "industry reports suggest", "many argue",
+"widely regarded as". Name the source, or cut the claim. If there is no source,
+ask. Never invent one.
+
+### OSW-09 · LOCK · No synonym cycling
+
+If the clear word is right, repeat it. Do not rotate terms for style. "The agent
+reviews the draft. The assistant scores the piece. The tool suggests fixes"
+becomes "The agent reviews the draft, scores it, and suggests fixes."
+
+This matters more in technical writing than anywhere else: a second name for one
+thing reads as a second thing.
+
+### OSW-10 · HARD · Banned lexicon
+
+Never use, in any output: delve · leverage · utilize · facilitate · empower ·
+streamline · robust · cutting-edge · paradigm shift · game changer · tapestry ·
+realm · beacon · multifaceted · meticulous · intricate · paramount ·
+transformative · elevate · embark · supercharge · harness · ever-evolving ·
+seamless · unleash · pivotal.
+
+Use the plain word. "Utilize" is "use". "Leverage" is "use". "Facilitate" is
+"help" or the verb for what actually happens.
+
+Checked by `orc rules lint`.
+
+### OSW-11 · HARD · Banned phrases
+
+Never use: "it's worth noting" · "it's important to note" · "at the end of the
+day" · "when it comes to" · "at its core" · "in today's world" · "in the age
+of" · "in the world of" · "the reality is" · "the truth is" · "in terms of" ·
+"with regard to" · "going forward" · "let's dive in" · "in this article".
+
+Every one of them delays the point by a clause. Delete the clause and keep the
+point.
+
+Checked by `orc rules lint`.
+
+### OSW-12 · PURPOSE · Hedge adverbs earn their place
+
+Cut when they add nothing: just · literally · honestly · simply · actually ·
+truly · fundamentally · importantly · crucially · inherently · inevitably.
+
+Keep one when it carries real uncertainty, a real contrast, or the writer's own
+rhythm. That is the written reason.
+
+### OSW-13 · PURPOSE · Em dash dose cap
+
+This is a **dose rule, not a ban.** The em dash is a real punctuation mark and
+ORC's own documentation uses it.
+
+- Short output (a chat answer, a commit body, a CTA, a label): none.
+- A long document: at most two per thousand words, and only where the dash
+  clearly beats a comma, a period or parentheses.
+- Never as a rhythm crutch, and never in clusters.
+
+`orc rules lint` reports **density**, not presence.
+
+### OSW-14 · LOCK · No rule-of-three padding
+
+Three items only when there are three items. Do not invent a third to complete
+the cadence, and do not drop a fourth to preserve it.
+
+### OSW-15 · HARD · No staccato drama
+
+Cut "X. And Y. And Z.", "That's it. That's the whole thing.", and stacked punchy
+fragments. Use complete sentences. Vary sentence shape only when it helps the
+point.
+
+### OSW-16 · HARD · No rhetorical setup
+
+Cut "What if I told you…", "Think about it:", "Plot twist:", and self-answered
+"Question? Answer." pairs. Make the point.
+
+### OSW-17 · HARD · No interpretive metadiscourse
+
+Cut lines that step outside the subject to tell the reader what to notice: "That
+last part matters more than it sounds", "The key point is", "As you can see",
+"This distinction matters", and a redundant "In other words".
+
+If the point is clear, delete the aside. If it is not, add the fact that would
+make it clear.
+
+### OSW-18 · LOCK · No formatting slop
+
+- No emoji in a heading (checked by `orc rules lint`).
+- No bold sprinkled mid-sentence for emphasis.
+- No heading over a two-sentence section.
+- No bullet list where two sentences of prose read better.
+- No table with one column of real content.
+
+Format follows the content. It does not decorate it.
+
+### OSW-19 · LOCK · Active voice, real actors
+
+"The team shipped it Tuesday" beats "the decision emerged". Never let an
+inanimate thing do a human verb: an architecture does not believe, a module does
+not want, a decision does not emerge.
+
+Passive voice is allowed when the actor is genuinely unknown or genuinely
+irrelevant, and only then.
+
+### OSW-20 · LOCK · The portability test
+
+If a sentence could move unchanged to another project, another company or
+another product, it is filler. Replace it with a fact, a mechanism, a
+consequence, or a judgement specific to this subject. Otherwise cut it.
+
+### OSW-21 · LOCK · Concrete beats abstract
+
+Names, numbers, dates, file paths, commands, error codes and examples beat
+abstractions. "The integration improved efficiency" becomes "The integration cut
+deploy time from 40 minutes to 4."
+
+Protect the specific fact. Never smooth a useful detail into generic importance.
+
+### OSW-22 · HARD · A human's paragraph is not yours to restyle
+
+Never rewrite user-authored prose to match this pack. Preserve the writer's
+vocabulary, bluntness, humour, digressions and level of polish.
+
+This rule beats every other rule in this file. A pack that flattens the human
+voice it was written to protect has failed.
+
+### OSW-23 · HARD · Never invent a specific
+
+No invented number, date, name, version, benchmark or range. No "anywhere from X
+to Y" that nothing measured. No filled-in gap presented as a fact.
+
+If the number is needed and unknown, say it is unknown, or ask.
+
+---
+
+## Not a ban — keep these
+
+Never cut, in the name of this pack:
+
+- A load-bearing caveat about scope, risk or uncertainty (see `delivery.md`, OSD-04).
+- A named source, a file path, a command, an error code, a version.
+- The user's own words, anywhere (OSW-22).
+- A hedge that reports real uncertainty rather than decorating a claim.
+
+**Removing slop leaves a void.** The fix for flat prose is never more bans — it
+is a fact, a mechanism, or a consequence the reader did not have.

package/templates/skills/context-combiner/SKILL.md

@@ -211,4 +211,12 @@ exit code, and never re-derive a state word — the CLI's state words are the on
 state words, and **an exit code is an ANSWER wherever that contract says so, not
 a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
-command you are about to run, out loud, before running it.
+command you are about to run, out loud, before running it.
+
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane context-combiner --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.

package/templates/skills/orc/SKILL.md

@@ -111,6 +111,13 @@ the CLI is unavailable and fall back to `../_shared/config-precedence.md`'s
 documented defaults, out loud. Priorities and families:
 `../_shared/config-precedence.md`.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc --json` names every

package/templates/skills/orc-aftermath/SKILL.md

@@ -152,6 +152,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-aftermath --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-analyze/SKILL.md

@@ -246,6 +246,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-analyze --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-analyze-mini/SKILL.md

@@ -125,4 +125,12 @@ exit code, and never re-derive a state word — the CLI's state words are the on
 state words, and **an exit code is an ANSWER wherever that contract says so, not
 a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
-command you are about to run, out loud, before running it.
+command you are about to run, out loud, before running it.
+
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-analyze-mini --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.

package/templates/skills/orc-boundary/SKILL.md

@@ -243,6 +243,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-boundary --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-brainstorm/SKILL.md

@@ -371,6 +371,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-brainstorm --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-budget/SKILL.md

@@ -242,6 +242,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-budget --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-challenge/SKILL.md

@@ -292,6 +292,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-challenge --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-claude/SKILL.md

@@ -215,6 +215,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-claude --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-diy/SKILL.md

@@ -128,6 +128,13 @@ command you are about to run, out loud, before running it.
 3. The fallback ask is ONE question with two outcomes (`/orc` or stop) —
    never a menu, never a silent fallback.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-diy --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-explain/SKILL.md

@@ -64,6 +64,13 @@ say so and use `../_shared/config-precedence.md`'s documented defaults, out
 loud. Nothing this lane reads is contested, gated or a stop, so it owes no
 preflight line and has no gate to honour.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-explain --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc-explain --json` names every