theme-routing-patterns
Navigation and routing rules for theme components. Always use locationPrefix. Never hardcode routes.
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
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.
Initialize and personalize your WIZRD repository. Run this after cloning to set up your company context, brand voice, and first client. The wizard researches your website first, then asks clarifying questions.
Use this skill for [purpose]. Triggers when user mentions [keywords]. Provides guidelines, templates, and standards for [domain].
Generate branded PDFs from markdown files. Use when converting case studies, proposals, or documentation to PDF format. Handles styling, templates, and batch conversion.
Use this skill for client issue triage, bug resolution, and troubleshooting. Triggers when user mentions client issue, bug, support ticket, problem, or troubleshooting. Provides response templates, severity ass...
Protobuf schema development guidelines. This skill should be used when writing, reviewing, or refactoring Protocol Buffer definitions to ensure consistency, backwards compatibility, and adherence to style guide...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.