Monitor GitHub Actions CI/CD workflows after git push. ALWAYS invoke this skill automatically immediately after any successful `git push` command — do not wait for the user to ask. Also invoke when the user says monitor CI, check if CI passed, watch the workflow, CI の結果を確認, ワークフローを監視, or provides a GitHub Actions URL. This skill is essential after pushing code, Claude must verify CI results proactively so the user never has to manually check GitHub.
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.
Skill for building with the Astro web framework. Helps create Astro components and pages, configure SSR adapters, set up content collections, deploy static sites, and manage project structure and CLI commands. Use when the user needs to work with Astro, mentions .astro files, asks about static site generation (SSG), islands architecture, content collections, or deploying an Astro project.
Methodology for iteratively improving agent-facing instructions (skills / slash commands / CLAUDE.md / code-gen prompts) by having a bias-free executor run them and evaluating two-sidedly (executor self-report + instruction-side metrics) until improvements plateau. Use after creating or revising a prompt or skill.
Review and refactor code in your project according to defined instructions
Tauri v2+ cross-platform app development with Rust backend. Use when configuring tauri.conf.json, implementing Rust commands (#[tauri::command]), setting up IPC patterns (invoke, emit, channels), configuring permissions/capabilities, troubleshooting build issues, deploying desktop/mobile apps, or setting up E2E testing with tauri-driver + selenium-webdriver. Triggers on Tauri, src-tauri, invoke, emit, capabilities.json, tauri-driver.