create-collection

Generates database migrations, API routes, UI pages, and tests for new DaaS collections.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill create-collection-rkaaaa404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-collection
Source: https://github.com/Rkaaaa404/cyberhack-SYDT/tree/main/.agents/skills/create-collection
Command: npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill create-collection-rkaaaa404

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Adding a new data entity to a DaaS application normally requires hand-writing migrations, REST endpoints, list and form pages, TypeScript types, and tests. This Skill scaffolds the entire collection module in one pass while enforcing Buildpad component conventions and mandatory audit fields. ## Core Features & Use Cases - Full-stack scaffolding: Creates the Supabase migration, API routes (route.ts + [id]/route.ts), content pages (list + form), and API/page tests for a new collection. - Standard field groups: Automatically applies a decision tree for Group A audit fields (always), Group B workflow fields (state machines), and Group C scope fields (multi-tenancy), with copy-pasteable MCP JSON payloads. - Buildpad compliance enforcement: Mandates CollectionList and CollectionForm usage and includes a post-generation grep check that flags forbidden raw Mantine imports with a fix mapping table. - Use Case: A developer needs a new suppliers entity with approval workflow. The Skill generates the migration with audit and workflow fields, CRUD API routes, list/form pages using Buildpad components, and passing tests, then hands off to the create-workflow skill. ## Quick Start Ask the AI to create a new collection named suppliers with fields name:text, email:text, and active:boolean, including workflow support.

Frequently Asked Questions about create-collection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new collection with API routes and UI pages in a DaaS app?▼

Provide the collection name and fields as name:type pairs. The Skill generates the Supabase migration, CRUD API routes under app/api/items, list and form pages under app/content, and API plus page tests, all using Buildpad components.

What field types are supported when generating a collection?▼

Supported types include text, number, boolean, date, select, richtext, file, m2o, and m2m relations. Each maps to a database column type and a corresponding Buildpad component such as Input, Toggle, DateTime, SelectDropdown, or ListM2O.

Does every collection need audit fields like user_created and date_created?▼

Yes, Group A audit fields are mandatory for every collection. The DaaS platform does not auto-add them, so the Skill includes user_created, date_created, user_updated, and date_updated in every MCP field create call or SQL migration.

How do I add workflow or multi-tenancy support to a collection?▼

Add Group B workflow fields (workflow_instance, workflow_state) for state machines, then invoke the create-workflow skill. Add the Group C resource_uri field for tenant isolation, then invoke the manage-scope skill to register scope config.

Why does the Skill forbid raw Mantine components in generated pages?▼

Raw Mantine imports like TextInput, Select, or useForm bypass Buildpad conventions and break consistency. A post-generation grep check scans for these violations and maps each one to its Buildpad equivalent such as Input, SelectDropdown, or CollectionForm.