ワンクリックでManusで任意のスキルを実行

full-feature

スター42

フォーク13

更新日2026年4月14日 12:04

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 ページを確認してインストールできます。

Manusで実行

ソース

Open-Earth-Foundation

Open-Earth-Foundation/CityCatalyst

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Full Feature Development

Overview

A complete feature in CityCatalyst touches up to 7 layers. Follow this order to avoid dependency issues.

Workflow

Phase 1: Database Layer

Migration: Create migration file in app/migrations/ (see create-migration skill)
Model: Create Sequelize model in app/src/models/
Register: Add to app/src/models/init-models.ts
Run: cd app && npm run db:migrate

Phase 2: Backend API

Validation: Add Zod schemas to app/src/util/validation.ts
Service (optional): Create app/src/backend/<Feature>Service.ts for complex logic
Route handler: Create app/src/app/api/v1/<feature>/route.ts with apiHandler
Swagger: Add @swagger JSDoc above imports
Test: Create app/tests/api/<feature>.jest.ts

Phase 3: Frontend Data Layer

RTK Query: Add endpoints to app/src/services/api.ts
- Query with providesTags
- Mutation with invalidatesTags
- Add new tag type to tagTypes if needed

Phase 4: Frontend UI

i18n: Add keys to app/src/i18n/locales/en/<namespace>.json
Component(s): Create in app/src/components/<Feature>/
Page (if new route): Create app/src/app/[lng]/<route>/page.tsx
Hook (if complex logic): Create app/src/hooks/use<Feature>.ts
Navigation: Update sidebar/nav if adding a new page

Phase 5: Quality

Types: Ensure all types are in app/src/util/types.ts or co-located
Lint: cd app && npm run lint
Format: cd app && npm run prettier
Test: cd app && npm run jest

File Mapping

Feature: "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

Quick Reference

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

このリポジトリの他の Skills

同じリポジトリ

non-tech-contribute

Open-Earth-Foundation/CityCatalyst

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.

2026-07-0142

pull-request-standards

Open-Earth-Foundation/CityCatalyst

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.

2026-07-0142

pr-review-gate

Open-Earth-Foundation/CityCatalyst

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.

2026-06-0542

k8s-health-audit

Open-Earth-Foundation/CityCatalyst

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.

2026-06-0442

k8s-readonly-query

Open-Earth-Foundation/CityCatalyst

Answer a single Kubernetes question using readonly investigation and evidence-first output.

2026-06-0442

create-ticket

Open-Earth-Foundation/CityCatalyst

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.

2026-05-2042

Full Feature Development

Overview

A complete feature in CityCatalyst touches up to 7 layers. Follow this order to avoid dependency issues.

Workflow

Phase 1: Database Layer

Migration: Create migration file in app/migrations/ (see create-migration skill)

Model: Create Sequelize model in app/src/models/

Register: Add to app/src/models/init-models.ts

Run: cd app && npm run db:migrate

Phase 2: Backend API

Validation: Add Zod schemas to app/src/util/validation.ts

Service (optional): Create app/src/backend/<Feature>Service.ts for complex logic

Route handler: Create app/src/app/api/v1/<feature>/route.ts with apiHandler

Swagger: Add @swagger JSDoc above imports

Test: Create app/tests/api/<feature>.jest.ts

Phase 3: Frontend Data Layer

RTK Query: Add endpoints to app/src/services/api.ts

Query with providesTags
Mutation with invalidatesTags
Add new tag type to tagTypes if needed

Phase 4: Frontend UI

i18n: Add keys to app/src/i18n/locales/en/<namespace>.json

Component(s): Create in app/src/components/<Feature>/

Page (if new route): Create app/src/app/[lng]/<route>/page.tsx

Hook (if complex logic): Create app/src/hooks/use<Feature>.ts

Navigation: Update sidebar/nav if adding a new page

Phase 5: Quality

Types: Ensure all types are in app/src/util/types.ts or co-located

Lint: cd app && npm run lint

Format: cd app && npm run prettier

Test: cd app && npm run jest

File Mapping

Feature: "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

Quick Reference

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

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.