Explore skills
Showing 62011–62040 of 77104 skills
Run svelte-check (or `pnpm check`) after EVERY edit to any .svelte or .ts file under frontend/src. Triggers on: edit/save .svelte / .ts, refactoring Svelte 5 components, after extracting helpers, after changing $state/$derived/$props, after migration, after converting handlers (oninput/onchange/bind), before reporting work as done, before git commit. Use to: verify types, catch pre-existing vs newly introduced errors, confirm refactor safety, validate AGENTS.md policy compliance. Always read output END-TO-END before reporting.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexDesign and implement web animations that feel natural and purposeful. Use this skill proactively whenever the user asks questions about animations, motion, easing, timing, duration, springs, transitions, or animation performance. This includes questions about how to animate specific UI elements, which easing to use, animation best practices, or accessibility considerations for motion. Triggers on: easing, ease-out, ease-in, ease-in-out, cubic-bezier, bounce, spring physics, keyframes, transform, opacity, fade, slide, scale, hover effects, microinteractions, Framer Motion, React Spring, GSAP, CSS transitions, entrance/exit animations, page transitions, stagger, will-change, GPU acceleration, prefers-reduced-motion, modal/dropdown/tooltip/popover/drawer animations, gesture animations, drag interactions, button press feel, feels janky, make it smooth.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexUse when the user asks to create, edit, rebuild, or refine editable diagrams in `.drawio` / diagrams.net format, especially for academic figures such as system architecture diagrams, technical roadmaps, workflow diagrams, method pipelines, module relationship diagrams, and experiment flowcharts. Use this skill when the user wants publication-ready outputs with both an editable source file and a PNG export, or when an existing figure image needs to be rebuilt into a clean editable academic-style diagram.
SHALINS428/Codex-drawio-skill
Stars: 29Claude CodeCodexAutonomous novel writing CLI agent with web workbench (JiaOS Studio) - use for creative fiction writing, standalone short-fiction packages, cover generation, novel generation, style imitation, chapter continuation/import, EPUB export, AIGC detection, and fan fiction. Native English support with 10 built-in English genre profiles (LitRPG, Progression Fantasy, Isekai, Cultivation, System Apocalypse, Dungeon Core, Romantasy, Sci-Fi, Tower Climber, Cozy Fantasy). Also supports Chinese web novel genres (xuanhuan, xianxia, urban, horror, other). Multi-agent pipeline, two-phase writer (creative + settlement), stronger long-form chapter craft rules, hook-ledger payoff checks, 33-dimension auditing, token usage analytics, creative brief input, structured logging (JSON Lines), multi-model routing, custom OpenAI-compatible provider support, and JiaOS Studio web UI for visual book management, short-fiction runs, cover generation, chapter review, real-time writing progress, market radar, and analytics.
zxerai/novelix
Stars: 79Claude CodeCodexCloses an approved RFC into the permanent record: drafts ADR(s) for decisions it produced, updates RFC status/links, and lists concrete arc42 + C4 sections to update in the same change. Use after review when the proposal must become history and the system map must catch up. Invoked via design-docs-template.
openmove/engineering-design-playbook
Stars: 0Claude CodeCodexScaffolds the next numbered ADR from the MADR template (minimal by default), status proposed, and updates the ADR index. Use when a decision is settled and must be recorded immutably. Invoked via design-docs-template.
openmove/engineering-design-playbook
Stars: 0Claude CodeCodexScaffolds the next numbered RFC from the repo's RFC template, updates the RFC index, and leaves a Draft ready to write. Use when a change has real trade-offs and needs a proposal before code. Invoked via design-docs-template.
openmove/engineering-design-playbook
Stars: 0Claude CodeCodexHygiene pass on a draft RFC: aligns names, Mermaid diagrams, prose, and examples to one canon; removes stale noise after iteration so readers are not misled. Use before review or close-loop when the RFC grew messy. Invoked via design-docs-template.
openmove/engineering-design-playbook
Stars: 0Claude CodeCodexCloses an approved RFC into the permanent record: drafts ADR(s) for decisions it produced, updates RFC status/links, and lists concrete arc42 + C4 sections to update in the same change. Use after review when the proposal must become history and the system map must catch up. Invoked via design-docs-template.
openmove/engineering-design-playbook
Stars: 0Claude CodeCodexScaffolds the next numbered ADR from the MADR template (minimal by default), status proposed, and updates the ADR index. Use when a decision is settled and must be recorded immutably. Invoked via design-docs-template.
openmove/engineering-design-playbook
Stars: 0Claude CodeCodexScaffolds the next numbered RFC from the repo's RFC template, updates the RFC index, and leaves a Draft ready to write. Use when a change has real trade-offs and needs a proposal before code. Invoked via design-docs-template.
openmove/engineering-design-playbook
Stars: 0Claude CodeCodexHygiene pass on a draft RFC: aligns names, Mermaid diagrams, prose, and examples to one canon; removes stale noise after iteration so readers are not misled. Use before review or close-loop when the RFC grew messy. Invoked via design-docs-template.
openmove/engineering-design-playbook
Stars: 0Claude CodeCodexChecklist for adding a new TriggerCrud-based trigger type to Windmill (Azure, GCP, Kafka, etc.). Use when wiring a new trigger kind across backend, frontend, CLI, and capture infrastructure.
devorb1t/windmill
Stars: 0Claude CodeCodexAuthor and run black-box benchmark cases for the Windmill AI generation modes (flow/app/script/cli/global) in ai_evals/. Use when adding or changing eval cases, or when running before/after benchmarks for AI chat / copilot changes.
devorb1t/windmill
Stars: 0Claude CodeCodexCreate a git commit with conventional commit format. MUST use anytime you want to commit changes.
devorb1t/windmill
Stars: 0Claude CodeCodexCode review the current PR (or branch diff against main) for bugs, security, and AGENTS.md compliance. MUST use when asked to review code.
devorb1t/windmill
Stars: 0Claude CodeCodexRun the CI Codex PR review locally against this branch's unpushed work (committed + uncommitted) before pushing. Same policy, model, and reasoning effort as the codex-pr-review GitHub action.
devorb1t/windmill
Stars: 0Claude CodeCodexGuidance for adding native trigger services to Windmill. Use when implementing or modifying native trigger integrations across the backend and frontend.
devorb1t/windmill
Stars: 0Claude CodeCodexRust coding guidelines for the Windmill backend. MUST use when writing or modifying Rust code in the backend directory.
devorb1t/windmill
Stars: 0Claude CodeCodexSvelte coding guidelines for the Windmill frontend. MUST use when writing or modifying code in the frontend directory.
devorb1t/windmill
Stars: 0Claude CodeCodexHow to safely update SQLx offline query cache. MUST use when SQL queries change.
devorb1t/windmill
Stars: 0Claude CodeCodexAll-in-one fullstack dev engine. /aura: 46 modes (build/fix/clean/deploy/review/spec/lore/ax/experiment/payment/debug/qa/orchestrate/escalate+), 6-layer security with 32 hooks, tiered models (ZERO/ECO/PRO/MAX), 8 languages, 16 specialized agents, SPEC/EARS/TRUST5/XLOOP/RALF/Autopus absorbed. ~55% token savings.
smorky850612/Aurakit
Stars: 46Claude CodeCodexInteractive SEO content-writing and humanization engine by Pardeep Kumar (ToolNPlay.com). Guides the user step by step through focus keyword selection, 10 intent-matched SEO title suggestions (with regeneration), word count and FAQ selection, up-to-date grounded research without fake data, natural human-sounding prose editing, a 16:9 website-ready featured image, and a deterministic on-page SEO and anti-AI audit. Use whenever the user asks to write an SEO blog post, article, pillar guide, product page, or refresh existing web content.
pardeeppatel/seo-friendly-content
Stars: 0Claude CodeCodexReview code for quality, simplicity, and common mistakes before declaring work complete.
juspay/vira
Stars: 20Claude CodeCodexIteratively study and apply elegant coding patterns. Each iteration - understand the code, research what simple and elegant code looks like, apply learnings, verify with CI. Use as a standalone refactoring pass or when the user asks to make code more elegant, simple, or idiomatic.
juspay/vira
Stars: 20Claude CodeCodexAudit code for correctness and rigor — logic errors, silent error swallowing, wishful thinking, and unjustified fallbacks. This is not a style review; it's a logic review. Use when you want a focused correctness audit separate from the full code-police pass.
juspay/vira
Stars: 20Claude CodeCodexCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
juspay/vira
Stars: 20Claude CodeCodexUse this when writing or reviewing Haskell code. Covers error handling, type safety, idiomatic patterns, HLint compliance, Aeson usage, and testing.
juspay/vira
Stars: 20Claude CodeCodexEvaluate code (especially LLM-generated) for structural simplicity using Rich Hickey's "Simple Made Easy" framework. Use this skill whenever reviewing a PR, diff, or code snippet for accidental complexity — particularly when the code was generated by an AI coding assistant and line-by-line review isn't feasible. Also use when the user asks about complecting, simplicity vs. easiness, structural coupling, or concept deduplication. Trigger on phrases like "is this simple", "does this complect", "review for complexity", "structural analysis", or any reference to Hickey, Simple Made Easy, or grey-box review.
juspay/vira
Stars: 20Claude CodeCodexEvaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).
juspay/vira
Stars: 20Claude CodeCodex