jmagar

Use when the user wants to live-test an Android APK end-to-end on an emulator/device and get a works/doesn't-work + UI/UX report — driving the real app, not writing test code. Triggers: "test my Android app", "QA this APK", "run the app on the emulator and tell me what breaks", "click through every screen", "review the app's UX", "does my APK work", "test the built APK". Installs/launches the APK, enumerates screens from the accessibility tree, exercises each feature via adb (tap/type/swipe/launch), watches logcat for crashes/ANRs, captures screenshots + UI dumps, and emits a structured report. Primary path is direct local adb; optional richer path via claude-in-mobile. Sibling of web-app-testing and desktop-app-testing (shared report format). Does NOT fire for: building/coding an Android app (use claude-android-ninja / jetpack-compose-expert), iOS, or unit tests.

Use when the user wants to live-test a built Windows desktop application (.exe) end-to-end inside the agent-os Windows 11 VM and get a works/doesn't-work + UI/UX report — launching the real binary and driving it, not writing test code. Triggers: "test my Windows app", "QA this .exe", "run my desktop build on agent-os and tell me what breaks", "click through the app", "review the desktop app's UX", "does my exe work", "test the built binary in the Windows VM". Gets the .exe into the VM, launches it, enumerates controls from the UI Automation tree, drives every feature (click/type by element), watches for crashes/hangs/error dialogs, captures screenshots + control-tree dumps, and emits a structured report. Drives the agent-os VM via the Windows-MCP gateway. Sibling of web-app-testing and android-app-testing (shared report format). Does NOT fire for: building/coding a desktop app, the user's personal Windows on steamy (use nircmd), or general agent-os VM driving (use agent-os).

Use when the user wants to live-test a WEB app/site end-to-end in a real browser and get a works/doesn't-work + UI/UX report — not just write Playwright code. Triggers: "test my web app", "QA this site", "run E2E on the web app", "click through every feature and tell me what breaks", "review the UX of this web app", "does my web app work", "test the deployed site". Drives a real Chrome via Playwright over CDP (default http://127.0.0.1:9222), enumerates features from the DOM/ARIA tree, exercises each, captures screenshots + console/page/network errors, and emits a structured report. Sibling of android-app-testing and desktop-app-testing (shared report format). Does NOT fire for: writing a one-off Playwright script (use webwright), pure web design/build with no testing, or backend/API-only testing.

Read or interact with the broadcastr activity feed across concurrent Claude sessions. Use when the user says "what are other agents doing", "show recent activity", "mute plan-exec notifications", "what's on the bus", "broadcastr status", "tail broadcastr", "emit a manual broadcastr event", or asks why a notification appeared. Also use to disable broadcastr in the current session (BROADCASTR_DISABLED=1) or check the global feed. Does NOT fire on generic "show me activity" or "what's happening" unless broadcastr is explicitly named.

Use when the user asks to "work it", execute a superpowers executing-plans document in a worktree, create a PR as soon as the implemented plan is green, or run a complete review-and-fix loop over all touched files.

Use when the user asks to download, archive, search, inspect, or organize media with yt-dlp, MeTube, YouTube, playlists, channels, supported video sites, audio extraction, metadata, thumbnails, subtitles, Plex yt-dlp libraries, or NAS media downloads.

Save session documentation to a markdown file with full context — date, branch, HEAD, session ID, and git state pre-injected — then stage, commit, and push only the generated session artifact. Use when the user says "save session", "save to md", "document this session", "write up what we did", "save session notes", or asks to capture the current conversation as a session log. Pass `--html` or a `.html` path to render a rich Aurora-styled HTML artifact instead.

Install broadcastr's git-hook shims into the current repo. Use when the user says "install broadcastr hooks", "wire up broadcastr in this repo", "set up the broadcastr git hooks", or after first installing the broadcastr plugin in a new repo. Idempotent — safe to run repeatedly. Preserves any pre-existing hook as `<hook>.broadcastr-prev` and chains to it.

