Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

new-service

Étoiles20

Forks3

Mis à jour4 juin 2026 à 15:58

Scaffold a new API service with request functions, Zod schemas, URL constants, and optional MSW mock handlers. Use this skill whenever the user asks to "add a service", "create the projects API", "scaffold a new GAIA service", "wire up CRUD for users", or anything implying a new folder under `app/services/gaia/{name}/` with parsers/types/requests + matching `test/mocks/{name}/` collections.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

gaia-react

gaia-react/gaia

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	new-service
description	Scaffold a new API service with request functions, Zod schemas, URL constants, and optional MSW mock handlers. Use this skill whenever the user asks to "add a service", "create the projects API", "scaffold a new GAIA service", "wire up CRUD for users", or anything implying a new folder under `app/services/gaia/{name}/` with parsers/types/requests + matching `test/mocks/{name}/` collections.
model	haiku

new-service

Trigger: user asks to scaffold an API service.

Workflow

Confirm: name (kebab), endpoints, schema (name:type pairs), with mocks?
Run: .gaia/cli/gaia scaffold service <name> --endpoints "..." --schema "..." [--mocks]
Verify: pnpm typecheck clean; if --mocks, run a single MSW round-trip in a vitest test.
Wire the service into the consuming page/hook (CLI does not do this, manual).

Flags

--endpoints "get,post,put,delete", required (subset of get/post/put/delete)
--schema "id:string,name:string,status:enum(active,archived)", required
--mocks, also emit MSW mock collection
--json, emit ScaffoldResult JSON

Schema types: string, number, boolean, datetime, enum(a,b,...). Append ? for optional.

See

wiki/concepts/API Service Pattern.md, pattern source of truth
.claude/rules/api-service.md, quick pointer

Plus depuis ce dépôt

même dépôt

update-gaia

gaia-react/gaia

Pull the latest GAIA release into this project without clobbering customizations. Three-way merge per file using .gaia/manifest.json classes. Trigger when the user clicks the statusline `Run /update-gaia` indicator or asks "update GAIA", "pull the latest GAIA", "apply the new GAIA release".

2026-07-2220

update-deps

gaia-react/gaia

Autonomous Dependabot, auto-discover outdated packages, audit overrides, apply migrations for major bumps, resolve conflicts, run quality gate. Trigger when the user clicks the statusline `Run /update-deps` indicator or asks "update dependencies", "bump deps", "run dependabot".

2026-07-2120

file-tech-debt

gaia-react/gaia

File a new tech-debt GitHub issue for an out-of-scope code-review finding, building the dedup key, checking for an existing open or declined-closed match, and only if none exists, creating the issue with the right labels and touching the debt-count staleness sentinel. Trigger on natural-language asks like "file a tech-debt issue", "record this as tech-debt", "open a tech-debt issue for this out-of-scope finding", or "file this finding as debt". Do NOT trigger on draining, fixing, listing, or prioritizing existing debt (that's `/gaia-debt`), nor on general "clean up the code" or "fix this bug" asks that aren't about filing a new tracked issue.

2026-07-2120

playwright-cli

gaia-react/gaia

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

2026-07-1920

react-code

gaia-react/gaia

Patterns and conventions for writing and editing React code, including components and hooks. Use this skill whenever writing or reviewing React components, hooks (useEffect, useCallback, useState), event handlers, or component extraction decisions. Also trigger when debugging stale closures, infinite re-renders, or unnecessary re-renders caused by memoization issues, or when deciding whether to add a dependency, reach for a web-platform API (Intl, URL, crypto.randomUUID), or hand-roll a primitive. Also trigger when choosing a React 19 idiom, deciding between forwardRef and ref-as-prop, useContext and use(), or Context.Provider and the Context shorthand; when conditional rendering risks the && numeric-0 leak; or when tempted to reach for React's form Actions (useActionState, useFormStatus, useOptimistic) instead of React Router's form handling.

2026-07-1920

release-notes

gaia-react/gaia

Maintainer-only. Translate a version's GAIA CHANGELOG entries into plain-language public release notes for the marketing site (gaiareact.com). Writes a release-data `.ts` file under `../website/src/pages/changelog/releases/` plus an editorial-decisions report for human review. Use whenever the maintainer wants the adopter-facing notes for a version, e.g. "write release notes", "generate the changelog page entry", "translate the CHANGELOG for the website", "what's new on the site for v1.5.0", "public notes for 1.4.0", or right after cutting a release, and for one-time backfill of historical `## [x.y.z]` blocks. This is the website-notes step only. It does NOT edit `CHANGELOG.md`, it is not how you cut a release (version bump, manifest, and tag are `/gaia-release`), and it is not for an adopter's own app's release notes.

2026-07-1920

name	new-service
description	Scaffold a new API service with request functions, Zod schemas, URL constants, and optional MSW mock handlers. Use this skill whenever the user asks to "add a service", "create the projects API", "scaffold a new GAIA service", "wire up CRUD for users", or anything implying a new folder under `app/services/gaia/{name}/` with parsers/types/requests + matching `test/mocks/{name}/` collections.
model	haiku

new-service

Trigger: user asks to scaffold an API service.

Workflow

Confirm: name (kebab), endpoints, schema (name:type pairs), with mocks?
Run: .gaia/cli/gaia scaffold service <name> --endpoints "..." --schema "..." [--mocks]
Verify: pnpm typecheck clean; if --mocks, run a single MSW round-trip in a vitest test.
Wire the service into the consuming page/hook (CLI does not do this, manual).

Flags

--endpoints "get,post,put,delete", required (subset of get/post/put/delete)
--schema "id:string,name:string,status:enum(active,archived)", required
--mocks, also emit MSW mock collection
--json, emit ScaffoldResult JSON

Schema types: string, number, boolean, datetime, enum(a,b,...). Append ? for optional.

See

wiki/concepts/API Service Pattern.md, pattern source of truth
.claude/rules/api-service.md, quick pointer