80,000+ Skills to Supercharge Claude
The open directory for GitHub-integrated capabilities, tools, and prompts for your AI workflows.
cross-linking
by leovigna
Guidance for finding and adding bidirectional wikilinks when creating or updating content in the knowledge base. Use whe...
document-format
by leovigna
Create properly formatted documents for the knowledge base. Use when creating tasks, projects, bookmarks, companies, mee...
obsidian-bases
by leovigna
Work with Obsidian Bases - a native database system for creating dynamic views of notes using properties, filters, formu...
Locked auth + authorization pattern for coverage-nextjs. Always reuse AuthContext + withAuth + existing helpers. Never c...
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, idempoten...
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 ex...
Shared Vista Social integration rules and references (base URL, auth, error handling, and global constraints). Use befor...
Vista Social analytics integration. Locks the allowed endpoints, query params, response field usage, storage/dedupe expe...
Vista Social Inbox + Reply integration. Enforces exact endpoints, params, payload shapes, idempotency, and audit logging...
Locked patterns for building n8n automations in this stack. Enforces triggers, idempotency, retries, logging, secrets ha...
Use for diagnosing, confirming, and correcting bugs/regressions/data mismatches/auth failures/broken UI/incorrect output...
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 prim...
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 ru...
Generate the required feature plan file skeleton and enforce section outputs + Touched YES/NO gates.
UI-first rule + backend artifact staging under /supabase. Create only; do not apply/deploy/publish until post-UI gate.
Required folder structure and naming conventions for theme implementations.
Required verification steps and final report contents to update in the same plan file.
Required component interfaces and props for theme implementations. Every theme must implement these exact contracts.