Check whether the current branch or worktree is ready to merge, including dirty state, mergeability, conflicts, overlap with other branches/worktrees, lint/tests/CI, stale docs, config/example drift, and live config follow-up.

Create the save-to-md session doc before staging, git add all, commit with Claude co-authorship trailer, and push to current/new feature branch — including project version bump and changelog update when applicable. Use when the user says "quick push", "push my changes", "commit and push", "ship this", "push to a new branch", or any request to wrap up local work and get it on the remote. Accepts optional `--no-bump` argument to skip the version bump.

Run the PR Review Toolkit flow from Codex for the current branch or pull request. Use when the user asks for a comprehensive PR review, asks to run /pr-review-toolkit:review-pr, needs mandatory review waves inside work-it, or wants focused checks for code quality, tests, comments, silent failures, type design, docs/config drift, or simplification.

Use when the user asks to "work it", execute a plan in a worktree, create a progress-tracked PR, or run a mandatory review-and-fix loop over all touched files until lint, tests, CI, and reviews are green.

Use this BEFORE creating a git worktree or implementing any plan. Tailored to our workflow — prefer it over superpowers:using-git-worktrees and every other worktree skill. Triggers - creating or adding a worktree; starting lavra-work, lavra-work-ralph, lavra-work-teams, executing-plans, subagent-driven-development, or work-it; whenever a Claude, Codex, or Gemini plan mode is entered or a plan is accepted; or before implementing anything in a fresh branch. Creates the worktree under .worktrees/ in the repo and makes it identical to and as warm as the main checkout - copying secrets and local config (.env, CLAUDE.md.local, .claude/settings.local.json), symlinking warm caches (node_modules, .venv, target, .next), and re-trusting mise/direnv. Also use when a worktree is missing files, builds cold, or reports mise 'not a trusted directory'. Bundles a worktree-sync engine, a create-in-.worktrees entrypoint, a minimal baseline template, and references.

Scoped to Jacob's homelab Rust repos — the rmcp MCP-server family (rustifi, rustify, rustscale, unrust, rarcane, rustarr, apprise-mcp, cortex, synapse2, rmcp-template) and the Lab runtime/ACP work. Use when editing those repos: covers rmcp-template-derived server patterns, action-dispatched MCP tools, CLI/MCP/API parity, service-layer architecture, config/auth/scope contracts, testing strategy, release/build conventions, and ACP runtime/provider work. Not a general-purpose Rust skill.

Use when the user asks to drive or test Claude's reserved agent-os Windows 11 sandbox VM via Windows-MCP, PowerShell, screenshots, desktop apps, installers, registry, filesystem, or noVNC. Triggers include agent-os, the agent-os VM or desktop, windows sandbox, winbox, run on agent-os, screenshot agent-os, or PowerShell on agent-os. Prefer webwright for generic web verification; use agent-os only when the task depends on the Windows sandbox or desktop. Do not use for the user's personal Windows machines such as steamy or steamy-wsl.

This skill should be used when the user asks to save a snippet, store code, create a snippet, search snippets, find a snippet, share a snippet, list snippets, delete a snippet, add to ByteStash, or mentions ByteStash or snippet management.

Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.

Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.

This skill should be used when the user wants to automate an iOS Simulator, drive an Android device or emulator via MCP tools, test on multiple devices simultaneously, run a visual regression baseline on mobile, audit accessibility on a real device, release an app to the Play Store, or use the claude-in-mobile CLI or MCP server. Does not apply for structured end-to-end test reports (use android-app-testing or desktop-app-testing for those).

Interpret and use `mcpjam` probe, doctor, OAuth, apps conformance, tools, resources, and prompts output conservatively against MCP 2025-11-25. Use when interacting with MCP servers, executing tools, triaging findings, performing security reviews, deciding whether a CLI finding is real or overstated, or turning inspection output into an engineer-facing report with severity and confidence.

