Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

single-readme

Sterne0

Forks0

Aktualisiert19. März 2026 um 05:42

The Boilerplate monorepo has exactly one README.md (at repo root). Use when adding index/overview docs or creating new directories so you do not add a second README.

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

podverse

podverse/boilerplate

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	single-readme
description	The Boilerplate monorepo has exactly one README.md (at repo root). Use when adding index/overview docs or creating new directories so you do not add a second README.
version	1.0.0

Single README (Boilerplate)

The Boilerplate monorepo must have exactly one README.md, at the repository root (README.md).

Do

Keep the single project README at the repo root.
For directory docs use full-path names (e.g. INFRA-K8S.md, PACKAGES-UI.md) per the documentation-conventions skill.
The only INDEX.md in the repo is .cursor/skills/INDEX.md. Plan-set indexes under .llm/plans/ use 00-overview.md or 00-master-plan.md.

Don't

Do not create README.md in any subdirectory (apps, packages, infra, .llm/plans, .cursor/skills, etc.).
Do not add a second README or a second INDEX when introducing a new area; use the full-path doc name instead.

When to use this skill

Adding new documentation or index files.
Creating new directories that need an overview or index.
Planning or editing docs under .llm/, infra/, packages/, apps/, or .cursor/.

Mehr aus diesem Repository

gleiches Repository

api-testing

podverse/boilerplate

When changing API routes, auth, or env-dependent behavior, add or update the corresponding integration tests and keep the test file layout consistent.

2026-04-070

argocd-gitops-push

podverse/boilerplate

When adding or changing files under infra/k8s/ or sync targets for k8s, know what Argo CD syncs and remind the user to push to Git so the cluster can sync.

2026-04-070

generate-data-sync

podverse/boilerplate

Keeps tools/generate-data seeders and docs in sync when main or management DB schema or ORM entities change. Use when adding or changing tables/entities in packages/orm, packages/management-orm, or infra database migrations.

2026-04-070

roles-schema-sync

podverse/boilerplate

When changing DB schema or permission dimensions, consider predefined roles and bucket_role / role-related code.

2026-04-070

classification-env

podverse/boilerplate

Use when adding or changing environment variables, infra/env/classification YAML, scripts/env-classification, K8s env render, or local env generation.

2026-03-300

boilerplate-api-patterns

podverse/boilerplate

Common patterns for the Boilerplate HTTP API (Express)

2026-03-260

name	single-readme
description	The Boilerplate monorepo has exactly one README.md (at repo root). Use when adding index/overview docs or creating new directories so you do not add a second README.
version	1.0.0

Single README (Boilerplate)

The Boilerplate monorepo must have exactly one README.md, at the repository root (README.md).

Do

Keep the single project README at the repo root.
For directory docs use full-path names (e.g. INFRA-K8S.md, PACKAGES-UI.md) per the documentation-conventions skill.
The only INDEX.md in the repo is .cursor/skills/INDEX.md. Plan-set indexes under .llm/plans/ use 00-overview.md or 00-master-plan.md.

Don't

Do not create README.md in any subdirectory (apps, packages, infra, .llm/plans, .cursor/skills, etc.).
Do not add a second README or a second INDEX when introducing a new area; use the full-path doc name instead.

When to use this skill

Adding new documentation or index files.
Creating new directories that need an overview or index.
Planning or editing docs under .llm/, infra/, packages/, apps/, or .cursor/.