feature-delivery
SkillProductivityEnd-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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the feature-delivery skill
What this skill tells your AI
The instructions your AI receives, as published by hoangsonww/petswipe-match-app in .agents/skills/feature-delivery/SKILL.md and read by ahel’s review.
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_uxbackend_apiinfra_auditordocs_curatorreviewer
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.
Signals
- GitHub stars
- 26
- Forks
- 12
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
feature-delivery- Source
- github.com/hoangsonww/petswipe-match-app