bostonaholic
- 151 skills
- 0 followers
- 11 repo stars
- 2 days ago last updated
- ▌ Opening Prs · bostonaholic bundleOpens a draft pull request for the current branch, or refreshes the body of its open PR after a push, from the branch diff and an optional inputs file. Use when the user says "open a PR", or when the user explicitly asks to open or refresh a pull request for the current branch. Never infer from finished work or passing checks. Not for a gh stack layer; use stacking-prs. Not for screenshots; use attaching-pr-screenshots.
- ▌ Updating Changelogs · bostonaholic bundleAdds user-facing bullets under the Unreleased section of an existing Keep a Changelog CHANGELOG.md for the commits since the last release, skipping changes the section already covers. Use when the user says "update the changelog", or when the user explicitly asks to add changelog entries. Never infer from a finished change. Not for summarizing shipped work; use summarizing-shipped-work.
- ▌ Writing Commit Messages · bostonaholic bundleWrites a git commit message for staged changes with a 50/72 subject and body, a Conventional Commits type, footers, and issue citations, keeping any subject, type, or body line the caller fixes byte for byte. Use when the user says "write a commit message", or when the user explicitly asks for a commit message. Never infer from staged changes or a request to commit.
- ▌ Making Code Agent Friendly · bostonaholic bundleAudits, reviews, and refactors code so many coding agents can change it in parallel without merge conflicts: few shared files, strong boundaries, explicit contracts, fast checks. Also lists the shared files a design or diff edits and flags any file every change appends to. Use when the user says "make this agent-friendly" or "check shared files", or when asked to make code agent-friendly, find where parallel agents will collide, or name the shared files a feature edits or the files every change appends to. Not for general code review; use reviewing-code.
- ▌ Updating Bostonaholic Skills · bostonaholic bundleUpdates the bostonaholic skills plugin installs (Claude Code, Codex, the Cursor plugin clone) and the skill copies in the Antigravity, OpenCode, Cursor, and Grok Bot skill directories to the latest release tag. Use when the user explicitly asks to update the bostonaholic skills. Never infer from an outdated skill or a version mismatch. Not for installing; use INSTALL.md.
- ▌ Verifying Production Changes · bostonaholic bundleVerifies a merged change took effect in production by revision ancestry and cohort sampling, and reports a bound over sampled requests rather than "fully deployed". Use when the user says "is it live in prod?", or when asked to confirm or report whether a merged change is live or deployed in production, before answering, even when the build-info, status, or deploy output is already in hand; also when gating on a deploy reaching the fleet, sequencing deploys, or verifying a one-time migration, backfill, or cleanup. Not for CI or build state.
- ▌ Writing Acceptance Criteria · bostonaholic bundleWrites or rewrites acceptance criteria until each is provable: one observable outcome with a named check that can fail. Use when the user says "write acceptance criteria", or asks to write, rewrite, or tighten acceptance criteria or a definition of done. Not for proving work meets them; use proving-claims.
- ▌ Redesigning From First Principles · bostonaholic bundleRedesigns an existing design as if a new requirement had been a founding assumption, then propagates it to every reference and delivers it in working increments. Use when the user explicitly asks to redesign for a requirement or from first principles. Never infer from a feature request. Not for redoing an attempt; use redoing-implementations.
- ▌ Testing Behavior Not Implementation · bostonaholic bundleChecks each test asserts what the code's users can observe, so it fails when that behavior breaks and passes when only internals change. Use when the user says "test behavior, not implementation", or when writing, changing, or keeping a test. Not for auditing a whole suite; use auditing-tests.
- ▌ Redoing Implementations · bostonaholic bundleRebuilds the current implementation from scratch as the simplest design that satisfies what was learned, after the user approves the design. Use when the user explicitly asks to redo the work, start over, scrap the approach, or rewrite it more simply. Never infer from a failing or complex implementation. Not for fitting a new requirement into an existing design; use redesigning-from-first-principles.
- ▌ Learning From Mistakes · bostonaholic bundleCodifies the latest correction or mistake in the conversation as a short imperative rule in the project or global CLAUDE.md or AGENTS.md and, for a project lesson, proposes the highest check that makes the mistake impossible, after the user approves. Use when the user says "learn from this mistake", or when the user asks to learn from a mistake, remember a lesson for next time, add a rule to CLAUDE.md, make a mistake impossible, or not repeat a behavior. Not for a whole session; use reflecting.
- ▌ Writing System Prompts · bostonaholic bundleWrites and reviews system prompts for AI tools, agents, chatbots, and LLM products using a fixed section order and a quality checklist. Use when the user says "write a system prompt", or when drafting a system prompt or auditing one for missing stop criteria, tool rules, constraints, or examples. Not for compressing an existing prompt; use improving-prompts.
- ▌ Attaching Pr Screenshots · bostonaholic bundleUploads local images and short videos (mp4, mov, webm) through GitHub's attachment pipeline and writes one verified Screenshots section into a PR body. Use when the user says "attach screenshots to the PR", or when the user explicitly asks to add or attach screenshots to a PR. Never infer from local images. Not for capturing screenshots; use capturing-screenshots.
- ▌ Drawing Mermaid Diagrams · bostonaholic bundleWrites, edits, and debugs Mermaid diagrams (flowchart, sequence, class, state, ER, Gantt, pie, mindmap, timeline, quadrant, git graph, XY, Sankey, architecture, journey, kanban, block). Use when the user says "draw a diagram", or when the user asks for a diagram, flowchart, ERD, or Mermaid code, or when a Mermaid diagram fails to parse or render.
- ▌ Reconciling Documentation · bostonaholic bundleSweeps a repository's documentation for claims that disagree with its code and tests, decides which side is wrong for each, and fixes it after approval. Use when the user asks to reconcile, audit, or fix documentation that has drifted from the code.
- ▌ Summarizing Friction Logs · bostonaholic bundleAggregates frog friction logs across every repository in a workspace plus the global log into one prioritized dashboard. Use when the user says "show the friction dashboard", or when asked for the friction dashboard, all known friction or papercuts across repos, to list friction logs, or to decide which friction to fix first.
- ▌ Summarizing Shipped Work · bostonaholic bundleSummarizes the user's merged GitHub PRs for a timeframe into a grouped, linked shipped-work report with highlights, and offers to update a brag document. Use when the user says "what shipped?", or when asked what the user shipped (this week, last month, a quarter, since a date), for a status update, or to update a brag doc.
- ▌ Auditing Agent Token Usage · bostonaholic bundleAudits recent Claude Code and Codex session logs for token and context cost: model routing, inherited subagent models, long sessions, compactions, oversized tool results, and unused MCP servers. Use when the user says "audit token usage", or when asked about agent token usage, context costs, session length, model routing, or cost efficiency.
- ▌ Diagnosing React Code · bostonaholic bundleRuns the react-doctor scanner on a React package, fixes its error diagnostics, and re-runs until none remain. Use when the user says "health-check the React code", or when React components or hooks changed, when finishing a React feature or bug fix, or when asked to health-check React code.
- ▌ Reviewing Design Docs · bostonaholic bundleReviews a technical design document or RFC adversarially in fresh-context read-only subagents, one per lens, (coverage, decisions, edge cases, consistency, risks, citations, scope) and returns one merged report with a verdict. Use when the user says "review this design doc", or when asked to review a design doc, RFC, or technical design. Not for code diffs; use reviewing-code.
- ▌ Simplifying Ruby Code · bostonaholic bundleRewrites over-engineered Ruby and Rails classes (stateless service objects, behaviorless value objects, class-method-only classes, deep inheritance, needless metaprogramming) as Data, Struct, Hash, modules, or pure functions, after finding every caller and getting a green test baseline, or reports findings when asked to review. Use when the user says "simplify this Ruby", or when asked to refactor, simplify, review, or cut boilerplate from a Ruby or Rails class, value object, service object, gem, or branch diff (hand-written initialize, readers, ==, eql?, or hash; call-only classes; Struct vs Data), or when tests need heavy mocking. Not for a broad Rails tech-debt audit; use auditing-rails-tech-debt.
- ▌ Visualizing Codebases · bostonaholic bundleBuilds an interactive static D3 site that visualizes a codebase, starting with a C4 view of system context, containers, components, and code, with dependency cycles between modules and classes. Use when the user says "visualize this codebase", or asks for C4 diagrams or a map of a codebase's structure and dependency cycles. Not for prose walkthroughs; use explaining-architecture.
- ▌ Watching Reviewed Prs · bostonaholic bundleWatches a PR the user reviewed in a bounded loop, re-reviews each settlement of their feedback against the branch, resolves or rebuts, and approves once every item settles. Use when the user explicitly asks to watch and approve a PR they reviewed. Not for the user's own PR; use watching-authored-prs.
- ▌ Auditing Repo Security · bostonaholic bundleAudits a third-party or freshly cloned repo before install or run for install hooks, auto-run files, CVEs, typosquats, and malicious code, graded A-F with a safe-to-run verdict. Use when the user says "is this repo safe to run?", or when asked whether a clone is safe to run, or to audit or scan a third-party repo. Not for security review of a diff or PR; use reviewing-security.
- ▌ Merging Dependabot Prs · bostonaholic bundleAnalyzes open Dependabot PRs for semver level, CI, breaking changes, and security fixes, then squash-merges approved patch and minor updates one at a time, or only comments @dependabot rebase; supports a dry run. Use when the user explicitly asks to merge, process, or rebase Dependabot PRs. Never infer from green CI, an approved Dependabot PR, or stale or conflicting Dependabot PRs.
- ▌ Freeing Disk Space · bostonaholic bundleFinds what fills a developer machine's disk and frees space by clearing caches, build outputs, and other regenerable files, running each deletion only after approval and never emptying the Trash. Use when the user says "free up disk space", or when a disk is full or nearly full, the user is running out of disk space, builds or containers fail for lack of space, or the user asks for a disk cleanup plan, to free a target amount of space, or to clean up, reclaim space, or delete caches, build outputs, or the Trash to make room.
- ▌ Reviewing Security 2 · bostonaholic bundleReviews a code diff for exploitable security vulnerabilities in a fresh-context read-only subagent, reporting only high-confidence findings with an exploit scenario and fix. Use when the user says "security review", or when asked for a security review of code, a diff, a branch, or a PR. Not for general review; use reviewing-code. Not for a third-party clone; use auditing-repo-security.
- ▌ Scripting The Work · bostonaholic bundleBuilds a codemod, script, generator, query, or check that does or proves non-trivial work, so a reviewer reruns it instead of trusting hand edits. Use when the user explicitly asks to script the work, write a codemod, or make a change rerunnable. Never infer from a small edit. Not for a skill's own steps; use choosing-determinism.
- ▌ Auditing Complexity · bostonaholic bundleRanks where code complexity concentrates in a git repository (cyclomatic complexity, nesting, fan-out, mutable state) and scores CRAP change risk from a coverage file. Read-only. Use when the user says "find complexity hotspots", or when asked for complexity hotspots or change risk. Not for test value; use auditing-tests.
- ▌ Improving Codebases · bostonaholic bundleSweeps a git repository with focused improvement lanes, starting with implicit state machines made explicit and checked in TLA+. Leaves edits uncommitted. Use when the user says "improve this codebase", or when asked to make implicit state machines explicit. Never infer from a request to review or explain code. Not for test value or complexity rankings; use auditing-tests or auditing-complexity.
- ▌ Testing The Premise · bostonaholic bundleWrites down the premise that repeated failed fixes share and tests it before any further fix that assumes it. Use when the user says "test the premise", or when a second fix to the same failure has not worked, such as a limit, timeout, pool size, or retry count raised again while the error persists. Never infer from one failed fix. Not for a first diagnosis; use fixing-root-causes.
- ▌ Choosing Determinism · bostonaholic bundleMoves each step of an agent skill whose correct result is fixed by its inputs into a script the skill runs, leaving the model only judgment. Use when the user says "script the deterministic steps", or when creating a skill, or adding or changing its steps, commands, or parsing. Not for trimming a skill; use cutting-skills.
- ▌ Untangling Codebases · bostonaholic bundleRefactors a whole codebase in one pass so each change lands in one place: catalogs hidden links, needless links, surplus code, and special cases, redesigns to remove their shared causes, and repeats until nothing worth fixing is left. Use when the user says "untangle this codebase", or when asked to refactor a whole codebase so changes land in one place. Never infer from a bug fix or feature request. Not for one new requirement; use redesigning-from-first-principles.
- ▌ Capturing Screenshots · bostonaholic bundleCaptures deterministic, visually verified screenshots of a running web or native app (named screens, states, viewports, dark mode) with a manifest. Use when the user says "take screenshots", or when asked for screenshots of an app or its screens. Not for attaching images to a PR; use attaching-pr-screenshots.
- ▌ Stacking Prs · bostonaholic bundleSplits a large change into stacked pull requests with GitHub's gh stack CLI. Use when the user says "stack PRs" or "create a PR stack", or when a change is too big to review as one PR, has dependent parts, or overlaps the same author's open PRs, or when creating, updating, syncing, merging, or recovering a gh stack stack.
- ▌ Auditing Tests · bostonaholic bundleAudits a test suite, or a named part, for low-value tests and marks each retain, fix, consolidate, or delete with verified removal evidence. Read-only. Use when the user says "audit the tests", or when asked to audit tests for redundant, junk, or low-value tests. Not for code complexity; use auditing-complexity.
- ▌ Reviewing Code 2 · bostonaholic bundleReviews a code diff (PR, branch, commit range, working tree, or a diff already in the conversation) in a fresh-context read-only subagent, because a session holding the conversation is a biased reviewer, posts its Conventional Comments findings inline and its APPROVE, REQUEST CHANGES, or COMMENT verdict to the pull request when one exists, and returns a short summary. Use when the user says "code review", or when asked to review code, a diff, or a PR, including a pasted diff, a .diff or .patch file, or a diff shown earlier; never review it inline. Not for design docs; use reviewing-design-docs. Not for a security-focused review; use reviewing-security.
- ▌ Configuring Zsh · bostonaholic bundleChooses the zsh startup file (.zshenv, .zprofile, .zshrc, .zlogin, or a custom plugin under ZSH_CUSTOM) for a configuration change and edits the dotfiles repo source behind the symlink. Use when the user says "update the zsh config", or when adding or moving environment variables, PATH entries, aliases, functions, setopt or zstyle options, or completions in zsh config.
- ▌ Modernizing Prs · bostonaholic bundleBrings the checked-out PR up to date after checking its intent against base changes. MODERNIZE rebases, re-runs checks, and force-pushes with a lease; REWORK or CLOSE stops. Use when the user says "modernize this PR", or when the user explicitly asks to bring a PR up to date or rebase it, or when landing-prs or watching-authored-prs calls it on a conflict. Never infer from a behind branch alone.
- ▌ Removing Comments · bostonaholic bundleRemoves every source comment outside a short keep list, flagged by a fresh-context reviewer, and, with approval, fixes root causes and encodes enforceable constraints in types, tests, or lint. Use when the user explicitly asks to remove or clean up code comments. Never infer from a diff containing comments.
- ▌ Writing Playbooks · bostonaholic bundleWrites a playbook an on-call agent can run from the session that resolved an alert or incident. Use when the user says "write the playbook", "turn this into a playbook", or "make a runbook for this". Not for session learnings; use reflecting.
- ▌ Fixing Root Causes · bostonaholic bundleTraces a bug or failure to its root cause and fixes it there instead of patching the symptom. Use when the user says "find the root cause", or when debugging a crash, failing test, regression, or "fails after restart" bug, or when a fix would add a guard, retry, or workaround to silence an error.
- ▌ Writing Prose 2 · bostonaholicWrites and edits prose for people in a plain, conversational, short house style with no em dashes. Use when drafting or revising documentation, READMEs, explanations, blog posts, or other human-facing prose. Not for prompts written for agents; use writing-system-prompts or composing-agent-prompts.
- ▌ Getting Started · bostonaholicUse this in the first conversation with a new owner, to set up a chief of staff bot.
- ▌ Grooming Backlogs · bostonaholicGrooms a GitHub Projects backlog: verifies issues against the code, ranks and clusters them, and plans milestone, link, and closure changes, or promotes issues to Ready. Proposes tracker changes; each requires approval. Use when asked to groom, triage, or prioritize a backlog, or to promote issues to Ready.
- ▌ Improving Prompts · bostonaholicCompresses and clarifies an existing LLM prompt through concept elevation, verifying that no original instruction is lost. Use when the user supplies a prompt or prompt file and asks to improve, tighten, optimize, or refine it. Not for writing a new prompt; use writing-system-prompts.
- ▌ Composing Agent Prompts · bostonaholicComposes a self-contained, source-cited task prompt for another coding agent to execute in a target repository, without running the task. Use when the user asks to write, draft, or hand off a prompt, brief, or task spec for another agent. Not for system prompts; use writing-system-prompts.
- ▌ Saving A Job As A Skill · bostonaholicUse after running a job cleanly by hand, when turning it into a reusable skill, or when reviewing an existing skill that keeps producing inconsistent results.
- ▌ Conducting Deep Research · bostonaholicConducts source-backed, goal-directed research that combines a scholarly evidence review with an institution, company, or funding map. Use when a request needs both an evidence review and an organization or funding map. Not for quick lookups or general research write-ups.
- ▌ Auditing A Bot At 30 Days · bostonaholicUse monthly, or when a bot seems lazy, noisy, or ignored, to decide from run history whether each of its routines should stay, be rewritten, or be cut. Report only; changes nothing.
- ▌ Running Founder Office Hours · bostonaholicWhen a founder or CEO brings a product idea, strategic bet, pricing, focus, hiring, fundraising or kill decision and wants a hard-nosed startup-advisor pressure test (adapted from YC-style office hours in garrytan/gstack).
- ▌ Being Extremely Fucking Brief · bostonaholicKeeps every reply to the user to three lines or fewer, with no preamble, restated question, recap, or closing offer. Use when about to reply to the user: load it before every reply in every session, including plain questions, recommendations, and comparisons, even when no other skill applies.
- ▌ Running Efficient Recurring Work · bostonaholicUse when building, running, or auditing any recurring routine or multi-step workstream (monitors, digests, briefs, audits), to cut wasted reads, repeated checks, and restarts while keeping quality.
- ▌ Checking Live Status Before Review · bostonaholicUse right before sending a person any item for review, approval, or a decision (a PR, issue, draft, deploy, or approval request), so the ask reflects the item's live state and not stale memory.
- ▌ Running Unattended Routines And Triggers · bostonaholicUse when creating or editing a scheduled routine or event trigger that runs while nobody is watching, so it never stalls on an approval, never fires on noise, and is tested before it is trusted.
- ▌ Team · bostonaholic bundleUse for the Team pipeline only on explicit request. Never infer from ordinary coding work. Runs QRSPI or a leading route.
- ▌ Team Structure · bostonaholic bundleUse for breaking reviewed designs into verified implementation slices.
- ▌ Version Bump · bostonaholicUse for version bumps on explicit request or as the pre-merge step of a PR land. Never infer from finished, reviewed, green, or draft-ready work. Assigns SemVer.
- ▌ Create Team Skill · bostonaholicUse for creating or revising Team skills. Defines structure, catalog, and validation.
- ▌ Team Worktree · bostonaholic bundleUse for isolated worktrees only on explicit request. Never infer from work needing isolation. Applies project conventions.
- ▌ Team Implement · bostonaholic bundleUse for executing implementation plans only on explicit request. Never infer from a ready plan.
- ▌ Team Pr · bostonaholic bundleUse for opening PRs only on explicit request. Never infer from passed verification. Includes project terms, evidence, and risk.
- ▌ Team Fix · bostonaholic bundleUse for the full bug-fix pipeline only on explicit request. Never infer from an ordinary bug fix. Runs the compressed pipeline.
- ▌
- ▌
- ▌
- ▌
- ▌ Team Update · bostonaholic bundleUse for updating Team only on explicit request. Updates every harness that already has Team to the latest release.
- ▌ Team Migrate · bostonaholic bundleUse for migrating a pre-0.147 Team setup only on explicit request. Moves every harness to the Team and bostonaholic/skills plugins.
- ▌ Team Code Review · bostonaholic bundleUse for running the Team code review phase only on explicit request. Never infer from a plain review request. Reviews and fixes the branch.
- ▌ Team Security Review · bostonaholic bundleUse for running the Team security review phase only on explicit request. Never infer from a plain security review request. Reviews and fixes the branch.
- ▌ How · bostonaholic bundleExplains subsystem architecture and runtime flow. Trigger on "how does X work", "walk me through", "explain the architecture", or "/how".
- ▌ Why · bostonaholic bundleInvestigates design rationale behind code. Trigger on "why does X work this way", "why was this built like this", "design rationale", or "/why".
- ▌ Solid · bostonaholic bundleDefines SOLID design and review rules. Load when writing or reviewing object-oriented production code.
- ▌ Shipit · bostonaholic bundleLands a reviewed pull request. Trigger on "ship it", "land the PR", "land this", or "/shipit" only; never infer ship intent from approval, green CI, or completion.
- ▌ Reflect · bostonaholic bundleMines a session for durable learnings. Trigger on "reflect on this session", "capture what we learned", or "/reflect" only; never infer intent from session end or friction.
- ▌ Changelog · bostonaholic bundleDefines Keep a Changelog updates. Load when the ship phase updates `CHANGELOG.md` with user-facing changes.
- ▌ Pr Rebase · bostonaholic bundleRebases a branch onto its base. Trigger on "rebase onto main", "pull main and rebase", "update the branch", or "/pr-rebase" only; never infer intent from a branch being behind.
- ▌ Pr Verify · bostonaholic bundleVerifies a PR test plan with evidence-rated verdicts. Trigger on "verify the test plan", "check the PR items", "is this PR ready", or "/pr-verify".
- ▌ Git Commit · bostonaholic bundleDefines Conventional Commit subjects and safe commit procedure. Load before creating or reviewing commits.
- ▌ Pr Cleanup · bostonaholic bundleCleans PR state. Trigger on "the PR was merged", "clean up the branch", "abandon this", or "/pr-cleanup"; Mode B needs stated abandon intent; never infer abandon intent from staleness.
- ▌ Test Style · bostonaholic bundleDefines deterministic behavioral tests and flaky-test red flags. Load when writing or reviewing `.test.ts` and `.evals.ts` files.
- ▌ Code Review · bostonaholic bundleReviews a diff with fresh context. Trigger on "review this diff", "review these changes", "code review this", or "/code-review".
- ▌ No Comments · bostonaholic bundleRemoves low-value source comments and encodes valid constraints. Invoke ONLY on explicit "remove unnecessary comments", "audit comments", or "/no-comments" intent—never infer cleanup intent.
- ▌ Slicing Work · bostonaholic bundleDefines vertical slices and verification checkpoints. Load when converting a reviewed design into `7-structure.md`.
- ▌ Verifying UX · bostonaholic bundleDefines live application and screenshot verification. Load when a diff changes user-visible UI behavior.
- ▌ Finding Files · bostonaholic bundleLocates files by naming, structure, and imports. Load for read-only discovery when exact paths are unknown.
- ▌ Groom Backlog · bostonaholic bundleGrooms a project backlog and proposes tracker changes. Trigger on "groom the backlog", "groom the board", "clean up the backlog", or "/groom-backlog"; changes require user approval.
- ▌ Nested Agents · bostonaholic bundleDefines safe nested-agent dispatch and fallback. Load before agents spawn read-only scouts or cross-model couriers.
- ▌ Writing Prose · bostonaholic bundleDefines plain-language prose rules. Load when writing or assessing documentation in strict or STE-flavored modes.
- ▌ Pr Screenshots · bostonaholic bundleAttaches local images to a PR body. Invoke ONLY on explicit intent: "add screenshots to a PR", "attach an image to a PR description", or "/pr-screenshots"; never infer it from images on disk.
- ▌ Qrspi Workflow · bostonaholic bundleDefines QRSPI phases, artifacts, gates, and state transitions. Load when routing or resuming Team pipeline work.
- ▌ Reviewing Code · bostonaholic bundleDefines adversarial code review and evidence-based findings. Load when reviewing a diff without author context.
- ▌ Decision Making · bostonaholic bundleDefines a decision method based on reversibility and risk. Load when choosing among viable options or resolving a consequential trade-off.
- ▌ Pr Open Comments · bostonaholic bundleTriages unresolved PR review comments. Trigger on "address PR comments", "triage PR feedback", "handle the comments", or "/pr-open-comments"; never infer triage intent from unresolved comments.
- ▌ Product Thinking · bostonaholic bundleDefines product-need lenses. Load when questioner, design-author, or structure-planner validates demand and scope.
- ▌ Systems Thinking · bostonaholic bundleDefines system-boundary, feedback, and dependency analysis. Load during research, design, structure, or planning.
- ▌ Tracking Tickets · bostonaholic bundleDefines tracker status transitions and closing rules. Load when a pipeline run is linked to a ticket.
- ▌ Authoring Designs · bostonaholic bundleDefines the design-document procedure. Load when drafting or revising `6-design.md` for adversarial review.
- ▌ Reviewing Designs · bostonaholic bundleDefines adversarial design review and verdicts. Load when a fresh-context reviewer evaluates `6-design.md`.