spec-shaping
Shape product ideas into actionable specs and sprint plans. Use when interviewing about a product plan, breaking specs into sprints, or turning vague ideas into well-scoped work.
set-note-description
Generate or update the description frontmatter property for a note. Selects Summary mode or Meta mode based on content type. Use when asked to create a description frontmatter summary for a note.
validating-startup-ideas
Find and validate startup ideas by mining user complaints, crafting premises, and navigating the idea maze. Use when discovering product opportunities, validating ideas, shaping solutions, researching user pain points, or exploring what to build.
visual-keywords
Generate keyword-rich strings for visual references to optimize for fuzzy search and recall. Focuses on searchability and keyword matching rather than prose or alt text.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
raycast-extensions
Build Raycast extensions using React and Node.js. Use for creating commands, UI components (List, Form, Grid), hooks (useFetch), AI integration, and manifest configuration.
react-useeffect
React useEffect best practices. Use when writing Effects, derived values, or data fetching. Teaches when NOT to use Effects and better alternatives like useMemo or key props.
file-naming
Analyze file content and propose intelligent renames using context-aware naming conventions. Date-prefixed for transactional/periodic documents, content-first for creative works. Use for organizing files, cleaning up downloads, or standardizing filenames.
obsidian-clis
Documents terminal control of Obsidian notes using the Obsidian app CLI (`obsidian`) when it is on PATH, and notesmd-cli when the app CLI is unavailable (headless or synced vault only). Covers note CRUD, search, vault structure (orphans, backlinks, unresolved links), tasks, properties, Bases, and plugin development when the app CLI is available. Use when the user mentions Obsidian CLI, obsidian-clis, notesmd-cli, terminal vault operations, or shell automation of Obsidian notes.
using-heavy-mcps
Use mcporter and jq to reduce token bloat from heavy MCPs like Sanity or Brain vault. Filter and compact tool outputs outside chat to feed only essential data back to the model.
extract-flow-scenario
Extracts a sequence of workflow events from conversation context into a structured markdown list. Surfaces actors, state changes, and pain points to serve as raw data for any later synthesis, design planning, or spec development. Use when asked to document an actual operational flow, user journey, or scenario from a conversation to capture exactly what happened.
culinary-assistant
Culinary guidance for cooking, recipes, and meal planning. Use for kitchen techniques, substitutions, and format conversion (Mela, Schema.org). Handles recipe parsing and improvements.
obsidian-templater
Help with templates/snippets for the Obsidian Templater plugin. Use to help generate Obsidian templates from natural language, understand and debug existing tp.* snippets, and adapt vault notes and workflows to Templater when users mention Templater, tp.*, or <% %>.
quantify-impact
Extract quantifiable metrics and business outcomes from experience descriptions through structured conversation. Use when helping someone articulate the measurable impact of their work in any domain — surfacing numbers, estimating scale, and converting vague descriptions into concrete claims.
use-tailwind-v4
Tailwind CSS v4 reference and migration guide. Use for v4 projects, syntax changes, upgrading from v3, and troubleshooting v4-specific utility patterns or configuration differences.
update-changelog
Update changelog files following Keep a Changelog conventions. Use for project changelogs or skill changelogs. Handles version sections, change type groupings, and skill-specific metadata updates.
worktree
|
risk-assessment
|
gap-analysis
|
incident-handling
|
commit-push-pr-flow
|
process-commit
|
review-flow
|
skill-maker
Create and edit Claude Code skills with TDD methodology. Use when creating or editing skills. Test with subagents before deployment, iterate until bulletproof.
frontend-design
Production-grade frontend interfaces with high design quality. Use when building web components, pages, or UI applications.
git-workflow
Smart git operations — commit messages, branch management, PR creation with summaries. Use for any git workflow.
spec-driven-implementation
MANDATORY implementation — breaks design into TDD tasks in docx/features/ tasks.md with Red-Green-Refactor. MUST activate after spec-driven-planning.
translate
Convert strategy docs to Python (Backtrader) and TradingView Pine Script. Use when translating strategies to code for backtesting.
research
Systematic trading strategy research — edge hypothesis, statistical validation, and strategy documentation (entry, exit, risk management).
pattern
Chart pattern identification — head and shoulders, double tops, triangles, flags. Documents pattern library with entry/exit criteria.
analyze
Technical analysis with indicators (RSI, MACD, MA), support/resistance, multi-timeframe trends, and sentiment. Use when analyzing markets or interpreting charts.
test-driven-development
Strict RED-GREEN-REFACTOR enforcement with no exceptions. Use when implementing features or fixing bugs. No production code without a failing test first.
systematic-testing
Systematic debugging framework and test generation patterns. Use when writing tests, debugging failures, or investigating bugs.
spec-driven-planning
MANDATORY planning — creates specs in docx/features/ with EARS requirements and technical design. MUST activate instead of ad-hoc planning for any new feature.
brainstorming
Collaborative refinement of rough ideas into clear requirements/designs through systematic questioning. Use when requirements are vague or exploring architectural options.
documentation
Generate function docs, API specs, architecture diagrams (Mermaid), READMEs, and code explanations. Use when documenting code or APIs.
deployment-patterns
CI/CD pipelines, deployment strategies (rolling, blue-green, canary), health checks, and rollback strategies. Use when setting up CI/CD or preparing production releases.
docker-patterns
Docker and Docker Compose — multi-stage Dockerfiles, networking, volumes, container security, and debugging. Use when containerizing applications or configuring Docker Compose.
eval-harness
Eval-driven development (EDD) — define pass/fail criteria before coding, measure with pass@k metrics. Use when defining completion criteria or measuring agent reliability.
security-review
OWASP Top 10 vulnerability detection. Use PROACTIVELY for code handling user input, auth, APIs, payments, or sensitive data.
search-first
Research-before-coding workflow — search for existing tools, libraries, and patterns before writing custom code. Use before writing custom utilities or adding new dependencies.
review
25-point code quality checklist covering structure, errors, security, performance, and testing. Use before commits or when reviewing code.
e2e-testing
Playwright E2E testing — Page Object Model, configuration, flaky test strategies, and CI/CD integration. Use when writing, debugging, or configuring E2E tests.
agentic-engineering
Operate as an agentic engineer — eval-first execution, task decomposition, cost-aware model routing (Haiku/Sonnet/Opus). Use when setting up AI-assisted workflows or optimizing model routing.
api-design
REST API design patterns — resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting. Use when designing, reviewing, or documenting API endpoints.
backend-patterns
Backend architecture patterns — repository/service layers, middleware, query optimization, caching, error handling, and auth. Use when implementing backend services, fixing N+1 queries, or adding caching.
database-migrations
Safe database schema changes — zero-downtime migrations, expand-contract pattern, and rollback strategies. Use when altering database tables, adding columns, or running schema changes.
social-media-api-best-practices
Best practices for integrating social media APIs (Instagram, TikTok, YouTube, Twitter/X, LinkedIn, Facebook, Threads, Pinterest, Bluesky, Snapchat, Google Business, Reddit, Telegram). Covers OAuth, AT Protocol, rate limiting, media uploads, encryption, and error handling. Use when building social media integrations, scheduling systems, or debugging platform API issues.
css-sass
Use Sass/SCSS for advanced CSS preprocessing with modern @use/@forward syntax
css-tailwind
Build with Tailwind CSS utility-first framework - configuration, customization, best practices
Page 1366 of 1561 · 78015 results
