convex-self-hosting

The convex-self-hosting skill provides a standardized, repeatable framework for integrating Convex static hosting into modern web applications. Designed for developers and AI agents, this skill ensures that infrastructure setup—such as configuring Convex static assets, setting up upload APIs, and defining HTTP routes—aligns with the latest upstream practices from get-convex/self-hosting. It acts as an operational bridge between your codebase and the Convex runtime, facilitating smooth transitions from development to production.

• Automated synchronization with upstream Convex integration guides, including manual setup requirements and package version verification.

• Multi-platform support for Vite, Next.js, and Expo web exports, ensuring correct build pipelines and environment variable handling.

• Intelligent routing configuration for root path hosting or custom prefixes like /app to support single-page application (SPA) fallbacks.

• Standardized deployment workflows, including both one-shot deployments and decoupled two-step processes (backend updates followed by static asset uploads).

• Proactive troubleshooting for common issues like 404 errors on static routes, incorrect deployment URLs, and caching conflicts.

• Integration with convex-agent-plugins to maintain strict TypeScript validation, secure function definitions, and optimized data access patterns.

• Before making changes, the agent must run the provided upstream check script to ensure all configurations reflect current documentation.

• Users must clarify project-specific requirements, such as the preferred bundler and hosting path, before the skill executes any file modifications.

• All implementations require mandatory post-execution reporting, including the upstream doc commit timestamp, selected package installation path, a list of modified files, and the next steps for the user.

• The skill strictly enforces internal-only upload API policies and advises against exposing these endpoints to public HTTP traffic.

• Inputs include the target project type, path requirements, and deployment strategy; outputs include updated convex.config.ts, http.ts, staticHosting.ts files, and configured package.json scripts.