ai/directives/sdd/setup.directive.xml Creates or updates specs/README.md — Vision and Scope Graph. Sole owner of the Portal. Idempotent. new project · add scope · change project vision · register scope after discovery designing a specific scope · module decomposition · task scaffolding None ai/directives/sdd/discovery.directive.xml Scope-level discovery session. Creates or evolves specs/[scope]/[scope].spec.md. Branches by scope-type: infrastructure, contracts, library, product. design scope · raw idea for service/SDK/CLI/app · bootstrap infra tooling · refine or pivot existing scope approved spec exists and operator wants module decomposition · bug fix or local refactor · project-level vision change greenfield: none. refine/pivot: specs/[scope]/[scope].spec.md exists ai/directives/sdd/module-decomposition.directive.xml Decomposes a product or library scope into module specs with closed-world entity inventory, public surfaces, DbC contracts (Ports / Adapters / Services). discovery complete · split into modules · build module map · list all entities · produce DbC · Ports and Adapters scope spec missing or not approved · discovery still open · scope-type is infrastructure or contracts · tasks already generated specs/[scope]/[scope].spec.md with scope-type=product or library ai/directives/sdd/task-scaffolding.directive.xml Builds DAG of compact task tickets from scope graph. Each ticket includes BDD, Effective Rules, Verification, Execution Log template. all scope specs ready · break into tasks · build DAG · produce execution plan · scaffold tickets module specs lack contracts · discovery or module-decomp not closed · tasks already generated specs/README.md Scope Graph ✅; coding rule files exist for each language ai/directives/sdd/phase-execution-protocol.xml Execute ONE phase of ONE task ticket, dispatched by sdd-execute orchestrator. Read only what the phase needs; write only Target Files; emit typed Handoff for next phase / audit. orchestrator dispatches phase · phase ID + ticket path provided in prompt operator invokes directly without orchestrator · no phase ID ticket has section 2 Phases Overview + section 3 Phases block for target phase ID; prior-phase Handoffs (if any) recorded in current Round ai/directives/sdd/audit.directive.xml Post-execution verification. Compares spec ↔ ticket ↔ code. Detects drift, gaps, rules violations. Output: ephemeral findings routed to spec/ticket. audit · drift detection · post-implementation review · verify implementation · end of epic before merge no executed tasks · Execution Log empty · no spec to compare spec exists; ticket with non-empty Execution Log; code committed typecheck test lint format ai/directives/coding/result-conventions.xml ESLint enforcement of Result pattern conventions: no second generic, no object literals, no isErr short-circuit, no bare throw unknown. Target Files use Result from @tessell/core/result · task touches error-handling code · task adds new DML / service methods Config-only task; no Result usage in target files Before writing or reviewing any file that returns or propagates Result lint check-command ai/directives/coding/typescript-rules.xml Writing code in the chosen language: typing, DbC, patterns, anti-patterns. Target Files include source code files (not config) Config-only task; infra-setup task without code files Before editing or creating any source code file typecheck check-command ai/directives/coding/svelte5-runes.xml Writing Svelte 5 components with runes ($state, $derived, $effect, $props, $bindable). Inherits typescript-rules; adds Svelte-specific reactivity, template syntax, component structure. Prevents React-pattern code in .svelte files. creating .svelte file · writing Svelte component · using runes · .svelte.ts module pure TypeScript without Svelte · React/Vue project · backend server code Before editing or creating any .svelte, .svelte.ts, or .svelte.js file. Inherits from typescript-rules — read both. typecheck check-command Parent directive: inherits all TypeScript rules for language baseline. SvelteKit projects also activate sveltekit-rules (inherits from this directive). ai/directives/coding/sveltekit-rules.xml Writing SvelteKit applications: file-based routing (+page, +layout, +server), server load functions, form actions, hooks, adapters, $app modules. Inherits svelte5-runes + typescript-rules transitively. creating SvelteKit route · load function · form actions · hooks.server.ts · server/client boundary standalone Svelte without SvelteKit · pure component library · non-SvelteKit project Before writing SvelteKit route files or server logic. Inherits from svelte5-runes — read both. typecheck check-command Parent directive: inherits all Svelte 5 runes rules. Transitive parent: inherits TypeScript rules through svelte5-runes. ai/directives/testing/common.xml Shared testing core inherited by every runner-specific directive: contract boundary, case flow, phase anchors, unified context + factory, BDD mapping, snapshot operator-confirm, file budget. any runner-specific testing rule activates no test files in scope Auto-read whenever node-test or vitest-rules activates. Runner-specific files only state deltas. test check-command ai/directives/testing/vitest-rules.xml Writing tests on Vitest runner. Target Test Files present AND stack uses Vitest Stack uses a different test runner; no test files in scope Before writing or modifying test files. Inherits testing-common. test check-command Parent directive: read first for case flow, anchors, unified context, BDD mapping. ai/directives/testing/node-test.xml Writing tests on node:test runner. Target Test Files present AND stack uses node:test Stack uses a different test runner; no test files in scope Before writing or modifying test files. Inherits testing-common. test check-command Parent directive: read first for case flow, anchors, unified context, BDD mapping. ai/directives/testing/playwright-cli.xml Exploring web apps through Playwright CLI: AX Tree vision, aria snapshots, screenshots, trace viewer, codegen. Gives the agent eyes and hands for browser exploration. developing UI component · building a page · verifying visual layout · debugging failing e2e test · capturing aria snapshots pure backend logic · CLI command implementation · API endpoint without UI BEFORE writing any e2e test — explore the page first. Also when an e2e test fails and the agent needs to see what rendered. test check-command Transition to playwright-e2e when exploration complete. ai/directives/testing/playwright-e2e.xml Writing Playwright E2E tests: aria-snapshot-first contracts, role-based locators, fixture-based POM, auth via storageState, network mocking. writing e2e test · creating browser test · adding Playwright spec · testing user flow unit test · integration test without browser · exploration not done (use playwright-cli first) AFTER playwright-cli exploration. Before writing Playwright spec files. test check-command MUST run playwright-cli exploration first. ai/directives/testing/storybook-usage.xml Using Storybook MCP tools: reading manifests (component docs, props, stories), writing stories, running tests, self-verifying component rendering. developing UI component · using design system · creating story · fixing component bug · verifying component renders pure backend/CLI logic · no Storybook · MCP not installed (use storybook-setup first) Whenever working with UI components — BEFORE writing code, call MCP tools to check documented props. test check-command MUST have Storybook + MCP running. If unreachable, invoke storybook-setup. ai/directives/testing/svelte-testing.xml Testing Svelte 5 components: .svelte.test.ts extension, $effect.root isolation, flushSync for DOM, mount/unmount, @testing-library/svelte. Inherits node-test + vitest-rules. writing Svelte component test · testing runes · mounting Svelte component · Storybook interaction test for Svelte pure TS logic test without runes · E2E test with Playwright · non-Svelte project Before writing .svelte.test.ts. Inherits from node-test.xml and vitest-rules.xml. test check-command Inherits general testing rules (phase anchors, learning briefs, contract coverage). Inherits Vitest-specific rules (unified context, mock discipline). Runes knowledge required (.svelte.test.ts, $effect.root, flushSync). ai/directives/infra/eslint-setup.xml Configuring a linter: severity policy, autofix, config format, formatter integration. Task configures linter · installs linter · sets lint rules Coding/testing task that only RUNS lint, does not configure it Before writing linter config or modifying lint rules lint check-command ai/directives/infra/git-setup.xml Configuring VCS: ignore baseline, branches, commits, hooks, secrets discipline. Task bootstraps repo · configures VCS ignore file · sets up hooks · commit convention Task only commits code changes (does not configure VCS itself) Before writing VCS ignore file or configuring hooks ai/directives/infra/nodejs-npm-setup.xml Runtime + package manager setup: version pinning, single package manager, module system, mandatory check script. Task writes package manager manifest · runtime version file · sets engines · chooses package manager Task does not touch package manager manifest or runtime config Before writing package manager manifest or runtime version file ai/directives/infra/storybook-setup.xml Installing Storybook + MCP server: agentic init, MCP addon, Vitest addon, agent registration, AGENTS.md update. Bootstraps component development environment. install Storybook · add Storybook to project · configure MCP server · bootstrap UI toolchain no UI components · Storybook already installed + MCP confirmed running When project needs Storybook for first time. Follow agentic init: npx storybook@latest init. test check-command After setup (MCP running, manifest accessible), transition to storybook-usage.