Explorar skills

Auto-activate for uv build, hatch build, pyapp, Hatchling force-include, bundled frontend assets, PyApp onefile binaries, GitHub Actions build matrices, PYAPP_* env vars, cargo-zigbuild, or python-build-standalone. Use when packaging Litestar apps as wheels, onefile binaries, release artifacts, or asset-bundled distributions. Not for runtime deployment - use litestar-deployment.

Use when user invokes /research command with any source — URL, GitHub repo, YouTube video, podcast, Reddit post, academic paper, documentation page, product site, local file, or empty. Processes and indexes research materials with raw source preservation and topic-level synthesis coalescing. Do NOT use for quick factual questions — use /explain instead.

Auto-activate for uv build, hatch build, pyapp, Hatchling force-include, bundled frontend assets, PyApp onefile binaries, GitHub Actions build matrices, PYAPP_* env vars, cargo-zigbuild, or python-build-standalone. Use when packaging Litestar apps as wheels, onefile binaries, release artifacts, or asset-bundled distributions. Not for runtime deployment - use litestar-deployment.

Use when user invokes /harness-sync or wants to sync AI tool configurations across Claude Code, Cursor, and GitHub Copilot. Inventories installed skills, instruction blocks, and MCP configs on all detected platforms, reports divergence, and lets the user push or pull changes. Push path reuses harness-compile logic. Pull path updates harness.yaml and recompiles. Never overwrites without explicit co

Create a GitHub issue, commit, tag, and push a release. Detects repo type and runs mode-specific pre-flight checks with user confirmation at every step.

Referência rápida do AWS CLI v2 para desenvolvedores experientes, cobrindo computação, armazenamento, redes, segurança e CI/CD com GitHub Actions. Utilize para escrever comandos AWS, depurar acesso, configurar roles ou implantar no ECS.

Adversarial code review of uncommitted or staged changes. Includes a security scan via /security for full-tier reviews (skipped for docs-only changes). Use when the user asks to review code, check changes before pushing, or run a code review. Also use automatically before any git push, unless the user has explicitly said "push now" (unprompted); in that case run `codereview-skip && git push` witho

Use when writing Tailwind classes, fixing spacing issues, reviewing CSS, or auditing Tailwind patterns. Enforces v4 best practices for grid and responsive.

Use when reviewing file names, renaming files, fixing naming conventions, or auditing exports. Enforces consistent casing and suffix patterns.

Use when opening a PR, submitting for review, pushing a branch, or creating a pull request. Pushes and creates GitHub PRs with auto-assignment and description.

Generate a bias-free, ATS-optimized, skills-based job description for 2026. Runs a banned-word filter on gender-coded ("rockstar/ninja/guru/aggressive/dominate"), age-coded ("digital native/young/recent grad"), and ability-coded ("walk the floor") language; enforces skills-based requirements (drops "5+ years required" to "3 years preferred" unless regulatory); auto-injects pay transparency block f

Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes.