Skill.md
- SKILL.md
--- name: design-md description: Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files ---
Library Skill.md library
Each one names the GitHub repo it came from, so you can check exactly what it tells your AI to do.
274991 Skill.md files
--- name: design-md description: Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files ---
--- name: design-orchestration description: Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. ---
--- name: design-philosophy description: Visual philosophy and art-direction for frontend. Use when creating high-concept work, campaigns, or when the user asks for a visual philosophy, manifesto, or unmistakable art-like aesthetic. ---
--- name: design-spatial description: Design — spatial composition ---
--- name: design-spells description: Curated micro-interactions and design details that add "magic" and personality to websites and apps. ---
--- name: design-taste-frontend description: Use when building high-agency frontend interfaces with strict design taste, calibrated color, responsive layout, and motion rules. ---
--- name: design-thinking description: Direction and intent for frontend design. Use with design when defining purpose, tone, domain, color world, and review bar; includes cross-domain lens from cinema, architecture, marketing, UX, automotive, industrial design. ---
--- name: design-ux description: UX / usability audit — heuristic evaluation of INTERACTIVE UIs (not just visual polish). Load with design when a UI "feels off", "sucks to use", is hard to learn, needs an instruction wall, or before shipping an interactive tool/editor/app. ---
--- name: detect-ai-text description: Estimate whether a document's prose was written by AI, with the linguistic tells and honest abstention on non-prose. Use when the user asks whether an essay, report, CV, submission, or article was AI-generated — for triage, not proof. ---
--- name: deterministic-design description: Render the UI and prove it's balanced + usable: a deterministic layout audit (centroid / optical-center / pixel-oracle balance via explicit math + annotated screenshot) plus a vision-judged Nielsen usability audit by a separate fresh-eyes judge. The measurement layer taste-only design skills lack. ---
--- name: dev-to-hashnode description: When the user wants to publish on Dev.to, Hashnode, or other developer blogging platforms. Trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform." ---
--- name: devcontainer-setup description: Creates devcontainers with Claude Code, language-specific tooling (Python/Node/Rust/Go), and persistent volumes. Use when adding devcontainer support to a project, setting up isolated development environments, or configuring sandboxed Claude Code workspaces. ---
--- name: devcontainers-nix description: Create reproducible development environments with Dev Containers, Nix flakes, and Devbox for consistent toolchains across teams. ---
--- name: developer-advocacy description: When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public. ---
--- name: developer-audience-context description: When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. ---
--- name: developer-churn description: When the user wants to understand, reduce, or recover from developer churn. Trigger phrases include "why developers leave," "churn rate," "win-back campaign," "at-risk users," "developer retention," "preventing churn," or "competitor switching." ---
--- name: developer-listening description: Monitor what developers say about your brand, competitors, and the problems they're solving. Track mentions and conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter, and Discord. ---
--- name: developer-newsletter description: When the user wants to create, write, or improve a newsletter for developer audiences. Trigger phrases include "newsletter," "email marketing," "developer email," "weekly digest," "dev newsletter," "email subscribers," "newsletter growth," or "email list." ---
--- name: developer-onboarding description: Get developers to "Hello World" fast with optimized quickstarts, tutorials, and sample apps. ---
--- name: developer-sandbox description: Design and build interactive playgrounds that let developers experience your product without commitment. This skill covers playground architecture, pre-populated examples, embedding strategies, gating decisions, and converting playground users to signups. ---
--- name: developer-seo description: SEO strategy for technical queries and developer audiences. Covers keyword research for "how to X in language" queries, error message SEO, Stack Overflow-style content, technical long-tail keywords, and competing with official documentation sites. ---
--- name: developer-signup-flow description: Design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. ---
--- name: development description: Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery. ---
--- name: devops-deploy description: DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento. ---