This skill provides expertise in Clean Architecture and Hexagonal Architecture (Ports and Adapters) patterns in Go, including dependency inversion, layer separation, and testable design.

Analyze OpenAPI/Swagger spec (JSON or YAML) against existing test files and generate an HTML coverage report with QA automation tasks. Use when user provides an OpenAPI spec file and wants to know test coverage status.

'Define como componentes Angular devem ser criados, estruturados, documentados e testados no Design System Lumo.'

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

PyVISA and lab instrument control in Python: VISA resource lifecycle, timeouts and terminations, raw TCP/UDP sockets vs VISA, when to introduce hardware abstraction layers, validating user and config input before hardware, testing without hardware, and extracting tables or text from instrument manuals and datasheets (PDF). Triggers on pyvisa, VISA, GPIB, USB-TMC, serial instrument, socket lab, SCPI, datasheet PDF, instrument driver.

Audits PWA aspects of SunnahSleep. Use when working on offline support, service worker, manifest, caching, or install flow. Covers vite-plugin-pwa, Workbox, and PWA best practices.

Query, inspect, or refresh codebase intelligence files in .planning/intel/

Ordo testing and benchmarking guide. Includes unit tests, integration tests, Criterion benchmarks, k6 load tests, CI configuration. Use for writing tests, performance analysis, continuous integration.

Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.

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.

Load when a project has outgrown its current play level (Sprint→Build or Build→Platform) or needs to be scaled back. Use when user says 'this is bigger than a sprint now' or 'we need to treat this as a real product'. Updates .speck/project.json and adapts artifacts.

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

Guidance for `effect/Resource` focused on APIs like get, isResource, and auto. Load after `effect-skill-router` when this module is the primary owner.

Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API.

Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.

Complete Phase 2 instructions — scope planning, anti-bloat rules, screen metadata format, Make TC-EBC prompt framework, Guidelines.md structure, and quality checks. Read this when running /phase2.

Implements features strictly from specs. Reads specs first, modifies only listed files, no scope creep. Use when implementing a feature, working with specs/, or when the user references a spec number.

Implement technical plans from thoughts/shared/plans with verification

Guidance for facet `effect/unstable/http#core` focused on APIs like Etag, Cookies, and Headers. Load after `effect-skill-router` when this facet is the primary owner.

Create and maintain llms.txt files for AI crawlers following the official specification. Use when setting up AI-friendly documentation indexes, creating machine-readable content maps, or helping websites become more discoverable by LLMs like ChatGPT, Perplexity, and Gemini.

Verifies that a PaperMiner change is ready to hand over by checking tests, lints, ripple effects, and documentation sync. Use before declaring a feature, refactor, or bug fix complete.

Get GitHub issue details, body text, and optional comments. Use when users want to read issue content, inspect discussion context, or fetch issue data before another change. Accept issue identifiers as a number, `#number`, or issue URL, and expand Gist-backed attachments only when that extra content is useful.

>-

Converts static HTML mockups (especially multi-section pages under docs/inputhtmls) into Next.js App Router pages or React section components for this portfolio. Maps Tailwind-style tokens from the mock (primary, background-light/dark, surface, glass-card, animations) to project CSS variables and existing utilities in src/app/globals.css. Use when the user references docs/inputhtmls/*.html, asks to port a section or full page from HTML, or to sync a Storybook-style HTML export with the live site.

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.

Creates React components following RYLA patterns and file organization. Use when creating components, building UI, implementing features, or when the user mentions components, UI, or React.

>

Build a new design system or add components from specifications

Guidance for facet `effect/unstable/rpc/RpcServer` focused on APIs like make, layer, and layerHttp. Load after `effect-skill-router` when this facet is the primary owner.

Build a single skill from accepted CDRs based on user input

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 building, debugging, or optimizing Jazz applications. It covers Jazz's bindings with various different UI frameworks, as well as how to use Jazz without a framework. Look here for details on providers and context, hooks and reactive data fetching, authentication, and specialized UI components for media and inspection.

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

Run CADT integration tests, live API tests, and test data cleanup. Use when the user asks to run integration tests, run v1 or v2 tests, run live API tests, or delete test data.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Decision framework for GLSL shader projects. Routes to specialized shader skills (fundamentals, noise, SDF, effects) based on task requirements. Use when starting a shader project or needing guidance on which shader techniques to combine.

Use this skill when the task explicitly involves:

>

Reproduce and debug Android bugs on an emulator using ADB. Covers emulator setup, test data seeding, UI navigation via uiautomator, log capture, and screenshots. Use when the user asks to reproduce a bug, debug an issue on an emulator, or investigate an Android crash/behavior.

>-

office

Evidence-first ECC Tools burn and billing audit workflow. Use when investigating runaway PR creation, quota bypass, premium-model leakage, duplicate jobs, or GitHub App cost spikes in the ECC Tools repo.

Run the validation pipeline and produce a short markdown report.

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

After coding changes, fully verify and test the remote site (findtorontoevents.ca) using Playwright and HTTP fallback—events load, no JS errors, key features present.

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.

Rebuild the semantic token mapping from your palette. Maps surface, text, border, accent, and feedback tokens to specific palette shades based on project type.