Plan, inspect, approve, create, validate, and roll back a fresh Proxmox service guest while protecting legacy guests. Use before creating or changing an LXC or VM for self-hosted services, especially on resource-constrained Proxmox hosts.

Implements a feature by executing a plan phase-by-phase — writes tests first, runs them red, then implements code to make them green, then validates nothing is broken. Use when you have a plan from /draft and are ready to implement, build, develop, create, or write code for a feature using TDD.

Entrevista profunda greenfield + decide stack (priorizando Luana: FastAPI + Next.js + Clerk + Postgres + Qdrant) + scaffold inicial + PROJECT-MAP. Para proyectos VACÍOS o casi vacíos. NO ejecutar en proyectos con código existente — usar /project-audit en su lugar. Activa cuando Chris dice: '/project-bootstrap', 'arrancamos proyecto nuevo', 'greenfield', 'desde cero', 'bootstrap proyecto', 'crear scaffold', 'iniciá proyecto'.

Sub-architect Frontend. Invocado por /architect orchestrator. Lee 01-spec.md + 02-design-ui.md + story YAML. Produce 03-arch-fe.md con: routes, components FSD-Lite, hooks React Query, Zod schemas, types TS, tests Vitest+Playwright, server-first boundaries. Activa cuando /architect spawna o user dice: '/architect-fe', 'arq frontend', 'diseña FE'.

Ensures the app runs efficiently and safely by handling memory management, state architecture, and Coroutine optimizations. Use this skill to fix memory leaks (OOM), optimize Coroutine dispatchers, enforce immutable StateFlow architectures, add database indexes, or resolve Compose state bottlenecks.

Comprehensive guide for implementing Supabase Realtime features with best practices, scalable patterns, and migration strategies. Use when building realtime features in Supabase applications including messaging, notifications, presence, live updates, collaborative features, or migrating from postgres_changes to broadcast. Covers client setup, database triggers with realtime.broadcast_changes, RLS authorization, naming conventions, and performance optimization.

Conducts structured business analyses: problem and stakeholder analysis, as-is/to-be gap analysis, user personas, scope definition. Creates BA documents as the foundation for requirements engineering. Uses innovation phases EXPLORATION, IDEATION, and VALIDATION. Use this skill when the user mentions "Business Analysis", "BA", "Stakeholder Analysis", "Problem Analysis", "As-Is Analysis", "Gap Analysis", "User Personas", "Define Scope", "Analyze Project", "Explore", "How might we", "Value Proposition", "Idea Potential", "Innovation", or similar. Also when the user wants to start a new project and does not yet have a clear requirement. This skill helps understand the problem before discussing solutions.

Transforms business analyses into epics, features, and tech-agnostic success criteria. Creates handoff documents for the architect. Use this skill when the user mentions "Requirements", "RE", "Define Features", "Create Epics", "User Stories", "Requirements", "Success Criteria", "NFRs", "ASRs", "Acceptance Criteria", or similar. Also when a BA document exists and the next step is the formalization of requirements.

Use this skill when the user wants to scan code for secrets, find leaked credentials, check for hardcoded API keys, audit git history for sensitive data, or set up secret detection.

Use this skill when the user wants to schedule recurring tasks, convert natural language schedules to cron expressions, or manage APScheduler jobs.

Critiques a plan, design, finding, or hypothesis using codex CLI and agy (Antigravity) CLI in parallel, then reconciles their feedback via advisor(). Use when seeking a second opinion before committing to a plan, validating an approach, stress-testing a design, or challenging your own conclusions. Also auto-fires before ExitPlanMode, exploratory finding presentation, and superpowers phase commits (brainstorming, writing-plans, systematic-debugging, finishing-a-development-branch).

enforces engineering-governance checks before code changes that may be unnecessary, risky, architectural, or scope-widening. use when the user asks whether to refactor, clean up, redesign, choose a next development step, review a proposed implementation, evaluate architectural consistency, review a pull request, or prevent development drift. do not use as the primary implementation skill for routine debugging, bug fixes, feature coding, or language-specific coding unless a no-op, minimal-diff, or architecture-conflict judgment is needed.

Produce a day/week/month knowledge digest summarizing what was learned, updated, and connected in the wiki. Use for readable recent-learning summaries; wiki-status reports source and ingestion state instead.

Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.

Independently check whether an implementation matches its stated goal and return PASS/WARN/FAIL with actionable issues. Use for second-opinion validation of an implementation or generated output.

Configure Obsidian graph colors by tag, folder, category, or visibility by updating .obsidian/graph.json. Use for graph colorization; preserve other graph settings and back up before changes.

Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes. Use for architecture orientation, impact analysis, what-would-break questions, or finding callers. Uses CodeGraph when available and a dependency-free builtin fallback.

Manage SSOT, memory, and cross-tool memory search. Guardian of decisions.md and patterns.md. Use when user mentions memory, SSOT, decisions.md, patterns.md, merging, migration, SSOT promotion, sync memory, save learnings, memory search, harness-mem, past decisions, or record this. Do NOT load for: implementation work, reviews, ad-hoc notes, or in-session logging.

Generates technical guides that teach real-world use cases through progressive examples. **Auto-activation:** User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. **Input sources:** Feature skills, API documentation, existing code examples, or user-provided specifications. **Output type:** A markdown guide with YAML frontmatter, introduction, 2-4 progressive steps, and next steps section.

How to analyze and respond to GitHub PR review comments in NetAlertX. Use this whenever you are addressing PR feedback, review threads, or inline code comments.