Loading...
Loading...
Found 1,921 Skills
JSON processing, parsing, and manipulation. STRONGLY PREFERRED for all JSON formatting, filtering, transformations, and analysis. Use instead of Python/Node.js scripts for JSON operations.
Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.
Comprehensive PowerPoint presentation creation, editing, and analysis using OOXML manipulation including slides, layouts, speaker notes, comments, and formatting. Use when asked to "create a presentation", "edit this PowerPoint", "add slides to .pptx", "extract presentation text", or "analyze slide structure". Provides raw OOXML access for advanced formatting, python-pptx for programmatic slide generation, and markitdown for text extraction. Works with .pptx files through ZIP archive extraction and XML manipulation for professional presentation workflows.
Provides 3-tier validation approach for Home Assistant dashboards including pre-publish validation (entity checks, config structure), post-publish verification (log analysis), and visual validation (browser console, rendering). Use when validating HA dashboards, checking dashboard configs, verifying entity IDs, debugging rendering issues, or before deploying dashboard changes. Triggers on "validate dashboard", "check HA config", "dashboard errors", "entity not found", or "test dashboard". Works with Home Assistant WebSocket/REST APIs, Chrome extension MCP tools, Python dashboard builders, and YAML dashboard configurations.
Apply the "How I Made Your Machine" coding style guide to implementation, refactoring, and code review tasks across TypeScript, Rust, and Python. Use when a request asks for this style guide, when improving maintainability and type safety, when modeling domain concepts with explicit variants/types, or when enforcing behavior-first testing.
Use this skill when spreadsheet files are the primary input or output. This means the user wants to: open, read, edit, or repair existing .xlsx, .xlsm, .csv, or .tsv files (e.g., add columns, calculate formulas, format, create charts, clean messy data); create new spreadsheets from scratch or from other data sources; or convert between spreadsheet file formats. Trigger this especially when the user references a spreadsheet file by name or path—even casually (such as "the xlsx in my downloads")—and wants to process it or generate content from it. It's also used to clean or reorganize messy tabular data files (rows with incorrect formatting, misaligned headers, garbage data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do not trigger this when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Specifies Poetry or Rye for dependency management in Python projects.
Create production-quality Django REST Framework APIs using Clean Architecture and SOLID principles. Covers layered architecture (views, use cases, services, models), query optimization (N+1 prevention), pagination/filtering, JWT authentication, permissions, and production deployment. Use when building new Django APIs, implementing domain-driven design, optimizing queries, or configuring authentication. Applies Python 3.12+ and Django 5+ patterns.
Precise, instant code structure queries for active development — answer 'who depends on this interface before I refactor it', 'how many modules break if I change this', 'what is the real impact radius of this feature change', 'which module is the true high-coupling hotspot in this legacy codebase'. Essential before any interface change, continuous refactoring task, sprint work estimation, or when navigating unfamiliar or large legacy codebases. Requires Python 3.10+ and shell. Use nexus-mapper instead when building a full .nexus-map/ knowledge base.
Enforce Vertical Slice Architecture (VSA) when building applications in any language (Go, .NET/C#, Java, Kotlin, TypeScript, Python, etc.) and any type (web API, mobile backend, CLI, event-driven). Organize code by feature/use-case instead of technical layers. Each feature is a self-contained vertical slice with a single entry point that receives the router/framework handle and its dependencies. Use when the user says "vertical slice architecture", "VSA", "organizar por feature", "feature-based architecture", "slice architecture", or when building a new app or feature and the project already follows VSA conventions. Also use when reviewing or refactoring code to align with VSA principles.
Use when the user wants Codex to build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository. Adapts the CLI-Anything methodology to Codex without changing the generated Python harness format.
Operate InstaVM infrastructure: run ephemeral sessions, create or manage VMs, host or deploy apps, take snapshots, clone machines, register SSH keys, expose shares, set egress, mount volumes, and use platform APIs. Use this whenever the user mentions InstaVM, instavm.io, the `instavm` Python SDK, `ssh instavm.dev`, app hosting, or VM lifecycle work, even if they do not explicitly say "InstaVM".