القائمة
Use when the user wants to deploy, ship, or push the Jyotish Helper app live to production (Vercel) — merges/pushes to main and runs the Vercel prod deploy.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when building, styling, or reviewing any Jyotish Helper UI — components, colors, fonts, the North Indian chart, the time slider, glass panels — to keep the look consistent with the approved "Saffron Gold" direction.
Use after merging a branch to main or cutting a release, to bring README.md and docs/architecture.md in sync with what actually shipped.
Use when the user wants to run, start, preview, or view the Jyotish Helper app locally in a browser — starts the Vite dev server and opens it.
| name | deploy |
| description | Use when the user wants to deploy, ship, or push the Jyotish Helper app live to production (Vercel) — merges/pushes to main and runs the Vercel prod deploy. |
Static site, Vercel project web (root dir web/), live at
https://web-pi-kohl-36.vercel.app. Deploy always builds from main — never
deploy an unmerged branch straight to prod.
git status, git log --oneline -3 on
main. If work is still on a feature branch, merge it first
(fast-forward preferred, see AGENTS.md branch-deletion convention).cd web && npx vitest run — must be green.main if not already: git push origin main.cd web && vercel --prod --yes.
web/.vercel/ (project link) is gitignored. On a fresh clone, run
vercel link once before this will work.Production / aliased URL matches
https://web-pi-kohl-36.vercel.app.If this deploy corresponds to a notable release, tag and publish a GitHub Release too (see AGENTS.md "Versioning") — don't do this for every trivial deploy, only when the user wants a version bump:
gh release create vX.Y.Z --title "vX.Y.Z" --notes "..." --latest
git status first.