bkinsey808
32 verified skills64 total stars
ai-system
Explain, update, or audit the repository's cross-tool AI system. Use when the user asks how Copilot, Claude, Codex, Antigravity, Cursor, Gemini, skills, custom agents, or tool adapters are organized. Do not use for ordinary code changes that only need domain-specific implementation guidance.
tools2
code-comment-best-practices
Code comment conventions for TypeScript/React — JSDoc vs inline, when to explain why vs what, params/returns rules, spacing, placement, test comment rules, links in comments (@see vs {@link}), TODO/FIXME format, anti-patterns, writing style. Use when adding, updating, or reviewing comments in .ts or .tsx files. Do NOT use for general documentation questions unrelated to in-code comments.
development2
deployment-operations
Cloudflare deployment rollback, health monitoring, and production troubleshooting. Use when recovering from a failed deployment, checking deployment health, or diagnosing production issues.
testing2
file-splitting
Step-by-step guide for breaking large consolidated files into single-function files — naming, exports, import paths, test colocation, and validation. Use when refactoring consolidated utilities or test helpers into modular, maintainable pieces. Do NOT use for creating new files from scratch — this skill is for splitting existing files only.
tools2
hono-best-practices
Hono route handlers, Effect-TS integration, error mapping, middleware, validation, and architectural conventions for the API layer (`api/`). Use when creating or editing any handler, middleware, or route registration. Supersedes the former hono-api-patterns skill.
development2
lint-first-authoring
Lint-first coding workflow for this repo. Use when authoring or editing code and the goal is to produce changes that pass lint on the first try by matching local patterns, applying repo-specific constraints early, and validating before finishing. Do NOT use when the main task is fixing existing lint failures after they appear; use lint-error-resolution for that.
development2
naming-conventions
Symbol and file naming conventions for functions, types, variables, and React components. Use when naming a new function, hook, type, file, or variable, or when reviewing whether an existing name is appropriate.
development2
playwright-best-practices
Playwright E2E test conventions for this project — AAA pattern, translation-aware selectors, mock auth, staging DB sessions, two-user flows, debugging, and CI setup. Use when authoring or editing any Playwright spec, test helper, or E2E configuration. Do NOT use for unit tests or hook tests — load unit-test-best-practices instead.
tools2
scripts
Conventions for repository scripts (naming, execution, linting, testing).
development2
typescript-best-practices
TypeScript conventions for this repo (no `any`, explicit return types, JSDoc, exactOptionalPropertyTypes, ambient types, import style). Use when authoring or editing any `.ts` or `.tsx` file, resolving TypeScript strictness errors, or fixing type-related lint failures. Do NOT use for React-specific typing patterns (see react-best-practices skill) or JSDoc-only changes (see code-comment-best-practices skill).
development2
unit-test-hook-best-practices
Complete guide for testing React hooks — renderHook, Documentation by Harness, installStore, fixtures, subscription patterns, lint/compiler traps, and pre-completion checklist. Read docs/testing/unit-test-hook-best-practices.md for the full reference.
development2
zustand-best-practices
Zustand state management patterns for this project — store creation, selectors, Immer middleware, async actions with loading states, devtools, persist, and testing. Use when authoring or editing Zustand stores (use*Store files) or components that subscribe to stores. Do NOT use for React component structure or TypeScript-only utilities.
tools2
form-patterns
Project-specific form patterns using useAppForm, createFormSubmitHandler, and createApiResponseHandlerEffect. Use when building or editing any form with validation, submission, or API response handling in React.
development2
app-store-patterns
Zustand app store architecture — slice pattern, createXxxSlice factories, AppSlice type, useAppStore selectors, getTypedState for non-React code. Use when adding state to the store, creating new slices, or reading/writing store state in components or hooks.
development2
authentication-system
Dual JWT authentication system (visitor + user tokens) with Supabase. Use when implementing auth flows, token management, client-side token selection/caching, or working with auth state in React components.
tools2
cloudflare-cache-cicd
Cloudflare CDN cache management and GitHub Actions CI/CD workflows. Use when setting up or debugging CI/CD pipelines, handling cache invalidation, or troubleshooting workflow failures.
development2
deployment-strategies
Core Cloudflare Pages/Workers deployment workflow, environment variable configuration, and secrets management. Use when deploying code, configuring environments, or managing secrets.
development2
doc-best-practices
Documentation standards for this project — file naming, structure, writing style, formatting, skill+doc pairs, placement, and maintenance. Use when creating, updating, reviewing, or auditing any Markdown doc in `/docs/`, `README.md`, or `CONTRIBUTING.md`. Also use when deciding whether a new topic needs a doc, a skill, or both. Do NOT use for in-code JSDoc/TSDoc comments — load code-comment-best-practices instead.
development2
file-organization
File organization, naming conventions, and import patterns (no barrel files, direct imports, kebab-case docs, ESM config). Use when creating new files, modules, refactoring imports, or setting up directory structures.
development2
internationalization
i18n patterns for this project — useLocale/useLanguage/useCurrentLang hooks, URL-based language routing, adding translation keys, SupportedLanguageType. Use when adding UI text, building localized links, or working with language switching.
development2
lint-error-resolution
Guide for resolving lint errors in strict TypeScript/React environments — oxlint, ESLint, and TypeScript compiler errors. Use when encountering lint, oxlint, ESLint, or tsc errors in files being edited. Do NOT use for runtime errors unrelated to linting or TypeScript compilation.
development2
manage-page-patterns
Patterns for admin/manage pages (community manage, event manage) — local actionState, runCommunityAction/runAction helpers, realtime as primary update path. Use when building manage pages with mutations like invite, kick, add, or remove.
tools2
playwright-testing
Playwright testing workflows, templates, and tips for stable, non-flaky E2E tests in dev and CI environments. Use when writing Playwright specs for critical user flows (auth, navigation, features).
development2
react-best-practices
React 18+ conventions for this project — React Compiler (no manual memoization), ReactElement ambient type, useEffect comment rule, plain function declarations, file and import conventions. Use when authoring or editing any React component, hook, or page. Do NOT use for general TypeScript-only utilities with no React imports — load typescript-best-practices instead.
development2
realtime-rls-architecture
RLS policy architecture for Supabase Realtime subscriptions — access control layers, JWT validation logic for visitor/user tokens, verified production policy templates. Use when writing or reviewing RLS policies for tables used with Realtime. Do NOT use for debugging active subscription failures — load realtime-rls-debugging instead.
development2
realtime-rls-debugging
Debugging Supabase Realtime subscriptions that connect but deliver no updates, empty filter errors, and RLS silent-rejection diagnosis. Use when Realtime subscriptions are not delivering messages or updates.
development2
skill-best-practices
Guidance for writing SKILL.md files in this repository. Use when creating, updating, reviewing, or auditing a SKILL.md — including front matter, trigger design, sizing, output format, error handling, linking, safety, and composition. Do NOT use for general documentation questions unrelated to skill authoring.
development2
source-refactoring
Patterns for splitting functions and components into their own files. Ensures consistent exports, JSDoc preservation, and test colocation. Use when refactoring large files or extracting reusable logic.
development2
supabase-client-patterns
Which Supabase client to use in React (public vs token-auth vs withAuth), safe-query helpers (callSelect/callInsert/callUpdate), and SupabaseClientLike type. Use when querying Supabase from a React component, hook, or fetch function.
tools2
unit-test-best-practices
Vitest unit test authoring for this repo — setup, mocking, API handler testing, and common pitfalls for non-hook code. Use when the user asks to add, update, fix, or review unit tests for utilities, components, API handlers, or scripts. Do NOT use for React hook tests — load unit-test-hook-best-practices instead.
development2
write-skill
How to write, update, or split skill files in this repo. Use when creating a new SKILL.md, updating an existing one, or deciding whether to put content in a skill vs. docs/.
testing2
effect-ts-patterns
Effect-TS API patterns for Hono server (error handling, schema validation, service composition, dependency injection). Use when building API handlers, services, or working with structured error types.
development2