Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

maintain-project-docs

Sterne0

Forks0

Aktualisiert19. Mai 2026 um 14:54

Use when code or infrastructure changes require synchronized updates to docs under apps/web/content and related architecture references.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

takeshi-su57

takeshi-su57/luckyplans

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	maintain-project-docs
description	Use when code or infrastructure changes require synchronized updates to docs under apps/web/content and related architecture references.

Maintain Project Docs

When To Use

Architecture, infra, auth, API, or env var behavior changed.
Developer/deployment workflow changed.
New service or major capability added.

Required Docs Targets

apps/web/content/architecture/overview.mdx
apps/web/content/architecture/decisions/*.mdx (ADR when significant)
apps/web/content/guides/developer.mdx
apps/web/content/guides/deployment.mdx
apps/web/content/system/api.mdx
apps/web/content/system/configuration.mdx

Checklist

Identify what changed (architecture, API, config, workflow).
Update the matching docs in the same PR.
If architectural decision is significant, add ADR + decisions/_meta.ts.
Keep docs factual (current state, not roadmap).
Run: pnpm lint, pnpm type-check, pnpm build, pnpm format:check.

Mehr aus diesem Repository

gleiches Repository

add-testing-foundation

takeshi-su57/luckyplans

Use when introducing or expanding tests in LuckyPlans, especially service logic, shared utilities, controllers, and resolvers.

2026-05-190

add-frontend-page

takeshi-su57/luckyplans

Use when adding a new Next.js App Router page in apps/web, including route structure, data hooks usage, and auth/session-aware behavior.

2026-05-190

apply-ui-baseline

takeshi-su57/luckyplans

Use when implementing or modifying frontend UI in apps/web to enforce the repository's HeroUI + Notion-style baseline consistently.

2026-05-190

create-graphql-hook

takeshi-su57/luckyplans

Use when adding a new GraphQL query or mutation in apps/web so the operation is defined inline in a hook and consumed by components.

2026-05-190

customize-frontend-component

takeshi-su57/luckyplans

Use when modifying or extending an existing frontend component in apps/web while preserving project styling conventions, hook boundaries, and accessibility.

2026-05-190

enforce-apollo-state-boundary

takeshi-su57/luckyplans

Use when introducing or modifying frontend state management to keep GraphQL data in Apollo cache and avoid mixed-state ownership.

2026-05-190

name	maintain-project-docs
description	Use when code or infrastructure changes require synchronized updates to docs under apps/web/content and related architecture references.

Maintain Project Docs

When To Use

Architecture, infra, auth, API, or env var behavior changed.
Developer/deployment workflow changed.
New service or major capability added.

Required Docs Targets

apps/web/content/architecture/overview.mdx
apps/web/content/architecture/decisions/*.mdx (ADR when significant)
apps/web/content/guides/developer.mdx
apps/web/content/guides/deployment.mdx
apps/web/content/system/api.mdx
apps/web/content/system/configuration.mdx

Checklist

Identify what changed (architecture, API, config, workflow).
Update the matching docs in the same PR.
If architectural decision is significant, add ADR + decisions/_meta.ts.
Keep docs factual (current state, not roadmap).
Run: pnpm lint, pnpm type-check, pnpm build, pnpm format:check.