[ SECTION / 001 ]
11ROOMS · ONE PER TURN
ELEVEN
DEV SENIORS
/// one craft per senior; in a turn, only one comes in
[ SECTION / 002 ]HOW A ROOM ENTERS
You do not switch packs the way you switch an editor profile. You write the work. Alfred reads the sentence, sometimes a file at the root, and lights one room. The other ten do not travel this turn. Skills from rooms you enabled stay in the menu, in case the craft turns mid-conversation.
The radar looks for whole words, not fragments. «solid» lights Clean Code; «solidarity» does not. A substring would wake the wrong senior, which is worse than waking none: the model would get context you did not ask for.
If two rooms score the same, the name that comes first in the alphabet wins. Sometimes devops beats web. Not because it matters more: because the tie needs a rule you can predict. Below are the eleven. Walk into yours: when it enters, a case, and the border with its sister.
001securitySecurityFires when the turn smells like risk: audit this repo, a sonar-project.properties at the root, CVE, secrets or OWASP. «audit the security of this repo» injects the defensive context and the model pairs an OWASP pass with a real reading of the code. Each finding arrives with severity, file:line, an attack story and a minimum fix. Border with Compliance: Security looks at attackers, Compliance looks at duties. A Security finding cites file and line; a Compliance finding cites a GDPR article, a WCAG criterion or an SPDX id, and never invents the reference.002ai-agentsAI AgentsFires when you ask to parallelise agent work: review these PRs, in parallel, worktrees, fan-out. /fanout splits the task, estimates cost from the harness price table, assigns a cheap model to each unit and a collector merges results with a merge protocol. Border with DevOps / Infra: AI Agents orchestrates pi agents inside your session; DevOps orchestrates machines, containers and pipelines outside it.003docsDocsFires on «document this», «adr», «changelog», «this README». /docs-audit . classifies each page by Diátaxis mode, flags mixed modes and snippets that no longer run. Border with Escritura (ES): Docs decides which question each page answers and in which mode; the sister watches that the Spanish on that page obeys the house rules.004escritura-esEscritura (ES)Fires on «fix this text», «review the wording», accents, English-Spanish translation. /revision-es README.md edits in place, shows the diff and explains the applied rule only when the change is not obvious, keeping the author's voice. Border with Docs: it does not reorganise knowledge or judge structure; its ground is grammar, spelling and register, house rules included.005clean-codeClean CodeFires on «refactor», «review this PR», technical debt, SOLID, names that lie. /refactor src/foo.ts plans behaviour-preserving steps, one by one; if the code that matters has no tests, it writes characterisation tests first. Border with QA / Testing: Clean Code judges design and debt, QA judges risk and evidence.006web-fullstackWeb / FullstackFires on api, endpoint, scaffold, Astro, Playwright, an astro.config.mjs or a Program.cs at the root. /scaffold-crud invoices generates a migration, a validated API, views with states and tests, copying the repo's patterns instead of imposing its own. Border with Landing Design: Web builds the product that works; Landing sharpens the page that persuades.007complianceComplianceFires on GDPR, cookies, licences, copyleft, accessibility. /privacy-check src/forms/signup maps the personal-data flow and flags consent, third parties and retention, with the exact reference for each duty. Border with Security: Compliance states its limits (this is not a law firm) and sends high-risk cases to professional review.008landing-designLanding DesignFires on landing, hero, conversion, CTA, a screenshot or a mockup. /landing-review inspects the rendered page on desktop and mobile. Source alone is not evidence. Border with Web / Fullstack: Landing never ships without leave, and Web never judges copy without looking at the rendered page.009devops-infraDevOps / InfraFires on Dockerfile, compose, a 502 in production, «deploy», certificates, kubernetes. /diagnose-502 finds the failing layer with real checks. Restart is never the first diagnostic step. Border with Data / Analysis: the production database is DevOps; the slow query that needs EXPLAIN is Data.010data-analisisData / AnalysisFires on csv, sql, dashboard, «this query is slow», notebooks, dbt. /explore data.csv profiles the file, cleans with a reason for each step and delivers findings with numbers that trace back to a query that runs again. Border with DevOps: Data does not raise infrastructure and DevOps does not interpret distributions.011qa-testingQA / TestingFires on a test plan, coverage, «this test fails sometimes», contract testing. /flaky classifies the smell, delivers a deterministic reproduction and fixes the cause. A flake is a suite bug; retries never silence it. Border with Clean Code: 100% coverage is not its religion, and design pain without demonstrated risk is left to the sister.