feature-delivery
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.
来源信息
- 仓库
- hoangsonww/PetSwipe-Match-App
- 最近来源活动
- 2026年2月28日 01:57
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 26
- 分支
- 12
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
4 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- 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
1. Inspect the affected area before proposing structure.
2. Decide whether the task is frontend-only, backend-only, infra-only, docs-only, or cross-cutting.
3. Keep the change coherent across code, navigation, API behavior, validation, and docs.
4. Validate with the smallest reliable command set for the touched area.
5. 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.
在 GitHub 查看