PetSwipe-Match-App

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.

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.

Frontend-local workflow for PetSwipe chart overflow, tooltip, dark mode text, clipping, and responsive layout issues inside frontend pages and shared chart components. Use when working in frontend and the issue is specifically about charts or mobile layout behavior.

Frontend-local workflow for navbar behavior, route ordering, icon-only links, mobile menu UX, and page discoverability in PetSwipe. Use when working in frontend and the task touches Navbar, route links, or mobile navigation.

Kubernetes-local workflow for manifest hardening, renderability, overlays, quotas, network policies, and rollout safety in PetSwipe. Use when working inside k8s and the task is specifically about manifest correctness or production posture.

Terraform-local workflow for backend.hcl, tfvars examples, operator bootstrap, and plan/apply readiness in PetSwipe. Use when working inside terraform and the task is about making the Terraform workflow clearer, safer, or more deployable.

Safe PetSwipe backend workflow for Express route changes, TypeORM entity updates, service changes, migrations, auth adjustments, and API docs updates. Use when work changes backend behavior or data flow and needs route/controller/service/entity coherence.

PetSwipe documentation sync workflow for README, ARCHITECTURE, deployment docs, Kubernetes docs, and Terraform docs. Use when code or infra changes require documentation updates or when docs appear stale relative to the repository.

End-to-end PetSwipe delivery workflow for implementing or extending features across frontend, backend, docs, and validation. Use when a task spans user-visible behavior, API behavior, navigation, or multiple parts of the repository and needs a coherent change rather than a single isolated edit.

PetSwipe frontend workflow for page redesigns, responsive fixes, chart issues, navbar changes, and UI polish in the Next.js frontend. Use when the task is primarily visual, layout-focused, or interaction-focused inside frontend pages and shared UI components.

PetSwipe infrastructure and deployment workflow for Kubernetes, Terraform, production Docker Compose, release bundle, and preflight validation. Use when the task is explicitly about deployability, production readiness, operator workflow, or infra/devops changes.

Bug-focused PetSwipe review workflow emphasizing regressions, deployment risk, missing validation, stale docs, and user-visible breakage. Use when the user asks for a review or when a risky change needs structured scrutiny.

Workflow for safe PetSwipe backend/API changes across Express routes, controllers, services, entities, migrations, and API docs.

Workflow for keeping PetSwipe documentation aligned with the current codebase, deployment stack, and product surfaces.

End-to-end workflow for shipping PetSwipe features cleanly across frontend, backend, docs, and validation.

Workflow for high-quality PetSwipe frontend work across pages, layout, navigation, charts, responsive behavior, and visual refinement.

Operator-grade workflow for PetSwipe deployment, Kubernetes, Terraform, release bundle, and production-readiness checks.

Bug-focused PetSwipe review workflow emphasizing regressions, deployment risk, missing validation, and stale docs.