Templates
Project and code templates
circom
by hairyf
Agent-oriented reference for the circom language and compiler—circuits, constraints, signals, templates, compilation, and safety.
performance-optimization
by sanky369
Master perceived performance through optimistic UI, skeleton screens, and latency strategies. Learn the difference between actual and perceived latency. Use when optimizing load times, designing loading states, or improving user confidence during operations.
documentation-templates
by xenitV1
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
plugin-authoring
by ABCFed
Use when creating, modifying, or debugging Claude Code plugins. Triggers on .claude-plugin/, plugin.json, marketplace.json, commands/, agents/, skills/, hooks/ directories. Provides schemas, templates, validation workflows, and troubleshooting.
claude-hook-builder
by skills-lock
Scaffold and auto-install Claude Code hook configs.
app-builder
by xenitV1
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
git-workflow
by 0xlayerghost
"[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review."
transform-encode-hls-video-with-transloadit
by transloadit
One-off HLS encoding (local video -> HLS renditions + playlist) using Transloadit via the transloadit CLI. Prefer builtin templates (builtin/encode-hls-video@latest) and download outputs locally via -o.
plan-roadmap
by jankneumann
"Decompose a proposal into prioritized OpenSpec change candidates with a dependency DAG. Scaffolds a proposal first if none exists."
implement-feature
by jankneumann
"Implement approved OpenSpec proposal with tiered execution (coordinated / local-parallel / sequential)"
session-log
by jankneumann
"Structured decision records for session logs and merge logs at phase boundaries"
tinker
by M4n5ter
Comprehensive guide for Tinker Cookbook supervised fine-tuning covering all patterns including high-level Cookbook abstractions, low-level API usage, streaming datasets, file-based data, Blueprint configuration, and vision-language models.
dough-adr-awareness
by terryyin
Use and cite this project's current Accepted Architectural Decision Records for architecture-shaped work, follow supersession, surface conflicts instead of silently drifting, and preserve human ownership of decisions and exceptions. Use when a task mentions ADRs or architectural constraints, may reverse an existing decision, or crosses architecture areas defined by this project.
plan-ticket
by OmniNode-ai
Generate a copyable ticket contract template - fill in the blanks and pass to /create-ticket
pr
by BenjaminG
Publish a pull request with automated type detection, Jira linking, PR templates, and Slack review message.
skill-creator
by crewship-ai
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
grey-haven-project-scaffolding
by greyhaven-ai
"Generate production-ready project scaffolds for Grey Haven stack with Cloudflare Workers, React + TypeScript, Python + Pydantic, PlanetScale, proper structure, and configuration. Use when starting new projects, creating microservices, setting up monorepo workspaces, initializing projects, or when user mentions 'new project', 'project scaffold', 'project template', 'project setup', 'bootstrap project', 'project starter', or 'initialize project'."
grey-haven-pr-template
by greyhaven-ai
Generate pull request descriptions following Grey Haven Studio standards with clear summary, motivation, implementation details, testing strategy, and comprehensive checklist. Use when creating or reviewing pull requests.
brainstorm
by Aedelon
Multi-agent brainstorming and strategic thinking on any complex topic. Explores the subject deeply, then spawns specialized sub-agents in parallel for diverse expert perspectives. MUST BE USED PROACTIVELY when user faces any decision, architectural choice, design question, strategic dilemma, or open-ended problem that benefits from multiple viewpoints. Triggers: "brainstorm", "explore ideas", "what are the options", "how should I approach", "pros and cons", "compare approaches", "what do you think about", "best way to", "should I use X or Y", "what's the best approach", "help me decide", "trade-offs", "alternatives", "strategy for", "how would you", "what's your take", "opinions on", "which one", "recommend", "suggest", "ideas for", "possibilities", "ways to", "what direction", "where to start", "what's better".
uv-workflow
by Aedelon
Master uv package manager for Python: project setup, dependency management, virtual environments, lockfiles, CI/CD integration, Docker builds, and migration from pip/poetry. MUST BE USED when user mentions: "uv", "uv add", "uv run", "uv sync", "uv init", "uv lock", "uv venv", "uv pip", "pyproject.toml", "python project setup", "python dependencies", "virtual environment", "venv", "pip install", "poetry to uv", "migrate from pip", "lockfile python", "requirements.txt", "setup.py", "pip freeze", "uv tool", "install package", "add dependency", "python environment", "new python project", "package manager python", "create project", "uv export", "uv cache", "uv python". 10-100x faster than pip. Covers init, add, sync, lock, run, Docker, CI/CD. NOT for npm/pnpm/yarn (JS toolchain), Rust cargo, or deployment (use deployment-assistant).
commit-message
by Aedelon
Ship workflow: review changes, generate conventional commit messages, push, and create PRs. MUST BE USED when user says: "commit", "git commit", "commit this", "save changes", "commit message", "ship", "ship it", "push", "create PR", "pull request", "ready to merge", "deploy this", "stage changes", "what changed", "review my changes", "conventional commit", or after completing a coding task. Reviews changes, generates commit, optionally pushes and creates PR. NOT for git branching/rebasing (use git-workflow), code review (use review command), or deployment configuration (use deployment-assistant).
security-audit
by Aedelon
Proactive security audit: OWASP top 10, dependency vulnerabilities, secrets detection, input validation, auth patterns, and secure defaults. MUST BE USED when user mentions: "security", "vulnerability", "audit", "OWASP", "CVE", "security review", "pentest", "injection", "XSS", "CSRF", "authentication", "authorization", "secrets", "hardcoded password", "secure", "npm audit", "pip-audit", "check security", "is this secure", "security risk", "data leak", "SQL injection", "command injection", "path traversal", "SSRF", "RCE", "privilege escalation", "supply chain", "dependency scan", "snyk", "trivy", "semgrep", "bandit". Scans code for vulnerabilities, checks dependencies, verifies auth patterns. NOT for explaining security concepts (use pedagogical-explain), or general code review (use code-review).
anti-hallucination
by Aedelon
CRITICAL SAFETY SKILL — Verify ALL technical claims, API signatures, library methods, code behavior, and factual statements before answering. Use Context7, WebSearch, and Read tools to confirm. MUST BE USED PROACTIVELY whenever: writing code that calls any library or API, answering technical questions, stating facts about frameworks or tools, mentioning version numbers, describing function behavior, recommending libraries, comparing technologies, or making any claim that could be wrong. Triggers: "how does X work", "what are the arguments for", "does this function exist", "is this the right syntax", "what version", "API reference", "documentation for", "how to use", "method signature", "return type", "parameters", "correct usage", "does this library support", "what's the default", "is this deprecated". Prevents hallucinated code, wrong function names, fabricated documentation, and incorrect facts. When in doubt about ANY technical claim, this skill MUST activate.
core-protocols
by Aedelon
Debug errors systematically by searching first, then analyzing, then proposing verified solutions. MUST BE USED when user reports: "error", "bug", "doesn't work", "fails", "crash", stack traces, exception messages, or any troubleshooting scenario. Triggers: "TypeError", "ImportError", "undefined is not a function", "segfault", "panic", "broken", "not working", "unexpected behavior", "regression", "failing", "exception", "traceback", "stack trace", "debug this", "why does this fail", "help me fix". Also enforces confidence levels and output templates. Prevents guessing solutions without research.