buildpad-ai
- 60 skills
- 0 followers
- 16 hours ago last updated
- ▌
- ▌ Buildpad Validate Gap · buildpad-ai bundleAnalyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.
- ▌ Buildpad Validate Impl · buildpad-aiValidate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
- ▌ Relational Permissions · buildpad-aiConfigure permissions on junction and child collections so that nested relational writes (M2M, O2M, M2A) are enforced at every level — not just the parent. Use when setting up write access for collections that participate in relational fields, or when debugging silent no-ops on nested mutations.
- ▌ Security And Hardening · buildpad-aiHardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.
- ▌
- ▌ Spec Driven Development · buildpad-aiSpec-driven development (SDD) methodology for Buildpad DaaS apps. Use when starting a new project, feature, or significant change, or when requirements are unclear. Routes work through the spec workflow — requirements.md (EARS) → design.md → tasks.md in .kiro/specs/ — via the buildpad-spec-* skills, or Kiro's native specs when working in Kiro.
- ▌ Buildpad Steering Custom · buildpad-ai bundleCreate custom steering documents for specialized project contexts. Use when creating domain-specific steering files.
- ▌ Buildpad Validate Design · buildpad-ai bundleInteractive technical design quality review and validation. Use when reviewing design before implementation.
- ▌ Performance Optimization · buildpad-aiOptimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.
- ▌ Buildpad Spec Requirements · buildpad-ai bundleGenerate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.
- ▌ Buildpad Verify Completion · buildpad-aiVerify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
- ▌ Incremental Implementation · buildpad-aiDelivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
- ▌ Git Workflow And Versioning · buildpad-aiStructures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
- ▌ Planning And Task Breakdown · buildpad-aiDecomposes specs into implementable tasks. Use when you have a spec or feature description and need to break it into small, verifiable tasks with acceptance criteria and dependency ordering.
- ▌ Debugging And Error Recovery · buildpad-aiGuides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
- ▌ Add I18N · buildpad-ai bundleAdd internationalization to a Buildpad app the way the Next.js App Router guide prescribes — locale-prefixed routes (app/[lang]), Accept-Language negotiation inside the existing auth middleware, server-loaded dictionaries handed to client pages through an I18nProvider, a LanguageSwitcher built on SelectDropdown, DaaS field-label translations via VForm's locale prop, and Directus-style content translations (a languages collection plus <collection>_translations junctions with optional per-locale workflow). Use when the user says add i18n, internationalization, internationalisation, localization, translations, multilingual, multi-language, bilingual, locale, language switcher, RTL, or wants content or UI in more than one language.
- ▌ Add Files · buildpad-aiScaffold the Buildpad Files module — a ready-made /files library (FileManager) and /files/[id] detail view (FileDetail) with drag-and-drop upload, import-from-URL, folders, grid/list views, preview, metadata editing, and bulk delete. Backed by the useFiles/useFolders hooks and asset thumbnails. Use when the user says add files, file manager, file library, files module, uploads page, or wants a document/media library.
- ▌ Add Users · buildpad-aiScaffold the Buildpad Users module — ready-made /users, /roles, and /policies admin pages (UsersManager/UserDetail, RolesManager/RoleDetail, PoliciesManager/PolicyDetail) with search, filters, role assignment, API tokens, and a per-collection permissions matrix. Backed by the useUsers/useRoles/usePolicies hooks. Use when the user says add users, user management, user admin, roles page, policies page, permissions matrix, or wants an access-control admin surface.
- ▌ Create Cron · buildpad-ai bundleCreate and manage DaaS cron jobs for scheduled background tasks. Sets up recurring jobs with cron expressions, sandboxed JS code, timezone support, execution history, and overlap protection. Use when the user needs scheduled tasks, recurring jobs, background processing, or timed automation.
- ▌ Create Rbac · buildpad-ai bundleSet up complete role-based access control for DaaS applications including roles, policies, permissions, access entries, and dynamic filters. Supports patterns like own_items, role_hierarchy, and public_read. For multi-tenancy, use /manage-scope which handles scope-aware role assignment natively. Use when the user needs roles, permissions, access control, or security configuration.
- ▌ Idea Refine · buildpad-aiRefines vague ideas into concrete proposals. Use when you have a rough concept that needs exploration, or when requirements are vague and need structured thinking before specification.
- ▌ Review Code · buildpad-aiPerform a comprehensive code review checking for quality, security, performance, accessibility, and DaaS/Buildpad compliance. Generates actionable feedback with severity levels. Use when the user says review-code, review this, check code quality, or wants a PR review.
- ▌ Add Buildpad · buildpad-ai bundleAdd Buildpad UI components to a DaaS project via CLI. Installs Copy & Own components from the registry including input, selection, boolean, datetime, media, rich-text, relations, layout, collection, and workflow components. Use when the user says add-buildpad, install components, or needs Buildpad UI.
- ▌ Add Microapp · buildpad-ai bundleSplit an app into a Main App plus domain-focused micro-apps that share one DaaS backend. Covers domain boundaries, collection ownership, shared RBAC, cross-domain contracts, and repo bootstrap. Load this skill FIRST to decide the split, then load add-microfrontend-zones (Multi-Zones, the default for Next.js micro-apps) or add-microfrontend (iframe composition and the auth bridge) to wire the composition. Use when the user says add-microapp, microapp, service boundary, or needs to split a large app into domain-focused micro-apps.
- ▌ Create Tests · buildpad-ai bundleGenerate comprehensive Playwright E2E and Vitest unit tests for DaaS features, API routes, pages, components, security (RLS), permissions, and load tests. Creates test files with proper setup, cleanup, and coverage. Use when the user needs tests, testing, E2E tests, API tests, security tests, load tests, or wants to test a feature.
- ▌ Manage Scope · buildpad-ai bundleSet up and manage multi-tenancy or organizational data partitioning using the DaaS-native scope system. Use whenever the user needs tenant isolation, org-level access control, regional data partitioning, or any hierarchical data separation. This is the standard multi-tenancy approach for DaaS applications.
- ▌ Buildpad Impl · buildpad-ai bundleImplement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
- ▌ Daas Platform · buildpad-ai bundleCore DaaS (Data-as-a-Service) platform knowledge including two-tier architecture, DaaS-compatible REST API, Supabase integration, Next.js App Router patterns, MCP tool usage, and environment configuration. Automatically loaded as background context for all DaaS development tasks.
- ▌ Generate Docs · buildpad-ai bundleGenerate or update documentation for DaaS application code changes including API references, component docs, hook docs, schema files, and changelogs. Use when the user says generate-docs, update docs, document this, or needs documentation.
- ▌ Buildpad Debug · buildpad-aiInvestigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.
- ▌ Create Feature · buildpad-ai bundlePlan and implement a complete feature using spec-driven development. Analyzes requirements, designs data model, selects Buildpad components, and produces spec artifacts (requirements.md, design.md, tasks.md) with a testing strategy. Use when the user wants to add a new feature, module, or capability to an existing DaaS project.
- ▌ Create Project · buildpad-ai bundleInitialize a new DaaS (Data-as-a-Service) application with Next.js, Supabase, and Buildpad UI. Creates the project foundation including scaffolding, authentication proxy, and test infrastructure, ready for spec-driven feature development. Use when the user wants to start a new project, create a new app, or bootstrap a DaaS application.
- ▌ Create Service · buildpad-ai bundleCreate and manage DaaS custom services for reusable code shared between extensions and cron jobs. Define utility libraries, API wrappers, validators, and formatters that can be injected via `services.custom('name')`. Use when the user needs shared logic across hooks/crons, wants to avoid code duplication, or needs testable service modules.
- ▌ Buildpad Review · buildpad-aiReview a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
- ▌ Create Workflow · buildpad-ai bundleCreate workflow state machines, content versioning, and multi-stage approval processes for DaaS collections. Sets up workflow definitions, assignments, required fields, and WorkflowButton UI. Use when the user needs content lifecycles (draft/published), approval workflows, or state machine transitions.
- ▌ Add Multitenancy · buildpad-ai bundleMulti-tenancy for DaaS applications — delegates to /manage-scope, the standard approach.
- ▌ Amplify Env Vars · buildpad-aiManage AWS Amplify environment variables for the project's main app or a microapp via Buildpad platform MCP tools (amplify_get_env_vars, amplify_set_env_vars). Use when a deployment needs env vars read, set, updated, or removed without opening the Amplify Console.
- ▌ Create API Route · buildpad-ai bundleGenerate a server-side Next.js API route for Supabase auth (login, logout, callback, session). These routes manage Supabase SSR cookies and run server-side. Do NOT use this skill to create proxy routes for DaaS data — the UI calls DaaS directly using Authorization Bearer tokens instead. Use when the user needs a new auth endpoint or server-side Supabase route.
- ▌ Create Component · buildpad-aiGenerate a React component following DaaS platform patterns. Performs mandatory Buildpad-first check before creating any custom component. Use when the user needs a new React component, page section, or UI element for a DaaS application.
- ▌ Create Migration · buildpad-ai bundleGenerate a Supabase PostgreSQL database migration with proper schema, RLS policies, indexes, triggers, and grants. Follows DaaS naming conventions and includes standard audit columns. Use when the user needs a database migration, table creation, schema change, or wants to add columns to a collection.
- ▌ Hooks Extensions · buildpad-ai bundleDaaS runtime extensions (hooks) and utilities API reference. Covers filter hooks (validation, transformation before save), action hooks (audit logging, notifications after save), and utility endpoints. Use DaaS extensions instead of implementing backend logic in Next.js API routes. Automatically loaded as background context.
- ▌ Worker Messaging · buildpad-aiOffload long-running work from a Next.js/Amplify app to a Buildpad runtime worker over RabbitMQ, and chain job → worker → worker. Covers the standard topic-exchange convention (a single `jobs` exchange, routing key = job type, a message envelope, dead-lettering), the producer side (publish a job, fire-and-forget) and the consumer side (a worker that consumes and may hand off to another worker), and how to fetch the live RabbitMQ connection from the Buildpad Platform MCP (`get_project_detail` → `messaging`). Use when a request is too slow for request/response, needs background processing, or when one worker must pass work to another. Because the producer (Next.js repo) and the consumer (Node.js worker repo) are SEPARATE repositories worked on by separate agents, this skill also generates a cross-repo handoff doc that carries the topic/routing key, the payload schema and how to read it, the user's intent, and everything the other repo's agent needs to implement the matching side.
- ▌ Add Microfrontend · buildpad-ai bundleCompose independent Next.js micro-apps into one Main App with sandboxed iframes and a postMessage bridge. Covers the host component, the message contract, auth token bridging, URL and scope syncing, sandbox flags, and CSP. Load add-microapp first to decide domain boundaries and bootstrap the repos, then load this skill to wire the composition. Use when the user says add-microfrontend, micro-frontend, iframe composition, or needs to embed an independent app in another app.
- ▌ Buildpad Steering · buildpad-ai bundleMaintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
- ▌ Create Collection · buildpad-ai bundleGenerate a complete collection with database migration, API routes, UI pages (list + form), TypeScript types, and tests. Creates everything needed for a new data entity in a DaaS application. Use when the user wants to add a new collection, table, entity, or data model to the project.
- ▌ Add External OAUTH · buildpad-ai bundleAdd external OAuth/OIDC identity provider integration where Next.js acts as the OAuth client. Creates OAuth proxy flow with PKCE, user provisioning via Supabase Admin API with default DaaS role assignment, and session management. Required for self-hosted Supabase without deployment access.
- ▌ Buildpad Discovery · buildpad-aiEntry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.
- ▌ Buildpad Reference · buildpad-ai bundleBuildpad UI component catalog and Buildpad-First rule reference. Lists all 40+ available components, hooks, services, and types. Enforces that raw Mantine form/input components must not be used when Buildpad provides equivalents. Automatically loaded as background context.
- ▌ Buildpad Spec Init · buildpad-ai bundleInitialize a new specification with detailed project description
- ▌ Buildpad Spec Batch · buildpad-aiCreate complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.
- ▌
- ▌ Buildpad Spec Tasks · buildpad-ai bundleGenerate implementation tasks from requirements and design. Use when creating actionable task lists.
- ▌ Code Simplification · buildpad-aiSimplifies code while preserving behavior. Use when code works but is harder to read or maintain than it should be. Use when complexity has accumulated and needs reduction.
- ▌ Context Engineering · buildpad-aiFeeds agents the right information at the right time. Use when starting a session, switching tasks, or when output quality drops due to missing context.
- ▌ Create Form Builder · buildpad-ai bundleScaffold and use the Buildpad Dynamic Form Builder — a visual drag-and-drop authoring UI (FormBuilder) plus a runtime renderer (DynamicForm) layered on CollectionForm/VForm. An admin arranges a collection's fields into sections, sets width/required/readonly/hidden, and authors conditional logic, saving a reusable FormDefinition into an fb_definitions collection (the schema is never mutated). Use when the user says form builder, build a form, dynamic form, form designer, visual form editor, conditional form, or wants end users to design forms.
- ▌ Grant Module Access · buildpad-ai bundleGrant application-level capability flags to users via DaaS Module-Level Access Keys. Keys such as `workflow:approve` or `system:logs` are registered in `daas_module_access_keys`, toggled on policies, and checked in React with `usePermissions().hasModuleAccess(key)` or in API routes with the OR-merge logic already built into the platform. Use when an application needs to gate a feature, page, or workflow command that is not tied to a collection CRUD operation.
- ▌ Subagent Delegation · buildpad-aiDelegates focused work to Kiro subagents that run in isolated context. Use when work can run in parallel, when a specialized agent fits (code review, testing, security, research), or when a long task would otherwise bloat the main conversation. Trigger with "run subagents to ...".
- ▌ Authentication Proxy · buildpad-ai bundleAuthentication proxy pattern reference. All browser-to-backend communication MUST go through Next.js API proxy routes. Never call Supabase auth or DaaS backend directly from client components. Automatically loaded as background context.
- ▌ Buildpad Spec Design · buildpad-ai bundleGenerate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.