Audit the current Git checkout, open worktrees, local branches, stale or merged cleanup candidates, merge readiness, conflicts, PR/CI/test state, blockers, and safest merge order. Use when the user asks for repo status, branch/worktree cleanup candidates, stale branch review, conflict investigation, merge readiness, or what must be done before open branches can merge.

This skill should be used when the user mentions labby, the labby CLI, the Lab gateway, or any Lab operator surface. Triggers include: "run labby doctor", "check labby health", "start the labby MCP server", "configure ~/.lab/.env", "search upstream MCP tools with Code Mode", "use labby gateway to import servers", "manage the Labby marketplace", "reload the gateway", or any request to run labby CLI commands, inspect gateway upstreams, or dispatch an action against a Lab service.

Use when invoking upstream MCP tools through the Lab gateway Code Mode surface — i.e. when the exposed MCP tools are `search` and `execute`, and real upstream tools are hidden behind the gateway. Trigger on "search", "execute", "gateway tools", "find a tool for...", "call X through the gateway", "what tools do I have", or whenever `list_tools` shows the synthetic `search` + `execute` pair. Not for designing or implementing new MCP tools, building MCP servers, or generic "what can you do" questions unrelated to the gateway.

This skill should be used when the user asks to save a snippet, store code, create a snippet, search snippets, find a snippet, share a snippet, list snippets, delete a snippet, add to ByteStash, or mentions ByteStash or snippet management.

Manage code snippets in ByteStash snippet storage service. This skill should be used when the user asks to "save a snippet", "search snippets", "find code", "share snippet", "organize snippets", "list my snippets", "create snippet", "delete snippet", or mentions ByteStash, code storage, snippet management, or code archival.

Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.

Manage notes and memos in self-hosted Memos service. Use when the user asks to "save this to memos", "create a memo", "search my memos", "find notes about X", "what did I write about", "add a note", "capture this", "remember this", "save this thought", or mentions note-taking, knowledge management, or personal notes.

Manage documents in Paperless-ngx document management system. Use when the user asks to "upload document", "search paperless", "find document", "add to paperless", "tag document", "manage correspondents", "organize documents", "archive document", "export document", "delete document", or mentions Paperless-ngx, document management, OCR, or paperless office.

Control Plex Media Server - browse libraries, search media, check what's playing, view recently added. Use when the user asks to "check Plex", "search Plex", "what's on Plex", "recently added", "who's watching", "Plex sessions", "Plex library", "browse movies", "browse TV shows", or mentions Plex media server.

Search indexers and manage Prowlarr. Use when the user asks to "search for a torrent", "search indexers", "find a release", "check indexer status", "list indexers", "prowlarr search", "sync indexers", or mentions Prowlarr/indexer management.

Manage torrents with qBittorrent. Use when the user asks to "list torrents", "add torrent", "pause torrent", "resume torrent", "delete torrent", "check download status", "torrent speed", "qBittorrent stats", or mentions qBittorrent/qbit torrent management.

This skill should be used when managing movies in Radarr. Use when the user asks to "add a movie", "search Radarr", "find a film", "add to Radarr", "remove a movie", "add movie collection", "check if movie exists", "Radarr library", or mentions movie management, TMDB integration, or Radarr operations.

Scaffold a new domain module following the {{project-name}} spec layout. Creates all required files with correct structure and wires CLI, API, and MCP surfaces.

Specialized configuration help for Claude Code, Codex CLI, and Gemini CLI — skills, subagents, hooks, MCP servers, plugins, slash commands, permissions, settings, memory. Use whenever the user asks to add, modify, troubleshoot, or audit any agentic-CLI configuration. Trigger this skill aggressively for anything touching .claude/, .codex/, .gemini/, settings.json, config.toml, hooks.json, .mcp.json, AGENTS.md, GEMINI.md, or whenever the user mentions "Claude config", "Codex config", "Gemini config", "agent config", or any feature listed in the routing table — even if they don't explicitly ask to "configure" something.

