Use when the user says /deploydev, deploy dev, upload dev static hosting, or asks to deploy the current app to its development Convex static-hosting target.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this skill for a development @convex-dev/static-hosting upload in the current repo.
Source of truth:
https://github.com/get-convex/static-hostinghttps://www.convex.dev/components/static-hosting@convex-dev/static-hosting.package.json when present.staticHosting, but do not hard-code it if the repo defines another name.convex/convex.config.ts when needed by looking for app.use(staticHosting, { name: "..." }).staticHosting.npm run build separately before static upload. Static-hosting's --build flag injects the correct VITE_CONVEX_URL./deploydev WorkflowConfirm the user asked for dev.
Inspect available scripts:
npm run
Prefer the repo script when available:
npm run deploy:static:dev
If no script exists, discover the component name and run the static-hosting upload directly:
npx @convex-dev/static-hosting upload --build -c staticHosting --dev
Replace staticHosting with the configured component name if different.
Confirm deploy output includes:
Deploying to development environment
Your app is now available at: <dev convex site URL>
Report the dev URL exactly as printed and remind that it is not the public/canonical app.
If the upload cannot find static-hosting functions, run the app's dev Convex workflow first, usually:
npx convex dev --once
If the shell cannot reach Convex because of sandboxed network restrictions, rerun the same command with the required network approval.
Update docs only if deploy behavior changes:
README.mdchangelog.mdtask.mdfiles.mdIf the deploy behavior change is non-trivial, create a PRD in prds/.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
The English summary is being prepared. Showing the original description.
Agent Ready project design context for navigation, docs links, and interface tone. Use when building or reviewing UI in this repo so patterns match the documented product feel.
The English summary is being prepared. Showing the original description.
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
The English summary is being prepared. Showing the original description.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
The English summary is being prepared. Showing the original description.
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
The English summary is being prepared. Showing the original description.
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
The English summary is being prepared. Showing the original description.