Explore skills

Level of detail: overview | detailed | full-spec | production-ready.

Create a simple PR from staged changes with an auto-generated commit message.

JettraWUI

Use when the user mentions PageSpeed Insights, Core Web Vitals, LCP, TBT, CLS, site speed, page speed score, slow website, performance optimisation, or similar. Guides a phased, verification-gated approach — images first, fonts second, JavaScript third — specifically designed to avoid the regressions that typically occur when AI agents try to fix everything in one pass. Encodes lessons from a real

Numscript is a Domain-Specific Language (DSL) designed to model complex financial transactions, replacing complex and error-prone custom code with easy-to-read, declarative scripts.

Comprehensive Tailwind CSS utility-first styling patterns covering responsive design, layout, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Ideal for styling React/Vue/Svelte components, building responsive layouts, or optimizing CSS workflow.

Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements