发现 数据库 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
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.
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.
All theme colors MUST use CSS variables. Never hardcode hex values. This ensures admin color controls work across all themes.
Use this skill when you are requested to create a PR for a feature branch.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。