yaarr

Org-internal engineering standards. Invoke for repo scaffolding and audits, executable quality gates, validation or generation scripts, CI, bug investigation or fixes, regression tests, or configuration of `Cargo.toml`, `rust-toolchain.toml`, `justfile`, `.editorconfig`, `.prettierignore`, `tsconfig.json`, `package.json`, `pnpm-lock.yaml`, `bunfig.toml`, `pyproject.toml`, `uv.lock`, `.python-version`, `lefthook.yml`, or `*.tf`. Also for `axum`, `utoipa`, `async-graphql`, `uv`, `ruff`, `pyright`, `pytest`, `eslint`, `prettier`, or Node package-manager setup (pnpm is the org default). Fully documented: Rust (workspace inheritance, MSRV, `just`, coverage, test tiers, Axum+utoipa, published-crate conventions, async-graphql), Python (uv workspaces, `src` layout, ruff, pyright strict, pytest tiers), TypeScript/Node (tsconfig, multi-context configs, npm scripts), Terraform (workspaces, backend, naming). Bun is a stub; invoke anyway rather than improvising.

Expert guidance for the Model Context Protocol (MCP), the JSON-RPC 2.0 protocol connecting LLM apps to tools and data. Covers official versions 2024-11-05 through 2026-07-28, including modern stateless request metadata, `server/discover`, MRTR, subscriptions, extension negotiation, transports, Resources, Prompts, Tools, and Elicitation, plus legacy initialization, sessions, Sampling, Roots, and Tasks. Also covers the Rust SDK `rmcp` 2.2 and the TypeScript SDK `@modelcontextprotocol/sdk`, including the `pkce-challenge` bundler failure. Use when building or debugging MCP clients, servers, transports, authorization, or SDK integrations. Always invoke for questions mentioning MCP, modelcontextprotocol, `rmcp`, tools/list, tools/call, server/discover, subscriptions/listen, MRTR, resultType, Streamable HTTP, Mcp-Session-Id, or `@modelcontextprotocol/sdk`.

Expert guidance for Qwik (v1 and v2) and its meta-framework — Qwik City in v1, Qwik Router in v2 — covering resumability, components, signals, stores, tasks, context, QRLs, file-based routing, route loaders/actions, middleware, endpoints, layouts, async data (useResource$/useAsync$/Suspense), v1→v2 migration, and deployment. Use whenever someone writes, debugs, or reviews Qwik code, asks about useSignal, useStore, useTask$, useAsync$, routeLoader$, routeAction$, component$, the $ suffix, resumability vs hydration, migrating v1 to v2, server-side data fetching, REST/JSON endpoints, middleware, or deployment. Always invoke for any question mentioning Qwik, Qwik City, Qwik Router, QRL, routeLoader$, routeAction$, useVisibleTask$, useAsync$, noSerialize, or the resumable architecture.

Expert guidance for the Agent Client Protocol (ACP) — the JSON-RPC 2.0 standard connecting code editors/IDEs (Clients) with AI coding agents (Agents), the way LSP connected editors with language servers. Covers v1 (stable) and v2 (draft): initialization and capability negotiation; sessions (new/load/resume/list/delete/close); the prompt turn (`session/prompt`, `session/update`, stop reasons); content blocks; tool calls and permission requests; agent plans; client `fs/*` and `terminal/*` methods; session modes and config options; slash commands; cancellation; MCP server passthrough; extensibility (`_meta`); the stdio transport; the v1→v2 migration; and the official SDKs (Rust, TypeScript `@agentclientprotocol/sdk`, Python, Kotlin, Java). Always invoke for ACP, Agent Client Protocol, editor↔agent integration, Zed external agents, building an ACP Agent or Client, or any `session/*`, `fs/*`, or `terminal/*` protocol method.