Security: unscanned / not scanned

Use when one screen needs specifying on its own — a screen already built in the code, a screen a feature needs, or a layout to try before anything is specified. Derives it from the findings or asks, picks the floorplan, posture and density, binds regions, records tier overrides and can show the layout early as a Storybook story. Triggers on 'describe this screen', 'spec the inbox screen', 'which layout fits this', 'show me this screen', 'try two layouts'.

Use when the app needs its frame — the shell frame, the navigation model it realises, the one list of destinations, and the layout patterns every screen reuses. Works with or without features and screens, from the code's own routes when they exist. Triggers on 'app shell', 'navigation structure', 'sidebar or top bar', 'what does the layout look like', 'design the frame'.

[skaile-development] Evaluates resolved questions about the skaile-dev monorepo for FAQ-worthiness and curates entries. Broadened to all monorepo packages.

Git operations for the standalone skaile repos (platform, workspaces, ai-assets, store, brand, …). Five modes: commit (structured commit messages), branch (create/switch feature branches), worktree (parallel work in isolated checkouts), pr (open a pull request), finish (merge/PR/keep/discard branch). The former sync and deploy modes served the retired skaile-dev shell and now stop with a pointer.

The morning startup ritual for skaile-dev — opens with a cheeky "what did Peter do last night" investigation of the repo state, syncs the shell repo + submodules (reattaching any that landed detached at origin/main), reinstalls workspace deps, and builds the platform backend so frontend + backend are ready to start. Does NOT launch dev servers — Peter starts those himself. Use when Peter says "good morning", "/good-morning", "let's start the day", "fire up the platform", "boot me up", or any other morning kick-off phrase.

Monorepo-aware implementation orchestrator for the skaile-dev codebase. Reads the affected package CLAUDE.md files, identifies the tech stack, routes to the right prog-experts, produces a plan, executes with supervised dispatch, then triggers test, doc, and devlog on completion. Use for any non-trivial change to the skaile-dev monorepo.

[skaile-development] The bar a ticket must clear to exist: six impact questions (user harm, money, stability, security, team drag, significant benefit), each answered with evidence. Use before filing an issue an agent found on its own (a ship follow-up, a review leftover, an audit finding), when triaging incoming issues, or when sweeping an existing backlog for tickets that can be closed. Returns KEEP / CLOSE / ASK per ticket with the evidence, and a ready-to-post close comment.

[skaile-development] Debug a recently failed Skaile deployment on Jenkins. Defaults to the `skaile_platform` job; pass `target=store` to debug the `skaile_store` job instead. Reads the job over the local SSH tunnel (http://localhost:8090, anonymous read), finds the relevant build (last failed by default, or current/explicit), extracts the failure region from the console log, cross-references recent commits in skaile-dev around the build timestamp, and reports a structured summary with a fix hypothesis. Use when the user says "why did the deploy fail", "debug the jenkins failure", "what broke on jenkins", "the platform deploy is red", "the store deploy is red", "check the last platform-deploy", or otherwise asks about a Jenkins deployment failure.

Cleanly kills the Skaile platform backend and every process in its spawn chain (port 3001 listener, nest start --watch, dotenvx, bun run dev, sh wrappers). Use when the user says "kill the backend", "stop the backend", "free port 3001", "kill bun run dev", "clean up stray backend processes", or wants a clean slate before restarting `bun run dev` in `platform/backend`.

Use when you need to extract metadata (title, authors, abstract) and references from scientific PDF papers or book chapters.

Use when you need to create a podcast script from the output of the knowledge-paper-research skill.

Given a scientific paper (PDF or Markdown), run a full structured-knowledge extraction and web-research pipeline. Produces one metadata file next to the paper and a dedicated <stem>_research/ folder containing four thematic research files plus one per-author profile file (prefixed author_). Use whenever you need to deeply understand a paper, prepare a research briefing, or enrich a paper's content with external context.

Use when you need to generate long form podcast content from documents using a sophisticated multi-agent orchestration process.

[skaile-development] Distill a git diff into a 'reading diff' for a human: a judgment-call header plus an abridged diff whose every line is verbatim source - mechanical noise (renames, lockfiles, generated files, formatting, import churn) collapsed or dropped. Comprehension, not critique - it does not hunt defects. Use when the user wants to understand a diff rather than review it: before approving a merge, catching up on a branch, reading agent-written code, or when the ship skill offers a reading diff at its final merge question. Concept and rubric from boldsoftware/meat, reimplemented as a prompt - no binary, no extra API key.

Use when you need to migrate a legacy skaile.yaml (schema 4.x and earlier, using `repositories:` or `ai_resources:`) into the new canonical-identity shape (`sources:` + `stores:` + canonical dep refs `kind:@<publisher>/name[#pin]`). Triggers: 'migrate skaile.yaml', 'convert manifest', 'schema 4.x migration', 'update to canonical-identity', 'fix repositories: error', 'fix ai_resources: error', '@skaile to @skaile-ai rebrand'.

Use when stakeholder notes left on the Storybook mockup need to land in the concept, or when the user says 'work through the feedback', 'apply the annotations', 'what did the reviewers say'. Routes each open note to the spec, data-model entity or glossary term it belongs in, authors a reviewable diff for it, and — after you approve the review file — applies the approved diffs in one commit and closes the notes.