Authoritative checklist for reviewing apps/web/ changes — fully aligned with docs/design-docs/design-system-contract.md. Covers Aurora tokens, typography ramp, elevation, radius, scrollbar, import rules, shadcn bans, TanStack Query v5, logging, and auth. Preloaded by aurora-reviewer.

Authoritative checklist for auditing parity between Claude Code, Codex CLI, and Gemini CLI configurations across skills, subagents, hooks, and MCP servers. Encodes the cross-platform mapping rules including the hook-event capability gap. Preloaded by agent-parity.

Audit the docs/references llms.txt cache for drift — stale files, orphaned entries, and (optionally) version-bumped upstream releases. Each *-llms.txt is self-describing via YAML frontmatter; this skill reads that frontmatter and cross-references it against Cargo.lock / package.json. Used by sync-stack-llms before generating new entries.

Five drift checks for detecting where the codebase has outpaced documentation — knowledge map integrity, spec.md vs xtask parity, exec-plan lifecycle drift, stale active plans, ADR coverage gaps. Preloaded by drift-detector.

Manage llms.txt reference files in docs/references/. Create new entries from GitHub repos, refresh existing ones, list current entries, or remove obsolete ones — all via the bundled script. Use this skill whenever the user mentions creating an llms.txt for a specific GitHub repo (`/manage-llms-txt jmagar/lab`, `add a docs reference for owner/repo`, `pull docs for nextjs-form-validator`), refreshing the references (`refresh the llms.txt files`, `update our docs cache`, `re-pull all the references`), or auditing what's there (`what llms.txt files do we have`, `list the references`). Also handles removal (`remove the llms.txt for foo/bar`). The script is the source of truth — invoke it; don't re-derive its logic in conversation.

Authoritative procedure for publishing an MCP server to the official MCP registry at registry.modelcontextprotocol.io — package metadata, server.json schema, authentication, validation, publish, and verification. Preloaded by mcp-publisher.

This skill should be used when the user wants to manage subtitles in Bazarr. Triggers include: "missing subtitles", "wanted subtitles", "search subtitles", "download subtitles", "subtitle providers", "Bazarr status", "what subtitles are missing", "find subtitles for", or any mention of subtitle management for movies or TV series.

This skill should be used when the user asks about Jellyfin media server. Triggers include: "check Jellyfin", "Jellyfin library", "who's watching on Jellyfin", "active Jellyfin sessions", "add a Jellyfin user", "Jellyfin metadata", "Jellyfin transcoding", "Jellyfin health", "Jellyfin scheduled tasks", "Jellyfin plugins", or any mention of Jellyfin media server management.

This skill should be used when the user wants to request movies or TV shows via Overseerr, monitor or manage media requests, or check request status. Triggers include: "request a movie", "request a TV show", "add to Overseerr", "check request status", "pending requests", "is my request done", "Overseerr status", "approve a request", "decline a request", "delete a request", or any mention of Overseerr media requesting.

This skill should be used when the user wants to interact with their Plex Media Server. Triggers include: "check Plex", "search Plex", "what's on Plex", "what's playing on Plex", "who's watching", "Plex sessions", "active streams", "Plex library", "browse movies", "browse TV shows", "recently added", "on deck", "continue watching", "Plex status", or any mention of Plex Media Server.

This skill should be used when the user asks to search indexers, find a release, check indexer status, list indexers, sync indexers to Sonarr or Radarr, connect Prowlarr to another app, or mentions Prowlarr or indexer management.

This skill should be used when the user asks about torrents, downloading, seeding, or the qBittorrent client. Triggers include: "what's downloading", "list torrents", "add a torrent", "pause/resume/delete torrent", "torrent speed", "download queue", "qbit", "qBittorrent stats", "check download status", or any mention of managing a torrent client.

This skill should be used when the user wants to manage movies in Radarr. Triggers include: "add a movie", "search Radarr", "find a film", "download a movie", "remove a movie", "add movie collection", "check if movie exists", "is [film] in my library", "monitor a film", "check download queue", "Radarr library", or any mention of movie management or TMDB integration.

