Use when working on ScenePilotix across multiple threads or when a task may change product flow, workspace boundaries, naming, save/export behavior, prompt-engine routing, or platform execution strategy. Ensures the shared development strategy doc is treated as the single source of truth and updated at the end.

Conduct deep research on a topic using web search and analysis. Use when you need comprehensive understanding of a topic.

Adversarially review proposed mew self-improvement loops for product-goal drift, M5 safety boundaries, weak evidence, missing verification, hidden rescue edits, and whether the loop should be approved, rejected, or revised.

Turns a Gardener runtime failure into a deterministic session recording + test.

Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment. Handles state management, animations, testing, and performance optimization for mobile, web, desktop, and embedded platforms. Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features.

AWS security finding analysis: analyze findings, map to Atmos components/stacks, generate structured remediation with exact Terraform changes and deploy commands

**Skill Name**: browser-local-chrome-remote-debugging

Use when you have made code changes and want another CLI agent to review them before committing or continuing. Covers crafting review prompts, scoping reviewer permissions to read-only, interpreting feedback, and follow-up clarification sessions.

Pause for review every N tasks - selective autonomy pattern

Use Moneta shared memory via MCP tools to recall project knowledge

This is an example `workflow-<slug>/SKILL.md` generated from a workflow spec.

>

Use this skill whenever the user wants durable context, cross-project memory, shared procedures, audit trails, Obsidian-backed knowledge, or a reusable operating layer across multiple agent sessions. Trigger aggressively on requests to remember decisions, save findings, reuse previous workflows, coordinate several agents, maintain shared organizational context, install or activate MAKOS, or avoid starting from scratch in each conversation.

Use this skill when the project uses shadcn-svelte and the task involves implementing or refactoring UI with that library.

对 Python 改动做“问题优先”的代码审查。适用于审查 diff、定位行为回归、评估风险、检查测试覆盖缺口，尤其是 crawlers、storage、fish_intel_mvp 相关改动。

Transform one mentioned lecture transcript markdown file into a structured lecture note and save a merged output file in the same folder. Use when the user asks to create lecture notes from an existing transcript file. Keep transcript cleanup loose and preserve original wording as much as possible.

Run or inspect the hotspot monitoring cycle for the wy-hotspot-monitoring workspace. Use this skill whenever the user asks to scan now, trigger a monitor manually, check which monitors are due, validate the monitoring pipeline, or see the latest run results and new hotspots. Prefer this skill over using the web UI when the request is operational.

Keep git history clean for each goal-oriented work unit. Use when Codex starts new implementation work, prepares a PR/review request, or needs to ensure unrelated commits/diffs are not mixed.

Use when developing, reviewing, or closing work in beamHO-bench that is governed by an active pending SDD, especially when the task requires reading PROJECT_CONSTRAINTS, active pending status, validation rules, and lifecycle-sync docs before editing code.

Ensure the front-end application remains fully compatible with the backend API by referencing and adhering to the Server API Specification.

Use when starting any active phase/group in ntn-sim-core platform refactor, or before promoting a downstream MODQN/UI prompt into active work, to verify authority docs, phase status, prompt freshness, and go/no-go conditions.

hologres-cli

Create or update Agent Skills for Claude Code, Codex, and other Agent Skills-compatible clients. Use when users ask to design a new skill, revise an existing skill, write SKILL.md, optimize skill triggering descriptions, or decide scripts/references/assets and folder structure from a prompt.

Use this skill when creating or refactoring Svelte 5 / SvelteKit frontend code, especially UI components, local feature UIs, component APIs, and Tailwind-based styling. This skill improves code quality by enforcing modern Svelte 5 conventions, strong component boundaries, clear state ownership, reusable modular logic, and disciplined Tailwind usage. Not intended for visual design exploration or branding work.

Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.

Generate a concise hotspot briefing from the wy-hotspot-monitoring workspace state. Use this skill whenever the user asks for a hotspot digest, trend summary, recent signal review, shift report, or operator-ready briefing, especially when they want a quick readout instead of raw JSON or the full dashboard.

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

