Run any Skill in Manus with one click

feature-delivery

Stars22

Forks12

UpdatedFebruary 28, 2026 at 01:57

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hoangsonww

hoangsonww/PetSwipe-Match-App

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

4 files

SKILL.md

readonly

name	feature-delivery
description	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.

Use this skill when implementing or expanding a feature in PetSwipe.

Workflow

Inspect the affected area before proposing structure.
Decide whether the task is frontend-only, backend-only, infra-only, docs-only, or cross-cutting.
Keep the change coherent across code, navigation, API behavior, validation, and docs.
Validate with the smallest reliable command set for the touched area.
Update docs when the task changes user-visible behavior, APIs, or deployment posture.

Delegation

If the task is broad, spawn the matching specialist agent:

frontend_ux
backend_api
infra_auditor
docs_curator
reviewer

PetSwipe Rules

Frontend work should preserve the Next.js Pages Router structure.
Backend work should keep routes, controllers, services, entities, and docs aligned.
Infra work should be validated with render and preflight commands, not claimed complete on inspection alone.
Doc updates should be made in the same task when behavior changes.

Read references/repo-map.md for structure and references/validation.md for command guidance.

More from this repository

same repository

deployment-claims-audit

hoangsonww/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.

2026-02-2822

map-geocoding-debug

hoangsonww/PetSwipe-Match-App

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.

2026-02-2822

navigation-and-page-structure

hoangsonww/PetSwipe-Match-App

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.

2026-02-2822

planner-and-insights-pages

hoangsonww/PetSwipe-Match-App

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.

2026-02-2822

testing-and-validation

hoangsonww/PetSwipe-Match-App

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.

2026-02-2822

swagger-health-contracts

hoangsonww/PetSwipe-Match-App

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.

2026-02-2822

name	feature-delivery
description	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.

Use this skill when implementing or expanding a feature in PetSwipe.

Workflow

Inspect the affected area before proposing structure.
Decide whether the task is frontend-only, backend-only, infra-only, docs-only, or cross-cutting.
Keep the change coherent across code, navigation, API behavior, validation, and docs.
Validate with the smallest reliable command set for the touched area.
Update docs when the task changes user-visible behavior, APIs, or deployment posture.

Delegation

If the task is broad, spawn the matching specialist agent:

frontend_ux
backend_api
infra_auditor
docs_curator
reviewer

PetSwipe Rules

Frontend work should preserve the Next.js Pages Router structure.
Backend work should keep routes, controllers, services, entities, and docs aligned.
Infra work should be validated with render and preflight commands, not claimed complete on inspection alone.
Doc updates should be made in the same task when behavior changes.

Read references/repo-map.md for structure and references/validation.md for command guidance.