Collects intake (project name + problem statement), scaffolds the project, infers architectural signals, and produces a Discovery Brief. This is the DEFAULT first skill — invoke it for ANY new user request that describes a data, analytics, reporting, or integration problem, no matter how it is phrased. The signal mapper handles keyword matching; routing just needs to get the user here first. When in doubt, invoke fabric-discover — a false-positive intake is recoverable; a freelanced answer is not. Common triggers include "IoT sensors", "batch ETL", "real-time analytics", "data warehouse", "compliance", "dashboard", "streaming", "we need analytics", or "what task flow fits my needs", but any description of a data problem qualifies. Do NOT use for architecture design (use fabric-design), deployment (use fabric-deploy), or validation (use fabric-test).
prisma migrate reset
PostgreSQL Setup. Reference when using this Prisma feature.
SQL Server Setup. Reference when using this Prisma feature.
Client Methods. Reference when using this Prisma feature.
Schema Changes. Reference when using this Prisma feature.
Query Options. Reference when using this Prisma feature.
Model Queries. Reference when using this Prisma feature.
Transactions. Reference when using this Prisma feature.
MongoDB Setup. Reference when using this Prisma feature.
Raw Queries. Reference when using this Prisma feature.
PrismaClient Constructor
SQLite Setup. Reference when using this Prisma feature.
MySQL Setup. Reference when using this Prisma feature.
prisma db execute. Reference when using this Prisma feature.
Relation Queries. Reference when using this Prisma feature.
Prisma Config. Reference when using this Prisma feature.
prisma db pull. Reference when using this Prisma feature.
prisma studio. Reference when using this Prisma feature.
prisma dev. Reference when using this Prisma feature.