Manage hotspot monitoring definitions for the wy-hotspot-monitoring workspace. Use this skill whenever the user asks to create, update, pause, resume, inspect, list, or delete monitoring items, or when they want to change keywords, scopes, sources, intervals, GitHub repo allowlists, or notification email settings. Prefer this skill over editing data files manually.

Upgrades React Native apps to newer versions by applying rn-diff-purge template diffs, updating package.json dependencies, migrating native iOS and Android configuration, resolving CocoaPods and Gradle changes, and handling breaking API updates. Use when upgrading React Native, bumping RN version, updating from RN 0.x to 0.y, or migrating Expo SDK alongside a React Native upgrade.

A rigorous Technical Architect and Systems Analyst responsible for producing implementation-ready specifications AND an execution-safe implementation plan. This skill defines immutable technical contracts (APIs, data models, states, migrations, constraints) and a structured step-by-step implementation roadmap while explicitly minimizing AI drift through locked requirements, guardrails, and verification checkpoints.

Deploy any project to Vercel. **Always deploy as preview** (not production) unless the user explicitly asks for production.

>

>

Semantic version control — entity-level diffs on top of Git. Use when reviewing code changes, understanding what changed in a commit/PR, diffing files, analyzing impact of changes, or when line-level diffs are insufficient. Triggers: sem diff, semantic diff, what changed, entity diff, function diff, impact analysis, entity blame, dependency graph, code change summary, what broke, what was renamed, show changes semantically, 语义差异, 实体级别差异

Applies the project's commit message convention. Use when writing commit messages, making git commits, or summarizing changes.

Solve one assignment problem file using a single endpoint with two logical tracks: (A) Math/Physics PDF problem solving (lecture slides/lecture notes as ground truth) and (B) code artifact generation. Save a final answer with detailed explanation next to the problem file.

>

>

Fast semantic code navigation via LSP. Load FIRST before ANY code task - even 'simple' ones. Trigger scenarios: (1) fixing lint/type/pyright/mypy warnings or errors, (2) fixing reportAny/reportUnknownType/Any type errors, (3) adding type annotations, (4) refactoring or modifying code, (5) finding where a function/class/symbol is defined, (6) finding where a symbol is used/referenced/imported, (7) understanding what a function calls or what calls it, (8) exploring unfamiliar code or understanding architecture, (9) renaming symbols across codebase, (10) finding interface/protocol implementations, (11) ANY task where you'd use ripgrep to find code or read-file to view a function. Use `leta show SYMBOL` instead of read-file, `leta refs SYMBOL` instead of ripgrep for usages, `leta grep PATTERN` instead of ripgrep for definitions, `leta files` instead of list-directory.

>

Use when validating beamHO-bench changes, deciding which project gates to run, preparing SDD closure, or checking whether lifecycle docs and manual acceptance evidence are sufficient before marking work complete.

Generates high-quality, predictable, and efficient .agent/skills/ directories based on user requirements. Reference this at any time you are creating any other skill for Antigravity.

Use when ntn-sim-core changes need validation planning or phase-completion verification, to map the current scope to the correct validation gates, scripts, blockers, and evidence requirements.

Expert Docker and Nginx deployment assistant. Use for Docker configuration, containerization, VPS deployment, infrastructure setup, SSL certificates, docker-compose files, nginx reverse proxy, deployment guides, infrastructure documentation, cloud deployment, container orchestration, production deployment, environment configuration, dockerfiles, server setup, deployment checklists.

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Configure and use Biome (biomejs) for TypeScript linting and formatting. Use when setting up Biome in a project, configuring lint rules, migrating from ESLint/Prettier, fixing lint errors, setting up CI pipelines with Biome, or configuring git hooks for code quality. Covers biome.json configuration, file inclusion/exclusion patterns, rule overrides, and integration with build tooling.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.

Use when mapping literature or standards evidence into ntn-sim-core parameter registry, parameter spec, or provenance surfaces without letting synthesized simulator docs override the paper-catalog source chain.

Go templates: Sprig/Gomplate functions, atmos.Component, atmos.GomplateDatasource, atmos.Store, template configuration, evaluations