jira-verify
This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. It checks epic parent relationships and validates description completeness for coding assistants, developers, and stakeholders.
jira-journey
Read a JIRA ticket's Validation Journey section, execute the steps using Playwright MCP browser tools across all defined viewports, capture screenshots at each marker, generate evidence templates, and post to JIRA + GitHub PR using the jira-evidence skill.
jira-evidence
Upload screenshots to GitHub pr-assets release, update PR description with evidence, upload attachments to JIRA, post wiki markup comment, and move ticket to Code Review. Reusable by any skill that captures screenshots and generates evidence/comment.txt + evidence/comment.md.
jira-create
This skill should be used when creating JIRA epics, stories, and tasks from code files or descriptions. It analyzes the provided input, determines the appropriate issue hierarchy, and creates issues with comprehensive quality requirements including test-first development and documentation.
jira-add-journey
Add a Validation Journey section to an existing JIRA ticket by reading the ticket description, understanding the feature, and generating the journey steps, viewports, and assertions.
atomic-design-gluestack
|
container-view-pattern
This skill enforces the Container/View pattern for React components. It should be used when creating new components, validating existing components, or refactoring components to follow the separation of concerns pattern where Container handles logic and View handles presentation.
cross-platform-compatibility
This skill enforces cross-platform compatibility best practices for Expo apps targeting iOS, Android, and web. It should be used when creating new features, components, or screens to ensure they work correctly on all platforms. Use this skill when writing platform-specific code, using Platform.OS checks, creating platform-specific files (.web.tsx, .native.tsx, .ios.tsx, .android.tsx), or reviewing code for cross-platform issues.
directory-structure
This skill enforces the project's directory structure standards when creating or moving files. Use this skill when creating new components, screens, features, hooks, utilities, or any other code files to ensure they are placed in the correct location with proper naming conventions. Also use when reviewing file placement or restructuring code.
expo-env-config
This skill should be used when creating, modifying, or accessing environment variables in this Expo/React Native codebase. It enforces type-safe, validated environment configuration using Zod schemas. Use this skill when adding new environment variables, setting up env validation, or writing code that reads from process.env.
expo-router-best-practices
This skill should be used when creating new routes, configuring navigation layouts, implementing deep linking, or organizing the app/ directory structure in Expo Router projects. It provides best practices for file-based routing patterns.
gluestack-nativewind
This skill enforces Gluestack UI v3 and NativeWind v4 design patterns for consistent, performant, and maintainable styling. It should be used when creating or reviewing components, fixing styling issues, or refactoring styles to follow the constrained design system.
claude-code-action
Knowledge base for creating and configuring Claude Code Action GitHub workflows
lisa-integration-test
This skill should be used when integration testing Lisa against a downstream project. It applies Lisa templates, verifies the project still builds, and if anything breaks, fixes the templates upstream in Lisa and retries until the project passes all checks.
lisa-learn
This skill should be used when analyzing a downstream project's git diff after Lisa was applied to identify improvements that should be upstreamed back to Lisa templates. It validates the environment, captures the diff, correlates changes with Lisa template directories, categorizes each change, and offers to upstream improvements.
lisa-review-project
This skill should be used when comparing Lisa's source templates against a target project's implementation to identify drift. It validates the Lisa directory, detects project types, scans template directories, compares files, categorizes changes, and offers to adopt improvements back into Lisa. This is the inverse of lisa:review-implementation.
lisa-update-projects
This skill should be used when updating local Lisa projects in batches. It reads the project list from .lisa.config.local.json, checks out the target branch, pulls the latest, creates an update branch, runs the package manager update for @codyswann/lisa, migrates legacy CI workflows, checks for upstream changes, then commits, pushes, and opens a PR for each project.
mutation-testing
This skill should be used when performing AI-powered mutation testing to evaluate and improve unit test quality. It generates targeted code mutants, runs tests to identify surviving mutants, and strengthens or creates tests to kill them. Accepts a file path, directory, or defaults to git diff changed files.
apollo-client
This skill should be used when writing or modifying GraphQL operations, hooks, or mutations using Apollo Client 3.10. It enforces best practices for optimistic responses, cache updates, and TypeScript type generation. Use this skill when creating new queries/mutations, reviewing Apollo code, or troubleshooting cache issues.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
kalshi-markets
Access Kalshi prediction market data including market prices, orderbooks, trades, events, and series information. Use when the user asks about prediction markets, Kalshi markets, betting odds, market prices, or needs to search or analyze prediction market data.
ask-questions-if-underspecified
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
bootstrap-repo
Bootstrap or refresh a repo scaffold (governance docs, .codex folder, Tree.txt). Use only when explicitly invoked.
create-plan
Create a concise, executable plan for a coding task. Use when the user explicitly asks for a plan or when work is clearly multi-step.
decision-capture
Capture non-trivial decisions as a proposed entry for a repo's decision log (e.g., DECISIONS.md). Use when work involves meaningful tradeoffs.
governance-sync
End-of-work audit that identifies which governance artifacts should be updated based on actual changes. Use when wrapping a milestone/checkpoint or after multi-file/structural work.
intake-interview
Interview to extract intent, constraints, assumptions, and success criteria for a new system or major feature. Produces an Intake Brief (not a plan, not code).
personalize-repo
Tailor a bootstrapped repo into a project-specific operating system by capturing intent, constraints, and preferences, then updating docs and generating a repo-local REPO_PROFILE.json. Use only when explicitly invoked.
prediction-arbitrage-scout
Scout price discrepancies between Polymarket and Kalshi for discovery and comparison. Read-only; no execution.
cartographer
Generate a deterministic project map (Tree.txt + docs/PROJECT_MAP.md) for a repo. Use only when explicitly invoked.
email-best-practices
Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing.
send-email
Use when sending transactional emails (welcome messages, order confirmations, password resets, receipts), notifications, or bulk emails via Resend API.
shadcn
This skill should be used when the user asks to "add a component", "use shadcn", "install Button", "create Dialog", "add Form", "use DataTable", "implement dark mode toggle", "use cn utility", or discusses UI components, component libraries, or accessible components. Always use the latest shadcn/ui version and modern patterns.
stripe
>-
supabase-expert
>-
tailwindcss
This skill should be used when the user asks to "style with Tailwind", "add CSS", "configure theme", "use @theme", "add custom colors", "implement dark mode", "use container queries", "add responsive design", "use OKLCH colors", or discusses styling, theming, or visual design. Always use the latest Tailwind CSS version and modern patterns.
react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
authz-policy
Define and enforce authorization rules for protected actions, with tests and audit considerations.
state-modeling
Define client state shape and transitions for non-trivial UI flows (multi-step, branching, async, derived state).
performance-pass-ui
Identify and reduce avoidable UI performance regressions (render churn, heavy computations, oversized bundles) without behavior change.
frontend-test-additions
Add or extend frontend tests to cover intended behavior and critical UI states.
form-validation
Add input validation rules and UX patterns for forms (client-side validation, errors, submit gating) consistent with repo conventions.
data-fetching-integration
Wire UI to a data source with typed inputs/outputs, loading/error/empty states, and caching rules.
component-scaffold
Create a new UI component consistent with repo conventions (structure, typing, styling, exports).
a11y-semantics-pass
Improve semantics and accessibility coverage for UI changes (roles, labels, focus, keyboard, ARIA correctness).
persistence-layer-change
Implement schema/migration changes and update data access patterns safely.
observability-audit
Ensure logging/metrics/tracing and auditability match the quality bar for changed behavior.
job-worker-orchestration
Add background jobs and orchestration with idempotency, retries, and observability aligned to repo conventions.
integration-adapter
Build an external API adapter with timeouts, retries, idempotency, and error mapping.
endpoint-scaffold
Create a validated, authorized backend endpoint with error mapping and tests.
Page 1486 of 1705 · 85211 results
