End-to-end smoke test of all MemCan MCP endpoints. Creates, searches, updates, deletes memories and checks logs. Use when verifying MemCan installation or after upgrades.

>

Use when implementing a task - follow the plan, check ACs, track progress

Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise. Expert in team composition, personality balancing,

Angular 21.x SPA development skill with TailwindCSS 4.x and daisyUI 5.5.5. Use when building Angular standalone components, services, lazy-loaded routes, unit tests, or creating UI with TailwindCSS + daisyUI. Covers component scaffolding, UI/UX design, accessibility audits, and design systems.

Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.

REST and GraphQL API testing with Playwright. Use when testing APIs, mocking endpoints, validating responses, or integrating API tests with E2E flows.

Select and apply the correct SQL connector implementation pattern (SDK-default minimal or source-specific custom). Use when building or extending SQL metadata/query extraction connectors.

Use when adding authentication to Android applications (Kotlin/Java) with Web Auth, biometric-protected credentials, and MFA - integrates com.auth0.android:auth0 SDK for native Android apps

>

Create an isolated worktree in `.worktrees/` branched from up-to-date main, with spec directory scaffolded.

Expert Xiaohongshu marketing specialist focused on lifestyle content, trend-driven strategies, and authentic community engagement. Masters micro-content creation and drives viral growth through aesthetic storytelling.

description: Automated pipeline from SPEC.md to ready-to-execute tasks — runs autonomously by default with parallel task execution

Use PROACTIVELY when discovering, creating, renaming, or removing workflow definitions. MUST BE USED when adding a new user-facing flow that needs testing, or when the user asks for workflow changes. Owns the four-file workflow contract (registry + spec + bug file + fix-loop binding).

Implement features using Spec Driven Development (SDD) workflow. Creates design and task documents with approval gates.

Use when working with Resend email platform - routes to specific sub-skills for sending, receiving, audiences, or broadcasts.

Prepare and commit code changes with full verification, pre-commit checks, and tests. Runs verification skill, fixes issues using TDD, executes all test suites, and creates atomic commits. Use when ready to commit changes, before committing, or when asked to prepare a commit.

Patterns for detecting and managing code smells and technical debt in .NET applications. Run Slopwatch CLI to detect LLM reward hacking, disabled tests, suppressed warnings, empty catches, and other shortcuts. Use when identifying code smells, running quality gates in CI/CD, or validating LLM-generated code changes.

Create a specification before implementing features. Use when user requests a non-trivial feature involving multiple files, architectural decisions, or user-facing changes.

>

A framework for building ui, components and design systems. Components are added as source code to the user's project via the CLI.

Expert in systematic debugging, root cause analysis, test automation, and stealth bug hunting. Find what developers forgot. Test behavior, not implementation.

Fix a specific bug or problem in the codebase. Supports two modes: immediate fix or plan-first approach.

Transforms AI-generated text into human-sounding writing by applying a **fixed, ordered pipeline of rules**. Each rule is a specific find/replace or structural operation. The agent executing this skil

Simplifies and refines code for clarity, consistency, and maintainability while preserving exact functionality. Focuses on recently modified code unless instructed otherwise. Use when the user asks to simplify, refactor for readability, reduce complexity, improve maintainability, dedupe, or clean up code after changes.

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

Implement technical plans from thoughts/shared/plans with verification

>-

Provides guidance for enterprise-grade RL training using miles, a production-ready fork of slime. Use when training large MoE models with FP8/INT4, needing train-inference alignment, or requiring speculative RL for maximum throughput.

Perform cross-artifact consistency and quality analysis. Automatically

Drives iterative development of the Pet Central trusted marketplace. Use when building features, improving UI/UX, implementing backend modules, testing, or completing any work described in docs/spec.md. Applies to all apps (web-consumer, web-vendor, web-admin, web-partner, web-kiosk), packages (ui, database, auth, etc.), and the api-gateway. Includes complete testing and validation with correction loops until the system is fully functional.

Design and implement Concept Encoder PyTorch modules safely. Use when sketching tensor shapes, writing or refactoring nn.Module code, checking memory or DDP behavior, choosing AMP or torch.compile patterns, or improving training-time performance and numerical stability. Not for experiment logging, changelog updates, or high-level research prioritization.

Use this skill when the task explicitly involves:

>

>-

Run all linting, type checking, tests, Markdown lint, and documentation build for the project. Check for errors and warnings, then fix any problems found. Use when the user asks to run checks, verify the build, run CI locally, or fix lint/type/test errors.

Add or insert a new numbered pipeline step in the p2cs_project, following the standardized Step/DataFile/explore notebook patterns and safely renumbering subsequent steps (code, data, figures, tests, config, dependencies, and imports) when inserting in the middle of the pipeline. Use when creating a new step_* directory, inserting a step between existing ones, or updating step numbers across the project.

DART CI/CD troubleshooting - GitHub Actions, cache debugging, platform-specific failures

Development workflow guide. Covers build, test, lint, format commands, package structure, Git hooks, TDD methodology, and coding conventions. Use when setting up dev environment, running tests, or following project conventions.

Rust coding conventions expert covering naming, formatting, comments, clippy, rustfmt, lints, code style, best practices, and idiomatic patterns.

Rust learning and ecosystem tracking expert covering version updates, new features, RFC tracking, crate updates, best practice evolution, and learning resources.

Use when developing Rust projects in the tempoxyz org—standardizes fmt/clippy/nextest, sccache+mold, feature-powerset checks, MSRV builds, docsrs flags, and xtask patterns so local and CI behavior match.

Handle user questions, feature requests, and bug reports for connectrpc-axum. This skill should be used when users ask questions about the library, request new features, or report bugs. It first attempts to answer using project documentation, verifies bugs with integration tests, and submits GitHub issues when needed.

Implement a new Flet extension/control that wraps a third-party Flutter package end-to-end, including dependency selection, version pinning, compatibility checks, Python/Flutter integration, docs, examples, tests, and CI updates. Use when adding any flet_* package backed by an external pub.dev package.

Apply MCAF non-functional-requirements guidance to capture or refine explicit quality attributes such as accessibility, reliability, scalability, maintainability, performance, and compliance. Use when a feature or architecture change needs explicit quality attributes and trade-offs.

Create or update a feature spec under `docs/Features/` using `docs/templates/Feature-Template.md`: business rules, user flows, system behaviour, Mermaid diagram(s), verification plan, and Definition of Done. Use before implementing a non-trivial feature or when behaviour changes; keep the spec executable (test flows + traceability to tests).

Use when the user asks about Omni platform documentation outside the narrow embed flow, including modeling, REST API, AI and MCP features, administration, permissions, connections, and platform setup; browse official `docs.omni.co` pages, prefer `$omni-embed-docs` for embed-specific questions, and answer with source links.

SIMD vectorization for Rust — detects ISA features, identifies vectorizable patterns, generates platform-specific intrinsics (ARM NEON/SVE, x86 SSE/AVX/AVX-512), validates correctness and performance. Uses tiered research with baked-in references and /deep-research fallback.

Edit LCP protocol docs under docs/protocol/ in BOLT-style (TLVs, message formats, state flow).

Migrated from the legacy agent profile. Use this as an on-demand specialist workflow.