Publishes AppLocker (and similar Apple apps) via repo scripts plus App Store Connect MCP: verify entitlements, sync icons, bump versions, archive/export/upload, then ASC metadata and versions through MCP tools. Use when the user wants App Store Connect publishing, resubmission after rejection, TestFlight, or updating “What’s New” / localizations.

This skill should be used when migrating book content to website, converting chapter formatting, or making any changes to migrated content. Use when the user mentions "migration", "book content", "chapter", or edits files in docs/ that correspond to book chapters.

UX/UI Designer Nicolify. Toma 01-spec.md (ui-story o mixed) y produce 02-design-ui.md + mockups HTML. Iterative dialogue con Chris hasta aprobación. Si descubre edge cases nuevos → propone delta-spec.md, /po ratifica. Cargá skills sales-agent-expert, brand-expert, frontend-expert, tessl__shadcn-ui, tessl__tailwind. Activa cuando user dice: '/ux-ui', 'diseñemos la pantalla', 'mockup', 'wireframe', 'rediseña', 'la UI de X'.

Developer team router. Toma 1 ticket de 04-tickets.yaml. Decide owner según owner_eligibility (qwen-opencode preferido para BE/FE no-agentic; Opus 4.7 obligatorio para AGENTIC). Para qwen → invoca via Bash con prompt pre-cocido. Para Opus → spawna agent builder-{be,fe,agentic}. Mantiene T-{n}-impl-log.md vivo. TDD obligatorio. Corre /test-{backend,frontend} + Playwright + agentic evals. Push commit. Update ticket state. Activa cuando user dice: '/dev-team', 'tomá ticket T-N', 'implementá T-N', 'arrancá build'.

Product Owner Nicolify. Toma 1 user story (de /pm o Chris directo) y produce 01-spec.md + actualiza/crea product/stories/{module}/{id}.yaml. Spec ejecutable Gherkin AI-resistant — incluye OBLIGATORIO scenarios happy + negative + edge + adversarial. Loop iterativo con Chris hasta ratificación. Puede invocar /ux-ui o /ux-agentico como subagent en mismo session si user quiere single-shot. Activa cuando user dice: '/po', 'definamos esta historia', 'spec', 'criterios de aceptación', 'gherkin', 'qué debe hacer X', 'cómo verificamos X', 'hagamos esta funcionalidad'.

MoveIt2 SRDF generation, validation, and planning-semantics workflow. Use when creating, editing, regenerating, inspecting, or validating `.srdf` files, `gen_srdf()` sources, MoveIt planning groups, virtual joints, passive joints, end effectors, group states, disabled collisions, URDF-linked planning semantics, or SRDF handoff for live review. Use the URDF skill for robot structure, the SDF skill for simulator descriptions, and the Replicator artifact review pane for project artifact paths.

Update the project's long-term memory after a merge to main. Reads the merged diff and the current memory, then writes Expert shards, discovered invariants, candidate lints, and AGENTS.md pointers — all on a reviewable learn/<sha> PR. Use post-merge (the harness invokes it automatically) or with --rebuild to regenerate memory from scratch. Triggers - learn, expert-update, update memory, update expert, post-merge memory, self-improve (project)

One-time, guided setup of the local agent-first coding harness — the polling loop, the deterministic dispatcher, its config, the AGENTS.md contract, and the worktree provisioning that makes per-feature worktrees runnable. Use when a developer wants to set up, bootstrap, install, or initialize the coding harness for the first time in a project.

Persistent structured memory for LLM agents using botmem CLI. Use when storing, retrieving, or managing agent memory — facts, knowledge graph relationships, conversation summaries, and context blocks. Use for memory recall, ingestion of conversation content, knowledge graph queries, and exporting full context for prompt injection.

Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.

Use when this repository's Cloudflare Worker misbehaves or fails to deploy, or when setting or rotating a Worker secret. Covers where to look first, the secret-setting trap for JSON and JWK values, why a secret change needs a redeploy, and the module-evaluation crash on a first deploy.

Use when preparing the current branch for a pull request — resolving the base branch, checking changesets, running builds and reviews, filing findings as issues, and opening the PR with the mandatory five-section body.

Generate transcriptome-wide virtual spatial transcriptomics from H&E histology with DeepSpot-M. Use when you need spatial gene expression in log1p-CPM for 224x224 tiles at about 20x, want to query protein-coding genes by symbol instead of a fixed panel, or want to run prediction across a whole slide after tiling with histolab.

Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.

Use this skill when the user wants to generate UI, build a design system, clone a site's aesthetic, or browse the community UI gallery. Triggers on /ui-ref, /ui-show, /ui-system, /ui-share, or natural-language requests naming a reference site.

Use when the user wants to UNDERSTAND and RETAIN code, systems, or protocols — not just change them. Three modes. (1) VISUAL EXPLAINER — "make a visual explanation of this", "build an HTML presentation / slides explaining this code", "walk me through this module visually" — produce a self-contained HTML deck that teaches big-picture-first. (2) DIAGRAM-IT — "draw an ASCII diagram of this", "diagram this protocol / architecture / request flow", "sketch the state machine" — produce accurate monospace ASCII diagrams grounded in the actual code. (3) RECALL LOOP — "quiz me on this", "test my understanding", "help me remember this", "spaced repetition" — run a loop where the user explains, you probe gaps Socratically, and persist review cards. Trigger whenever the user is learning from a codebase — onboarding, building a mental model, or studying to remember — even if they don't name a mode. Also mention the Explanatory/Learning output style (/config) for ongoing "explain the why" narration.

Route generic agent-history ingestion requests to the appropriate specialized history-ingest skill. Use when the user asks to ingest AI-agent history without directly selecting the underlying agent-specific skill.

Search one AI agent's raw history for a specific topic, ingest only matching sessions, and return a synthesized answer. Use for targeted cross-agent recall; use wiki-history-ingest for bulk archival ingestion.

Search the session-brain graph for a past agent session by topic and load the winning transcript into the current conversation. Use for finding which session handled X, when Y was last worked on, or whether this was done before. Read-only; requires a session-brain graph.

Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options. **Auto-activation:** User asks to write, create, or draft an API reference page. Also triggers on paths like `docs/01-app/03-api-reference/`, or keywords like "API reference", "props", "parameters", "returns", "signature". **Input sources:** Next.js source code, existing API reference pages, or user-provided specifications. **Output type:** A markdown (.mdx) API reference page with YAML frontmatter, usage example, reference section, behavior notes, and examples.