@trycompai
Organization
We're building an open source platform to help companies get SOC 2, GDPR and ISO 27001 compliant.
32 skills1 repository 2.1K
Apply the project’s core rules when changing TypeScript code: use Bun for package tasks, prefer the design system, validate external data without unsafe types, and follow conventions for data fetching and UI state. Run type and lint checks after changes.
Design clearer prompts for AI tasks by setting success criteria, specifying output formats, adding examples, organizing context with XML tags, and assigning a role. The guidance helps you draft and refine instructions for more consistent responses.
Use this skill when changing subscription billing with Stripe. It guides catalog and SKU updates, checkout, local entitlements and usage records, audit events, and webhook handling that tolerates retries and out-of-order delivery.
Generate a TypeScript MCP server from an OpenAPI spec with Speakeasy, exposing API operations as tools for AI assistants. The skill covers scopes, workflow configuration, authentication, and local or Docker-based ways to run the server.
Build interfaces that follow Trigger.dev v4 task runs as they happen. The skill covers subscriptions to run status, metadata, tagged runs, and streamed data from backend code or React hooks, using scoped access tokens for reads and triggers.
Write Trigger.dev v4 tasks with validated inputs, scheduled runs, retries, waits, and task-to-task triggers. The skill explains how to handle Result values returned by waiting for tasks and highlights patterns that the v4 SDK does not support.
Use this skill to define recurring Trigger.dev tasks with cron schedules, set time zones and environments, and manage schedules through code or the dashboard. It also explains schedule payloads and common conditions that prevent a task from running.
Create and maintain Cursor rules in `.mdc` files. Learn how frontmatter, glob patterns, and automatic or manual application control which guidance applies, plus ways to organize rules and troubleshoot rules that do not apply or conflict.
Use this skill to investigate failed SDK generation from an OpenAPI spec. It helps classify errors, identify likely root causes, and outline whether an overlay can address them, the spec needs changes, or a human decision is required.
Use the shared CheckResultsService to retrieve the latest real results from connected integration checks, such as per-user 2FA status or bucket findings. It explains how to filter resources, validate check-specific data, and shape results for a feature.
Create, apply, and validate OpenAPI overlay files to customize SDK generation without editing the source specification. Use JSONPath to target operations or schemas and configure naming, grouping, retries, pagination, headers, enum handling, or custom security.
Configure a Trigger.dev v4 project through `trigger.config.ts`, including task directories, runtime, retries, lifecycle hooks, and build extensions. Examples cover tools such as Prisma, Python, Playwright, and FFmpeg, plus custom extensions and environment settings.
Build React forms with React Hook Form and Zod. The skill shows how to define validation schemas, connect fields, display errors, handle submission state, and manage complex or dynamic inputs.
Review specified files for design system usage, replace legacy @trycompai/ui components and lucide-react icons with available @trycompai/design-system equivalents, and run the app type check to verify the migration.
Prepare an isolated worktree for a feature, ticket, or bugfix by following the repository’s setup conventions for environment files, databases, dependencies, and development servers. It also explains how to avoid conflicts when multiple worktrees are active.
Review old Git worktrees and their related Postgres databases, classify which appear safe to remove, and present recommendations before cleanup. The process checks branch and pull request status, local changes, and unpushed commits to protect work that may still be needed.
Guide API endpoint changes so request DTOs, runtime validation, OpenAPI documentation, and MCP tool metadata stay aligned. It covers discoverability, authentication, uploads, long-running tasks, and response types that MCP tools cannot handle.
Apply consistent TypeScript and React practices for safer data handling, component structure, state, and file organization. The guidance also covers readable code, accessible interactions and forms, event naming, and user feedback with Sonner toasts.
Set up Better Auth for TypeScript applications, including server and client configuration, database adapters, sessions, email and social sign-in, and plugins. The guide also highlights environment variables, schema generation, and security settings to review.
Review changed code after implementation for readability, repeated logic, inconsistent patterns, unsafe boundary handling, redundant casts, and dead code. The checklist guides cleanup and calls for a TypeScript type check after fixes.
Use these guidelines for visible UI changes to plan layouts across mobile, tablet, desktop, and large screens. They cover mobile-first breakpoints, design-system components, overflow, touch targets, long content, and checks at four screen widths.
Review security-sensitive code for serious flaws such as broken access control, tenant isolation errors, injection, exposed secrets, SSRF, and unsafe file handling. Confirm high-severity findings, fix them, and report remaining issues with their impact.
Structure data fetching so server pages provide initial data to client components, while SWR refreshes it and handles mutations through an API client. The guidance covers cache keys, server and client responsibilities, and URL based organization context.
Review specified files for outdated hook and API patterns, then replace them with the prescribed SWR hooks, API clients, or server API calls. The guidance covers data fetching, mutations, cache updates, and response handling, followed by a typecheck command.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)