This skill should be used when the user wants to manage Usenet downloads with SABnzbd. Triggers include: "what's downloading", "SABnzbd status", "NZB queue", "add NZB", "pause downloads", "resume downloads", "slow down downloads", "retry failed downloads", "SAB history", "download queue", "is SABnzbd running", or any mention of Usenet download management.

Credential setup and diagnostics for the overseerr-mcp media stack. Automatically extracts API keys from service config files (local or via SSH) and writes them to the plugin credential store. Use when the user asks to 'setup credentials', 'configure plex', 'add my API key', 'setup media stack', 'authentication failed', 'API key not working', '401 error', '403 forbidden', 'why isn't X working', 'check my credentials', 'did my keys get extracted', or mentions any of the 8 bundled services (Plex, Overseerr, Radarr, Sonarr, Prowlarr, Tautulli, SABnzbd, qBittorrent) in a setup or authentication context.

This skill should be used when the user says "request movie", "request TV show", "get something on Plex", "search Overseerr", "request media", "submit media request", "check request status", "has my request been approved", "is X available yet", "list failed requests", "approve this request", "decline this request", "what's trending on Plex", "what movies are coming out", "recommend something similar to X", "show me my Plex watchlist", "what's my request quota", "check playback data", "there's an issue with this show", "report a problem with this movie", or mentions Overseerr, TMDB IDs, Radarr/Sonarr request management, or managing a Plex media library. Also appropriate when the user discovers a movie or show during research and wants to request it, or needs to manage, approve, troubleshoot, browse, delete, or update media requests.

Control Plex Media Server - browse libraries, search media, check what's playing, view recently added. Use when the user asks to "check Plex", "search Plex", "what's on Plex", "recently added", "what did I add to Plex recently", "continue watching", "on deck", "what was I watching", "who's watching", "Plex sessions", "Plex library", "browse movies", "browse TV shows", "is Plex working", "my Plex collection", "refresh library", "scan Plex for new media", "Plex playlists", or mentions Plex media server.

Search indexers and manage Prowlarr. Use when the user asks to "search for a torrent", "search indexers", "find a release", "find releases for X", "search for a movie", "find TV show episodes", "search by IMDB ID", "search by TVDB ID", "what indexers do I have", "indexer not working", "check indexer status", "list indexers", "prowlarr search", "sync indexers", or mentions Prowlarr, indexer management, or NZB/torrent searching.

Manage torrents with qBittorrent. Use when the user asks to "list torrents", "what's seeding", "torrent stuck", "torrent stalled", "reannounce torrent", "tracker not responding", "unstick torrent", "clear completed torrents", "add torrent", "pause torrent", "resume torrent", "delete torrent", "check download status", "torrent speed", "qBittorrent stats", or mentions qBittorrent/qbit torrent management.

This skill should be used when managing movies in Radarr. Use when the user asks to "add a movie", "download a movie", "grab a movie", "monitor a movie", "movie not downloading", "Radarr can't find it", "search Radarr", "find a film", "add to Radarr", "remove a movie", "add movie collection", "check if movie exists", "Radarr library", or mentions movie management, TMDB integration, or Radarr operations.

Manage Usenet downloads with SABnzbd. Use when the user asks to "check SABnzbd", "list NZB queue", "add NZB", "pause downloads", "resume downloads", "SABnzbd status", "Usenet queue", "NZB history", "retry failed downloads", "what's the download speed", "clear the queue", "failed NZBs", or mentions SABnzbd/sab/Usenet download management.

This skill should be used when managing TV shows in Sonarr. Use when the user asks to "add a TV show", "monitor a show", "track episodes", "add season", "missing episodes", "episode not downloading", "Sonarr not finding", "search Sonarr", "find a series", "add to Sonarr", "remove a show", "check if show exists", "Sonarr library", or mentions TV show management, episode tracking, or Sonarr operations.

