software-testing
Software testing guidance with decision tree. Use when: (1) Writing or improving tests, (2) User asks about testing approaches, (3) Need guidance on test scope or assertions, (4) Working with specific test fram...
Découvrez les skills Entreprise, comparez leurs dépôts et consultez leurs instructions.
Software testing guidance with decision tree. Use when: (1) Writing or improving tests, (2) User asks about testing approaches, (3) Need guidance on test scope or assertions, (4) Working with specific test fram...
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or to...
Troubleshoot and fix failing GitHub Actions pipeline steps. Use when user reports a failing pipeline with error output.
Guide for characterization testing - capturing current system behavior to enable safe refactoring. Use when working with legacy code, undocumented systems, or code that needs modification but lacks tests. Helps...
Reviews conversation context to identify learnings and patterns that should be captured in skills. Use when the user asks to review the session for skill creation or updates.
Handle YouTube links and transcripts. Use when the user (1) pastes a YouTube URL that needs cleaning to short form, (2) requests transcript fetching from YouTube videos, or (3) works with YouTube video content....
Guidance for finding and adding bidirectional wikilinks when creating or updating content in the knowledge base. Use when user creates new content or wants to improve discoverability by adding links to related...
Create properly formatted documents for the knowledge base. Use when creating tasks, projects, bookmarks, companies, meetings, people, or research entries. Provides templates, frontmatter schemas, and managemen...
Work with Obsidian Bases - a native database system for creating dynamic views of notes using properties, filters, formulas, and multiple view layouts (table, cards, list, map). Use when creating or editing .ba...
Locked auth + authorization pattern for coverage-nextjs. Always reuse AuthContext + withAuth + existing helpers. Never create new auth routes or invent roles/permission logic.
Mandatory end-to-end schema verification. Never guess table/column/types/RLS behavior.
Vista Social Posts + Comments integration. Locks endpoints, params, request/response shapes, safe write rules, idempotency, and logging. Premium access assumed; do not mention tiers.
Navigation and routing rules for theme components. Always use locationPrefix. Never hardcode routes.
Data fetching patterns for theme components. Use existing fetchers. Server components fetch their own data.
Vista Social Profiles + Groups integration. Locks endpoints, allowed query params, canonical response fields, mapping expectations, and verification. Premium access assumed; do not mention tiers.
Shared Vista Social integration rules and references (base URL, auth, error handling, and global constraints). Use before any Vista Social endpoint work.
Vista Social analytics integration. Locks the allowed endpoints, query params, response field usage, storage/dedupe expectations, and proof requirements. Premium access assumed; do not mention tiers.
Vista Social Inbox + Reply integration. Enforces exact endpoints, params, payload shapes, idempotency, and audit logging. Premium access assumed; do not mention tiers.
Locked patterns for building n8n automations in this stack. Enforces triggers, idempotency, retries, logging, secrets handling, and strict JSON contracts between nodes.
Use for diagnosing, confirming, and correcting bugs/regressions/data mismatches/auth failures/broken UI/incorrect outputs. Enforces repro-first, trace-end-to-end, plan+approval gate, and proof-based fixes.
Enforce ownership boundaries between coverage-nextjs and template-coverage-creatives. Never mix responsibilities.
Enforce canonical payload/type definitions for cross-system boundaries in Coverage Creatives. Contracts are defined primarily via TypeScript types + inline edge function schemas + assistant instructions. No gue...
Complete checklist for implementing a new theme. Use this to verify all requirements are met before submission.
Locked Supabase client patterns for coverage-nextjs. Only 3 clients allowed. Never add new factories. Enforce env var rules and RLS boundaries.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.