Our review
Repairs runtime failures in a sandboxed application by reading exact errors, checking env-dependent code, applying safe patterns that preserve fallback behavior, and verifying with build and secret scans.
Strengths
- Focuses on root cause instead of masking errors.
- Provides specific files and configs to inspect.
- Emphasizes safe fallback patterns and no secret exposure.
- Includes verification steps such as rebuild and secret scanning.
Limitations
- Specific to the described Vibiz codebase structure and stack.
- Assumes a Next.js, E2B sandbox, and deployment conventions.
- Does not cover every possible runtime error.
Use when the sandbox app fails to build, boot, render, authenticate, call AI routes, read offers, or deploy cleanly.
Do not use for feature development or when you need to add new capabilities.
Security analysis
SafeThe skill provides safe repair guidelines for a sandbox app, emphasizing preservation of security guards, avoidance of secret exposure, and using standard debugging tools. There are no instructions for destructive or exfiltrating actions.
No concerns found
Examples
The app boots but the landing page shows a 500 and I see a Turso env var missing error in the console. Apply the runtime repair skill to fix it safely.The build fails because SAPIOM_API_KEY is absent during `npm run build`. Make it tolerate missing env keys without exposing secrets.After deploying, auth routes fail. Follow the runtime repair skill to inspect auth.ts, middleware, and api-guard, and apply the safe pattern to preserve landing-page-only mode.name: vibiz-runtime-repair description: Use when the sandbox app fails to build, boot, render, authenticate, call AI routes, read offers, or deploy cleanly. compatibility: opencode
Vibiz Runtime Repair
Repair the real failure. Do not bypass platform contracts to make an error disappear.
Start here:
- Read the exact error, terminal output, browser console, or failing route response.
- Inspect the file named in the stack trace before changing adjacent code.
- Check env-dependent code in
src/lib/auth.ts,src/middleware.ts,src/lib/sapiom.ts,src/lib/api-guard.ts, andscripts/migrate.mjs. - Check sandbox boot behavior in
e2b.tomland template build behavior inDockerfile.
Safe repair patterns:
- If auth is unavailable because Turso env vars are missing, preserve landing-page-only mode and existing guards.
- If AI routes fail because
SAPIOM_API_KEYis missing, keep server-only behavior and return a clear unavailable state. - If a user-supplied third-party integration truly requires a runtime key, put it in
.envserver-side and keep it out of browser-exposedNEXT_PUBLIC_*vars unless the key is designed to be public. - If offers are missing, preserve
getSeededOffers()fallback behavior and do not fabricate seeded offers. - If Tailwind fails, fix class/config/CSS compatibility instead of removing whole sections.
- If Next build fails from runtime-only env assumptions, make the code tolerate absent envs during build without exposing secrets or disabling production behavior.
Verification:
- Run the failing command again after each targeted fix.
- Run
npm run buildbefore considering runtime repairs complete. - Search for accidental secret exposure with
rg -n "SECRET|TOKEN|API_KEY|STRIPE".
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.