Loading...
Loading...
Found 5,557 Skills
Deploy project to hosting platform — read stack YAML for exact config, detect local CLI tools (vercel, wrangler, supabase, fly, sst), set up database, push code, verify live deployment. Use when user says "deploy it", "push to production", "set up hosting", or after /build completes. Do NOT use before build is complete.
Expert-level Kamal deployment guidance for deploying containerized applications to any server. Use this skill when users ask about Kamal, container deployment, zero-downtime deployments, deploying Rails/web apps to VPS/cloud servers, kamal setup, kamal deploy, Docker deployment without Kubernetes, or deploying to Hetzner/DigitalOcean/AWS with Kamal. Also use when users mention DHH's deployment tool, 37signals deployment, or want an alternative to Heroku/Render/Vercel with self-hosted infrastructure.
Validate specifications, implementations, constitution compliance, or understanding. Includes spec quality checks, drift detection, and constitution enforcement.
Use when writing, fixing, editing, or refactoring Python tests. Enforces Clean Code principles—fast tests, boundary coverage, one assert per test.
This tool is used when users explicitly request "generate NSFC technical roadmap/roadmap drawing/roadmap/flowchart" or need to convert research content in grant proposals into a "printable, A4-readable" technical roadmap. It outputs editable source files (`.drawio`) and rendered results that can be embedded in documents (`.svg`/`.png`/`.pdf`). ⚠️ Not applicable: Users only want to modify the format/size of an existing image (should use image processing tools) or only want to polish the textual description of the technical roadmap (should directly rewrite the text).
Researches how the industry solves a defined issue, collects references from engineering blogs, open-source projects, and technical articles, then produces a design document with industry baseline, research summary, design goals, non-goals, and proposed design. Use when an issue definition exists in docs/issues/ and a concrete design is needed before implementation begins.
Use when coordinating complex research tasks requiring literature synthesis, quantitative validation, or multi-source integration across researcher, calculator, synthesizer, and fact-checker skills
Effect-TS (Effect) guidance for TypeScript. Use when building, refactoring, reviewing, or explaining Effect code, especially for: typed error modeling (expected errors vs defects), Context/Layer/Effect.Service dependency wiring, Scope/resource lifecycles, runtime execution boundaries, schema-based decoding, concurrency/scheduling/streams, @effect/platform APIs, Effect AI workflows, and Promise/async migration.
Akademiskt skrivande med vetenskaplig stringens — svenska eller engelska. [VAD] Uppsatser, rapporter, avhandlingar, litteraturöversikter, papers enligt högskolestandarder. IMRAD-struktur, Harvard/APA-referenshantering. Tvåspråkig skill. [NÄR] Use when: akademisk, vetenskaplig, uppsats, rapport, avhandling, litteraturöversikt, forskningstext, Harvard-referens, APA-referens, kandidat, master, doktorand, paper, thesis [SPRÅK] Svenska eller engelska — matcha input eller fråga [EXPERTISE] Academic writing, methodology, source criticism, qualitative/quantitative (SV/EN)
Manage Alibaba Cloud Data Lake Formation (DlfNext) via OpenAPI/SDK. Use for listing resources, creating or updating configurations, querying status, and troubleshooting workflows for this product.
Use when users want to define, codify, or update their brand identity and connect it to design systems. Produces a self-contained user-level skill at ~/.claude/skills/{brand-slug}/SKILL.md that enforces brand guidelines whenever visual assets or written content are created.
ChatGPT-style deep research strategy with problem decomposition, multi-query generation (3-5 variations per sub-question), evidence synthesis with source ranking, numbered citations, and iterative refinement. Use for complex architecture decisions, multi-domain synthesis, strategic comparisons, technology selection. Keywords: architecture, integration, best practices, strategy, recommendations, comparison.