Implement or update the full CI/CD pipeline for a lab plugin. Use when the user wants to add or update GitHub Actions workflows (ci.yaml, publish-image.yaml, release-on-main.yaml), configure pre-commit or lefthook, set up automated releases, audit an existing pipeline for drift, or sync Justfile targets with CI steps.

This skill should be used when the user asks to query, inspect, create, update, or delete My Plugin resources, or mentions My Plugin by name.

Bring an existing MCP plugin into full alignment with the homelab canonical plugin spec. Use when the user wants to update a plugin to current standards, replace stale scaffolding with the `plugin-templates` repo, reconcile manifest drift, standardize Docker and CI files, or turn a review report into a concrete alignment plan and implementation.

Containerize and deploy a lab plugin using Docker and Docker Compose. Use when the user wants to create or update a Dockerfile, docker-compose.yaml, entrypoint.sh, or health endpoint; audit an existing container config for drift; or plan a deploy strategy for a plugin. Trigger phrases include "Dockerize my Rust plugin", "containerize my Python MCP server", "set up Compose for my TypeScript plugin".

Research current primary-source guidance for MCP, Claude Code plugins, Codex plugins, and the language/runtime stack used by homelab plugins. Use when the user asks "what changed in the MCP SDK", "is this transport pattern still current", "find the latest docs for X", "before I scaffold this plugin I need to know...", or any time up-to-date information about MCP protocol changes, plugin manifests, SDK versions, transport patterns, package choices, Docker guidance, or the latest official docs is needed to scaffold, review, or align a plugin.

Review an MCP plugin against the homelab canonical plugin spec and identify any and all misalignments. Use when the user wants a plugin audited for spec drift, wants to compare a plugin to canonical manifests and runtime patterns, wants to know whether deviations are documented and justified, or wants a detailed plugin review report.

Create a new MCP plugin scaffold aligned to the homelab canonical plugin spec. Use when the user wants to create a new plugin repo, scaffold a plugin in Python, Rust, or TypeScript, choose manifests and runtime files, define commands/agents/skills, or turn docs and API references into an implementation plan for a new plugin.

Interactive credential setup wizard for claude-homelab. Use when the user wants to configure credentials, set up a new service, update API keys, or run initial setup after installing the homelab-core plugin. Triggers on: 'setup credentials', 'configure plex', 'add my API key', 'I just installed homelab-core', 'setup homelab', or any mention of needing to configure a homelab service credential.

This skill should be used when the user asks for a homelab health report, syslog summary, fleet status report, log analysis summary, 'what happened in the last 24 hours', 'show me this week's errors', 'summarize recent activity', or any time-bounded log analysis that should produce a written markdown report.

This skill should be used when the user asks to "search logs", "check errors", "tail logs", "show recent logs", "find log entries", "correlate events", "list hosts", "log stats", "syslog", "check homelab logs", or mentions system logs, syslog, log analysis, or log intelligence across homelab hosts.

Re-run the cortex plugin setup hook with the current userConfig and verify the Docker Compose deployment. Use when the user asks to redeploy cortex, apply plugin config changes immediately, rerun the setup hook, refresh the Docker deployment, or recover after an automated SessionStart/ConfigChange hook did not run.

Deploy rsyslog forwarding drop-ins to configured fleet hosts over SSH. Use when configuring fleet forwarding, repairing missing rsyslog forwarding, or updating forwarding after server_url or syslog port changes.

Run a comprehensive cortex health check covering environment, config quality, storage, ports, service status, HTTP health, MCP actions, listener reachability, Docker ingest, and fleet rsyslog forwarding. Use when the user asks for syslog doctor, deployment diagnostics, first-run preflight, health check, sanity check, or broad deployment verification.

This skill should be used after running cortex action=abuse_investigate to analyze the resulting evidence bundle. Use when the user asks to assess frustration incidents, evaluate abuse signals, analyze agent or user friction, produce a frustration report, or follow up on abuse_investigate results.

