convex-create-component
This skill guides the creation of reusable Convex components by defining isolated tables, schemas, and backend functions. It enforces architectural boundaries by requiring authentication, environment variables, and HTTP routing to remain in the parent application.
Is convex-create-component safe to install?
Review the source first: our audit of convex-create-component's source files found 3 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill instructs the agent to run shell commands for development and code generation, and requires reading/writing files to structure the Convex component.
How we audit skills: our security review methodology.
Who is this skill for?
Convex developers building modular backend logic, reusable integrations, or component-based architectures.
What can you do with it?
- Creating new Convex components within an existing application
- Extracting reusable backend logic into isolated modules
- Building third-party integrations with dedicated tables and workflows
- Packaging Convex functionality for reuse across multiple applications
How good is this skill?
Quality score: 5/10. The skill provides clear, actionable instructions and strict architectural rules for Convex component development. It includes specific code patterns and a checklist for validation.
What does the skill file contain?
# Convex Create Component Create reusable Convex components with clear boundaries and a small app-facing API. ## When to Use - Creating a new Convex component in an existing app - Extracting reusable backend logic into a component - Building a third-party integration that should own its own tables and workflows - Packaging Convex functionality for reuse across multiple apps ## When Not to Use - One-off business logic that belongs in the main app - Thin utilities that do not need Convex tables or functions - App-level orchestration that should stay in `convex/` - Cases where a normal Typ...
Frequently asked questions
Can I access process.env inside a component?
No. Component functions cannot read process.env. You must resolve environment variables in the parent app and pass them as arguments to the component.
How do I handle authentication in a component?
Keep authentication in the app. Components do not have access to ctx.auth. Resolve the user identity in the app and pass the necessary data to the component.
Can I use v.id('tableName') for parent app tables in component arguments?
No. Components cannot access the app's table namespace. Treat parent-owned IDs as strings at the component boundary.
Where should I mount HTTP routes for a component?
Mount HTTP routes in the app's convex/http.ts file, as components cannot register their own HTTP routes.
Related skills
simple
221.4KDevelopers and project managers who need a fast, lightweight decision-making process for feature design or component creation
A structured brainstorming framework for architectural and creative tasks that guides users from discovery to decision-making through a defined process flow.
shadcn
217.3KDevelopers building UI components and design systems using shadcn/ui
The shadcn skill manages UI components and design systems for projects using the shadcn/ui framework. It provides tools to search, add, debug, and style components, while enforcing strict composition and styling rules based on project-specific configuration.
convex-migration-helper
81.1KDevelopers managing Convex database schemas who need to perform breaking changes, backfills, or table restructuring
The Convex Migration Helper provides a structured workflow for executing breaking schema changes and data migrations in Convex applications. It emphasizes a widen-migrate-narrow pattern to ensure data integrity and zero-downtime deployments using the @convex-dev/migrations component.
convex-setup-auth
80.1KDevelopers building applications on the Convex platform who need to integrate authentication providers like Clerk, Auth0, WorkOS, or Convex Auth
This skill provides a structured workflow for implementing authentication, identity mapping, and access control within Convex applications. It guides the agent to identify the appropriate auth provider, consult official documentation, and apply secure patterns for protecting backend functions.