🐻 A Tinder-inspired pet adoption app where you swipe to navigate, “adopt”, or “pass” on shelter animals. Built & deployed with PostgreSQL, Express, Node.js, TypeORM, Next.js, AWS, Agentic AI, MCP, Datadog, and many other modern technologies for a fun, real-time experience 🐱🐶
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.
★not rated 24 yesterdayA52 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: