data-prisma-feature-flags
To seed new feature flags in Cal.diy, create a Prisma migration:
$ npx -y skills add calcom/cal.com --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
To seed new feature flags in Cal.diy, create a Prisma migration:
Agent definition
data-prisma-feature-flags.mdtitle: Feature Flag Seeding impact: MEDIUM impactDescription: Proper feature flag setup enables controlled rollouts tags: prisma, feature-flags, migrations
Feature Flag Seeding
Creating Feature Flag Migrations
To seed new feature flags in Cal.diy, create a Prisma migration:
yarn prisma migrate dev --create-only --name seed_[feature_name]_feature
Migration File Location
The migration file should be placed in `packages/prisma/migrations/` with a timestamp prefix format:
20250724210733_seed_calendar_cache_sql_features/migration.sql
SQL Structure
Follow the pattern from existing feature seeding migrations like: `packages/prisma/migrations/20241216000000_add_calendar_cache_serve/migration.sql`
INSERT INTO "Feature" ("slug", "enabled", "type", "description", "createdAt", "updatedAt")
VALUES
('your-feature-slug', false, 'OPERATIONAL', 'Description of feature', CURRENT_TIMESTAMP, CURRENT_TIMESTAMP)
ON CONFLICT ("slug") DO NOTHING;The migration should INSERT the new features into the `Feature` table with:
- Appropriate type (like `OPERATIONAL`)
- Default `enabled` status for manual team enablement
Repo: calcom/cal.com
Other agents on caldiy.
- knowledge-base
This file contains domain knowledge about the Cal.diy product and codebase. For coding guidelines and rules, see [`rules/`](rules/).
Open agent - api-no-breaking-changes
**Impact: CRITICAL**
Open agent - api-thin-controllers
**Impact: HIGH**
Open agent - architecture-circular-dependencies
**Impact: CRITICAL**
Open agent - architecture-feature-boundaries
**Impact: CRITICAL**
Open agent - architecture-features-modules
The `packages/features` package should contain only framework-agnostic code: - Repositories (data access layer) - Services (business logic) - Core utilities and helpers - Types and interfaces
Open agent

