Build, query, and inspect the project knowledge graph in .planning/graphs/

Plan and implement Python changes with ruff, pyright, and pytest validation before commit.

Git 변경사항을 분석하여 Conventional Commits 형식의 커밋 메시지를 생성합니다. 커밋, commit, 커밋 메시지 요청 시 자동 활성화됩니다.

Build an installable ZIP for the Lime Pipeline Blender add-on. Use for release candidates, QA handoff to artists, or whenever version/changelog changes must ship as a distributable artifact.

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.

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.

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

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.

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.

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 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.

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

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.

'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.'

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.

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

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.

Use when implementing globe.gl (Globe.GL) for 3D globe data visualization with WebGL/ThreeJS, including setup, data layers (points, arcs, polygons, labels), and integration patterns in plain HTML or React.

<!--

go-test-coverage

Use when deciding the next sparse-ir-rs release version or checking whether a change set should be patch, minor, or major under Semantic Versioning

Comprehensive guide for creating high-quality specialized agents following v2 architecture patterns. Use this skill when users need to design and implement new agents, understand agent architecture, or learn best practices for agent creation.

Use after any meaningful ntn-sim-core phase/group completion or contract change to determine which SDD, status, validation, README, and todo documents must be updated in the same change set.

Evaluate cross-framework parity for generated components and accessibility metadata. Use when emitter behavior changes or parity regressions are suspected.

Write commit messages to a temporary file and commit with `git commit -F`. Never use `git commit -m`.

Automate browser interactions via the Playwright CLI. Use for web testing, form filling, screenshots, UI verification, and data extraction.

Use when editing beamHO-bench paper profiles, source maps, assumption-backed research parameters, or paper-source registries so schema, profile JSON, sources JSON, and validation coverage stay traceable and synchronized.

**🛡️ Test your AI agent's security posture against adversarial attacks**

Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.

Use when deciding whether a future ntn-sim-core follow-on, especially OMNeT++ / INET / estnet or other external-consumer/backend realism work, should be bootstrapped with OpenSpec instead of the repo's normal SDD/todo flow. Also use when a user explicitly mentions OpenSpec, opsx workflows, or wants a separate change/spec workflow for a new track without replacing existing ntn-sim-core authority.

Core principles, persona definitions, and command workflows for the dotfiles project. Use when seeking development guidance, selecting an appropriate expert persona (Architect, Developer, Tester, DevOps, Analyst), or following standard project commands (analyze, implement, design, etc.). Ensures consistency, quality, and adherence to project-wide best practices.

Build or modify a Pi extension. Use this whenever the user wants a custom slash command, extension tool, lifecycle hook, context filtering, session persistence, UI prompt, model/provider integration, or anything placed in ~/.pi/agent/extensions/. This skill is especially relevant when the user says “create a pi extension”, mentions /reload, wants custom command behavior, or needs extension code that uses Pi APIs rather than app code.

>

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

Use when working with scaleinvariance package for multifractal field simulation and analysis - Hurst exponent estimation, fractional Brownian motion (fBm), fractionally integrated flux (multiplicative cascades) (FIF), intermittency analysis, and Generalized Scale Invariance (GSI). Also use for scaling analysis of time series, turbulence data, atmospheric fields, or any task involving self-similar, cascade, or multifractal processes or fields.

>

Run the repository's standard validation flow quickly and safely. Use when changes are made and you need confidence before commit or push.

Seed a new runnable template under templates/NNN-slug/ from a short spec by chaining existing skills (intake → ship-faster stages) while keeping it clean and shareable (no secrets, minimal scope). Use when creating a new template quickly.

Use when you need to define or converge a project's visual direction. Scan project documentation to identify intent, then produce a design-system.md (either preserve existing style or pick from 30 presets). Triggers: design system, design spec, UI style, visual style, design tokens, color palette, typography, layout. Flow: scan → intent → (gate) preserve vs preset → deploy design-system.md after confirmation → (default) implement UI/UX per design-system.md (plan first, then execute).

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.

workleap-skill-optimizer

Custom CLI commands: command definition in atmos.yaml, arguments, flags, steps, env vars

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.