GitHub
auth-locked
Locked auth + authorization pattern for coverage-nextjs. Always reuse AuthContext + withAuth + existing helpers. Never create new auth routes or invent roles/permission logic.
☆ 0View skill
WorkSync-Developement AI Skills
GitHub ↗Browse published AI skills maintained by WorkSync-Developement. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
21Repository stars across indexed skills
0Repository forks
126Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
schema-trace
Mandatory end-to-end schema verification. Never guess table/column/types/RLS behavior.
☆ 0View skill
GitHub
vista-social-posts
Vista Social Posts + Comments integration. Locks endpoints, params, request/response shapes, safe write rules, idempotency, and logging. Premium access assumed; do not mention tiers.
☆ 0View skill
GitHub
theme-routing-patterns
Navigation and routing rules for theme components. Always use locationPrefix. Never hardcode routes.
☆ 0View skill
GitHub
theme-data-fetching
Data fetching patterns for theme components. Use existing fetchers. Server components fetch their own data.
☆ 0View skill
GitHub
vista-social-profiles-groups
Vista Social Profiles + Groups integration. Locks endpoints, allowed query params, canonical response fields, mapping expectations, and verification. Premium access assumed; do not mention tiers.
☆ 0View skill
GitHub
vista-social-common
Shared Vista Social integration rules and references (base URL, auth, error handling, and global constraints). Use before any Vista Social endpoint work.
☆ 0View skill
GitHub
vista-social-analytics
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.
☆ 0View skill
GitHub
vista-social-inbox
Vista Social Inbox + Reply integration. Enforces exact endpoints, params, payload shapes, idempotency, and audit logging. Premium access assumed; do not mention tiers.
☆ 0View skill
GitHub
n8n-automation
Locked patterns for building n8n automations in this stack. Enforces triggers, idempotency, retries, logging, secrets handling, and strict JSON contracts between nodes.
☆ 0View skill
GitHub
debug
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.
☆ 0View skill
GitHub
architecture-context
Enforce ownership boundaries between coverage-nextjs and template-coverage-creatives. Never mix responsibilities.
☆ 0View skill
GitHub
integration-contracts
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...
☆ 0View skill
GitHub
theme-implementation-checklist
Complete checklist for implementing a new theme. Use this to verify all requirements are met before submission.
☆ 0View skill
GitHub
supabase-patterns
Locked Supabase client patterns for coverage-nextjs. Only 3 clients allowed. Never add new factories. Enforce env var rules and RLS boundaries.
☆ 0View skill
GitHub
feature-orchestrator
Generate the required feature plan file skeleton and enforce section outputs + Touched YES/NO gates.
☆ 0View skill
GitHub
staging-ui-first
UI-first rule + backend artifact staging under /supabase. Create only; do not apply/deploy/publish until post-UI gate.
☆ 0View skill
GitHub
theme-folder-structure
Required folder structure and naming conventions for theme implementations.
☆ 0View skill
GitHub
verification-final-report
Required verification steps and final report contents to update in the same plan file.
☆ 0View skill
GitHub
theme-component-contracts
Required component interfaces and props for theme implementations. Every theme must implement these exact contracts.
☆ 0View skill
GitHub
theme-css-variables
All theme colors MUST use CSS variables. Never hardcode hex values. This ensures admin color controls work across all themes.
☆ 0View skill
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.