Marketplace deploy
Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.
install
source · Clone the upstream repo
git clone https://github.com/aiskillstore/marketplace
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/chakshugautam/deploy" ~/.claude/skills/aiskillstore-marketplace-deploy-7303c1 && rm -rf "$T"
manifest:
skills/chakshugautam/deploy/SKILL.mdsource content
Deploy Skill
NEVER deploy without completing ALL steps below.
Required Workflow
Before ANY deployment (vercel, git push to main, etc.):
1. Build Locally
pnpm build
- Must complete with zero errors
- Check output for warnings
2. Start Local Dev Server
pnpm dev
- Server must start successfully
3. Test in Browser
- Open the local URL in Chrome DevTools MCP
- Test ALL changed functionality manually:
- Click buttons, verify they work
- Test keyboard input if applicable
- Submit forms, verify responses
- Check for console errors
4. Verify Tests Pass (if tests exist)
pnpm test
5. Only Then Deploy
After ALL above steps pass:
vercel --prod
Rules
- NO SHORTCUTS - Every step must be completed
- NO ASSUMPTIONS - "It worked before" is not verification
- TEST AFTER CHANGES - Any code change requires re-testing
- LOCAL FIRST - Never deploy to see if something works
Common Mistakes to Avoid
- Deploying immediately after build without browser testing
- Assuming dependency changes don't break anything
- Skipping keyboard/interaction testing
- Deploying to "check if it works on Vercel"
When User Says "Deploy"
- Ask: "Have you verified locally? Let me run through the checklist."
- Run build
- Start dev server
- Test in browser via Chrome DevTools MCP
- Only after confirming everything works, deploy