菜单
End-to-end feature development workflow for CityCatalyst covering database, API, frontend, and tests. Use when the user asks to build a complete feature, implement a full user story, or create an end-to-end functionality.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guide non-technical contributors through making safe code changes to CityCatalyst. Use when someone without coding experience wants to update text, translations, colors, copy, or small UI details, and needs the agent to handle git, verification, and PR creation for them.
Create or update pull requests with repository-derived context and concise title/body standards. Use when creating, updating, automating, drafting, or polishing PRs, or preparing GitHub PR tool payloads.
Review pull requests for high-impact issues only. Use when the user asks to review a PR, especially requests like "do a review of PR <id>", "review PR <id>", or "PR review". Evaluate security, AGENTS.md alignment, repository structure, reuse over reimplementation, complexity, and regression risk. Return only actionable comments worth changing.
Run a read-only Kubernetes health audit against an explicit readonly cluster context such as `dev-cluster-readonly` or `prod-cluster-readonly`. Use when the user wants an automated cluster/pod health check, diagnosis of failing workloads, or a report of likely causes without making any write changes.
Answer a single Kubernetes question using readonly investigation and evidence-first output.
Generate structured Linear tickets (stories, tasks, bugs, spikes) with AI-enriched code references and acceptance criteria from a brief description. Use when the product team asks to create a ticket, write a story, draft a task, report a bug, or plan a spike for CityCatalyst.
| name | full-feature |
| description | End-to-end feature development workflow for CityCatalyst covering database, API, frontend, and tests. Use when the user asks to build a complete feature, implement a full user story, or create an end-to-end functionality. |
A complete feature in CityCatalyst touches up to 7 layers. Follow this order to avoid dependency issues.
app/migrations/ (see create-migration skill)app/src/models/app/src/models/init-models.tscd app && npm run db:migrateapp/src/util/validation.tsapp/src/backend/<Feature>Service.ts for complex logicapp/src/app/api/v1/<feature>/route.ts with apiHandler@swagger JSDoc above importsapp/tests/api/<feature>.jest.tsapp/src/services/api.ts
providesTagsinvalidatesTagstagTypes if neededapp/src/i18n/locales/en/<namespace>.jsonapp/src/components/<Feature>/app/src/app/[lng]/<route>/page.tsxapp/src/hooks/use<Feature>.tsapp/src/util/types.ts or co-locatedcd app && npm run lintcd app && npm run prettiercd app && npm run jestFeature: "Widget Management"
app/
├── migrations/20260410-add-widget.cjs # DB migration
├── src/models/Widget.ts # Sequelize model
├── src/models/init-models.ts # Register model
├── src/util/validation.ts # + createWidgetRequest schema
├── src/backend/WidgetService.ts # Business logic
├── src/app/api/v1/widget/route.ts # API handler (GET, POST)
├── src/app/api/v1/widget/[widget]/route.ts # API handler (GET, PATCH, DELETE)
├── src/services/api.ts # + RTK Query endpoints
├── src/i18n/locales/en/widget.json # i18n keys
├── src/components/Widget/widget-list.tsx # List component
├── src/components/Widget/widget-form.tsx # Form component
├── src/app/[lng]/cities/[cityId]/widget/page.tsx # Page
├── src/hooks/useWidget.ts # Custom hook (optional)
└── tests/api/widget.jest.ts # API tests
| Need | Location | Pattern |
|---|---|---|
| Auth check | if (!session) throw createHttpError.Unauthorized() | All protected routes |
| DB query | db.models.Widget.findAll(...) | Sequelize |
| Validate | schema.parse(body) | Zod (auto-caught as 400) |
| API error | throw createHttpError.NotFound(...) | http-errors |
| Data fetch | api.useGetWidgetQuery(id) | RTK Query hook |
| Translation | t("widget.title") | i18next |
| Styling | bg="background.overlay" | Chakra semantic tokens |