Tail or follow cortex service logs from Docker Compose. Use when the user asks for cortex service logs, startup logs, crash logs, plugin deployment logs, Docker logs, or follow mode. This is for the service's stdout/stderr, not client syslog entries.

Troubleshoot cortex connection failures, missing logs, unhealthy containers, restart loops, or vague "logs aren't working" reports.

Scaffold a new domain module following the spec layout. Creates all required files with correct structure and wires CLI, API, and MCP surfaces.

Authoritative procedure for publishing an MCP server to the official MCP registry at registry.modelcontextprotocol.io — package metadata, server.json schema, authentication, validation, publish, and verification. Preloaded by mcp-publisher.

Stage all current changes, optionally bump project versions, update changelog, commit with an appropriate message, push the current or new feature branch, and then save session documentation. Use when the user asks to quick push, commit and push everything, ship current changes, or run a full git add/commit/push workflow with session capture.

Save the current agent session to an in-repo markdown file with observed metadata, git state, session context, verification evidence, errors, open questions, and next steps. Use when the user asks to save session notes, persist conversation context, create a session log, document the current work, or when another workflow such as quick-push needs post-push session documentation.

Run xtask enforcement gates before declaring work complete. Use before finishing any Rust code change.

Post-cargo-generate setup for a new project. Walks through first-run configuration, domain replacement, and tooling bootstrap.

RAG synthesis prompt for axon ask — source-grounded, depth-adaptive, injection-hardened. Loaded at runtime by src/vector/ops/commands/ask/synthesis_prompt.rs.

Self-hosted RAG engine, web toolkit, and persistent agent memory. Use it to: remember durable project facts/preferences/decisions (memory.remember); recall/search agent memory (memory.search/show); answer questions indexed docs/code might cover (ask — a large corpus is already indexed; try ask BEFORE web-searching or giving up); search the web (search, auto-indexes results); semantic-search the index (query); scrape/fetch a page (scrape); crawl a docs site or pages you just used (crawl); map a site's URLs (map); extract structured data (extract); discover API endpoints (endpoints); extract brand identity — colors/logo/fonts/voice (brand); summarize a page (summarize); quick multi-source research (research); retrieve a URL's full indexed content (retrieve); embed local files/dirs (embed); ingest GitHub/GitLab/Gitea/Git repos, Reddit, YouTube, and Claude/Codex/Gemini sessions (ingest). Also triggers on axon, RAG, Qdrant, SearXNG, Tavily, hybrid/vector search, remember, recall, memory.

Use this skill when designing or implementing Aurora/Labby UI surfaces, shadcn registry components, registry/aurora tokens, app/gallery demos, or downstream Lab/gateway-admin screens that must follow the Aurora dark-first operator design system. Aurora uses a tokenized navy palette, cyan primary accent, rose secondary accent, muted status colors, and a Manrope + Inter type pairing.

Use whenever building, modifying, or styling UI for any Aurora, Labby, or Lab/operator surface on ANY platform — web (React/Next.js/shadcn), Android (Jetpack Compose), or CLI/editor/terminal — or when the user mentions Aurora, Labby UI, the operator console, the aurora-design-system repo (`~/workspace/aurora-design-system`), `aurora.tootie.tv`, the `@aurora` shadcn registry, `registry/aurora/`, `--aurora-*` CSS tokens, `aurora-page-shell`, the `tv.tootie.aurora` Android library, `AuroraTheme`/`AxonTheme`/Compose theming for an Aurora app, or the Aurora CLI/editor palette (`CliTheme`, Zed "Aurora Neon"). Invoke it any time React, Next.js, shadcn, Tailwind, Jetpack Compose, or "dashboard"-style UI work happens inside `~/workspace/aurora-design-system` or a project that consumes Aurora (web registry, Android library, or CLI tokens), even if the user doesn't say "Aurora" by name. Aurora is dark-first, uses a navy palette with cyan primary / rose secondary / violet AI accents, muted status colors, a Manrope + Inte