// 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.
| name | deployment-claims-audit |
| description | 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. |
Use this skill when a task involves strong readiness or deployability claims.
Read references/readiness-rubric.md.
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.
Docs-local workflow for keeping PetSwipe product pages, deployment docs, architecture docs, and operational claims aligned with the current repository. Use when working inside docs or when multiple docs need to be updated together.