Loading...
Loading...
Found 11 Skills
Produces Go/No-Go deployment checklists with SQL verification queries, rollback procedures, and monitoring plans. Use when PRs touch production data, migrations, or risky data changes.
Get a barebones Convex + web template running from a one-sentence idea.
This skill should be used when the user asks to "deploy to power pages", "upload site", "publish site", "deploy site", "push to power pages", "upload code site", or wants to deploy/upload an existing Power Pages code site to a Power Pages environment using PAC CLI.
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
Creates comprehensive deployment checklists with pre-deployment checks, smoke tests, verification steps, and sign-off workflows. Use for "deployment checklist", "release verification", "deployment runbook", or "production readiness".
Design or verify automated build, test, quality-gate, release, deployment, and post-deployment checks, including failure evidence and stop or rollback conditions. Do not use it for branch, commit, or tag history, or infer product correctness from a green pipeline alone.
사용자가 명시적으로 요청한 서비스 배포를 현재 프로젝트의 배포 환경에 맞춰 실행하고 공개 URL과 기본 동작을 확인한다. “배포해줘”, “인터넷에 공개해줘”, “URL을 만들어줘”, “Vercel에 올려줘”, “첫 배포를 해보자”라는 요청에 사용한다. 기능 추가나 디자인 수정에는 사용하지 않는다.
Find every copy of a plugin or skill on this machine and prove which ones are stale. Use when the user asks to update every place / everywhere on this PC, check the plugin cache, confirm an edit actually went live, verify a skill is deployed, find drifted or vendored copies, or asks why a skill still behaves like the old version. Also use before shipping a plugin change that other repos vendor. It reports and never writes.
Remote cloud workflow with explicit fqdn selection and deployment verification.
Drive the running app in a real browser to prove a flow works — on demand, or as a saved test for the few flows worth re-running. Use when a multi-step flow needs checking end to end, right after deploying (against the live URL, not localhost), when the builder asks for Playwright, e2e or browser tests, and when something works locally but is reported broken in production. Also use before demo day to confirm the core action still works and to capture screenshots.
Oversee the other Claude threads (sessions) working on the same project. Check what each is doing, confirm finished work is merged to main, has its changelog entry with screenshots, and is live, archive threads that are truly done, and restart or flag threads that were cut off. Use when the user says "check threads", "check new changes", "are the threads merged and pushed", "archive the done threads", or asks what the other sessions are up to. Project specifics (changelog format, live site, capture folders) go in an optional local references/<project>.md next to this skill.