菜单
Workflow for safe PetSwipe backend/API changes across Express routes, controllers, services, entities, migrations, and API docs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
PetSwipe workflow for checking whether deployment, production-readiness, or enterprise-grade claims are actually supported by repo evidence. Use when editing deployment docs, infra summaries, or any task that makes strong statements about readiness.
PetSwipe map and geocoding workflow for diagnosing map page issues, geocode request volume, cache behavior, API proxy behavior, CORS issues, and location-related UI regressions. Use when the task mentions the map page, geocoding, location results, or geocode performance.
PetSwipe navigation workflow for navbar changes, icon-only links, mobile menu behavior, route placement, and page discoverability. Use when work changes the navbar, mobile navigation, page ordering, or the relationship between key user-facing pages.
PetSwipe workflow for adoption-planner and insights page work, including comparison cards, gauges, charts, metrics, and recommendation panels. Use when changes focus on adoption-planner.tsx, insights.tsx, or the relationship between liked pets, readiness, and swipe analytics.
PetSwipe validation workflow for choosing the smallest reliable checks for frontend, backend, infra, docs, and mixed changes. Use when a task needs a concrete validation plan or when the repo's pre-existing lint or type issues make broad validation noisy.
Backend-local workflow for health endpoints, readiness behavior, Swagger/OpenAPI exposure, and runtime contract changes in PetSwipe. Use when backend work touches backend/src/app.ts, startup behavior, docs endpoints, or deployment-sensitive runtime behavior.
| name | backend-api-change |
| description | Workflow for safe PetSwipe backend/API changes across Express routes, controllers, services, entities, migrations, and API docs. |
Use this skill for backend endpoint changes, auth changes, entity updates, migrations, and service-layer work.
backend/src/app.ts is the central runtime and docs surface./health and /ready matter for deployment./api-docs.json and /docs.If the task is deep or risky, use the backend-api-specialist subagent first.
@references/api-checklist.md