菜单
Keep the frontend API types in sync with the backend after any endpoint change — regenerate menu-api.ts from the OpenAPI spec produced by the .NET build.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Fetch all issues for a GitHub repo, parse Epic task lists, and compute a blocked/unblocked/in-progress/done status for every issue and epic transitively.
Generate a self-contained HTML file containing one or more interactive Mermaid diagrams with dark GitHub-style theming, status-based colour coding, and mouse/button pan-and-zoom via svg-pan-zoom.
Step-by-step guide for adding a new Minimal API endpoint to MenuApi following the layered model pattern (EF Entity → DBModel → ViewModel, Mapperly, repository, service, MapGroup registration).
How to create a new Vogen value object in MenuApi — covering the attribute, assembly-wide defaults, EF Core value converter registration, Swagger mapping, and repository wrapping conventions.
Structured checklist for reviewing pull requests in the Menu repository — layer separation, Vogen coverage, Mapperly attributes, async conventions, and StyleCop compliance.
Canonical commands and safety rules for EF Core migration management in the Menu repository — adding, removing, and applying migrations correctly.
| name | openapi-sync |
| description | Keep the frontend API types in sync with the backend after any endpoint change — regenerate menu-api.ts from the OpenAPI spec produced by the .NET build. |
| user-invokable | true |
| context | inline |
Use this skill after any change to a MenuApi endpoint (new endpoint, changed request/response shape, renamed route). The frontend uses generated TypeScript types from the backend's OpenAPI spec; stale types cause type errors and runtime mismatches.
open-api/menu-api.json at the repository root.pnpm generate-openapi (from ui/menu-website/) reads that file and outputs src/generated/open-api/menu-api.ts.src/services/recipe-api.ts consumes the generated types via openapi-fetch.Never hand-write types in src/generated/ — the entire src/generated/ folder is overwritten on each run.
cd backend
dotnet restore MenuApi.sln
dotnet build MenuApi.sln --configuration Release --no-restore
This writes open-api/menu-api.json.
cd ui/menu-website
pnpm generate-openapi
This reads ../../open-api/menu-api.json and outputs src/generated/open-api/menu-api.ts.
Commit src/generated/open-api/menu-api.ts in the same commit as the backend change that caused the update.
open-api/menu-api.json is generated by the .NET build and is gitignored (open-api/.gitignore ignores *.json) — do not attempt to commit it. It is consumed as a build artifact at generation time and uploaded to CI artefacts for the frontend job.
After regeneration, confirm the frontend still compiles and passes lint:
cd ui/menu-website
pnpm run lint
pnpm run build
pnpm generate-openapi before building the backend — the spec file will be stale or missing.src/generated/open-api/menu-api.ts by hand — changes will be silently overwritten on the next generation run.open-api/menu-api.json — it is gitignored and is consumed as a build-time artefact, not a tracked file.