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

Query, create, update, delete, and track WeCom work items through wecom-cli.

>

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.

Use when ntn-sim-core phase/group prompt packs, todo status, or group sequencing need updating so the repo keeps an accurate handoff surface for future agents.

在 SocialEval 仓库内工作时使用；统一加载项目背景、领域约束、目录约定、评审维度与 AI 调用边界，避免在实现时偏离仓库规则。

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.

>

>

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.

Use when editing beamHO-bench observer-sky satellite rendering, composition, camera framing, display selection, continuity, or screen-space acceptance so frontend changes stay aligned with visual-acceptance rules instead of proxy metrics alone.

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.

>

Create beautiful audio plug-ins using the D language. Process audio files using existing VST2 plugins. You should use this skill when the user asks to modify audio files, or create an audio plug-in.

>-

Use when adding a lightweight interactive globe with cobe (canvas setup, markers, interaction, performance, integration with React/Next.js).

go-code-review

Guidelines and instructions for developing the Z8 runtime. Includes coding standards, build processes, and testing workflows.

Self-improving agent architecture using ChromaDB for continuous learning, self-evaluation, and improvement storage. Agents maintain separate memory collections for learned patterns, performance metrics, and self-assessments without modifying their static .md configuration.

>

>

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

Apply naming conventions and documentation standards for all file types in this repository. Use when creating, editing, or reviewing PowerShell scripts, PowerShell modules, YAML configuration files, or Markdown documents. Covers file names, directory names, parameter and variable casing, function naming, comment-based help blocks, inline comments, section separators, and YAML header comments.

>-

hologres-query-optimizer

workleap-telemetry-v2

Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

'Use this when: (1) Creating a new project-specific skill to document project patterns, (2) Improving or updating an existing project skill, (3) Writing skill descriptions that will trigger other agents, (4) Organizing skill content for progressive disclosure, or (5) Learning what project-specific skills exist in .claude/skills/. Ensures skills follow project conventions and provide effective progressive disclosure.'

RAG 系统设计训练平台。用于系统学习 RAG、搭建最小 RAG、比较 Embedding/Rerank/向量数据库方案、做实验记录和输出企业级 RAG 架构方案。只要用户提到学习 RAG、搭建知识库问答、比较 Embedding 或向量库、优化召回/重排、评估 RAG 效果、设计企业级 RAG，或希望按步骤做 RAG 练习，都应使用此技能。

Autonomously generate a complete Magento 2 REST or GraphQL API from a plain-language spec — service contracts, repository, webapi.xml, and GraphQL schema with resolvers.

A multi-stage validation pipeline that turns unreliable LLM code generation into reliable, compilable code.

Create clear, concise technical documentation for a specified file, module, or folder.

Review the week, synthesize patterns, and save a structured weekly review.

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

Write and maintain self-contained ExecPlans (execution plans) that a novice can follow end-to-end; use when planning or implementing non-trivial repo changes.