원클릭으로 Manus에서 모든 스킬 실행

ap-docs-guide-getting-started

스타28

포크0

업데이트2026년 6월 4일 21:32

How to write the Getting Started pages for the Atomic Payload docs — docs/content/docs/getting-started/*.mdx (quick-start, existing-project, environment, project-structure). Use when creating, editing, or reviewing a getting-started page. These are procedural, do-this-then-that guides that land the reader on a working project. Builds on the ap-docs-guide skill for shared conventions.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

pro-laico

pro-laico/atomic-payload

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Getting Started pages

Procedural setup guides under docs/content/docs/getting-started/. Goal: take the reader from nothing to a working project, step by step. Follow ap-docs-guide for shared conventions.

Structure

Intro — one sentence on the outcome ("Scaffold a new project and land on a running dev server.").
## Prerequisites — a short bullet list (Node version, pnpm, a database URL), where relevant.
The walkthrough — a <Steps> block; each <Step> has a ### heading, a short explanation, and a labeled command/code fence. Use <Tabs groupId="package-manager"> for npm/pnpm/yarn variants.
## Next — a one-line pointer (or <Cards>) to the next guide.

Notes

Imperative, second person ("Run…", "Copy…"). One action per step.
Commands and scripts must match the real template and CLI scaffolds — copy them, don't invent (verify against templates/atomic-payload and packages/create-atomic-payload).
Keep conceptual "why" short; link to a concept page for depth.

Checklist

Follows ap-docs-guide shared conventions.
Prerequisites (if any) → <Steps> walkthrough → Next.
Every command verified against the real scaffold/template.
Package-manager variants use <Tabs groupId="package-manager">.

이 저장소의 다른 Skills

같은 저장소

ap-docs-guide-plugin

pro-laico/atomic-payload

How to write the per-plugin documentation pages for the atomic-payload (@pro-laico/*) project — the docs/content/docs/plugins/*.mdx pages on the Fumadocs site. Use whenever creating, rewriting, or reviewing a plugin doc page. Covers the plain-language, benefit-first tone for a surface-level Payload/Next/React reader; the full page structure (intro → installation → setup walkthrough → using it in your app → options → environment variables → exports → related); the Fumadocs components to use; and the rule to ground every setup/frontend step in the real package source and the templates/atomic-payload template rather than inventing it. Trigger when documenting or editing any @pro-laico plugin's docs page, even when the user just says "document this plugin", "the plugin docs are incomplete", or "fix the setup section".

2026-06-0528

ap-docs-guide

pro-laico/atomic-payload

The shared, docs-wide guide for the Atomic Payload (@pro-laico/*) documentation site — the Fumadocs project under docs/. Use whenever creating, editing, or reviewing ANY docs/content/docs/**/*.mdx page. Covers the conventions every doc type shares — frontmatter, meta.json navigation, the plain benefit-first tone for a surface-level Payload/Next/React reader, the Fumadocs components to use, Shiki-safe code fences, link rules, and grounding content in real source — and maps each doc type to its focused companion skill (ap-docs-guide-plugin / -feature / -concept / -getting-started / -example / -template / -contributing). Trigger for any docs-site editing, even when the user just says "fix the docs" or "write a docs page"; then also read the matching type skill for that page's structure.

2026-06-0528

ap-docs-guide-concept

pro-laico/atomic-payload

How to write the Core Concepts pages for the Atomic Payload docs — docs/content/docs/concepts/*.mdx (architecture, kernel, type-augmentation, caching, slugs). Use when creating, editing, or reviewing a concept page. These explain how Atomic Payload is built and why, for readers who want the mental model rather than a procedure. Builds on the ap-docs-guide skill for shared conventions.

2026-06-0428

ap-docs-guide-contributing

pro-laico/atomic-payload

How to write the Contributing pages for the Atomic Payload docs — docs/content/docs/contributing/*.mdx (index, releasing). Use when creating, editing, or reviewing contributor/maintainer docs. Unlike the rest of the site, these address people working ON the monorepo (its layout, local dev, the plugin shape, releasing/publishing), not people using the plugins. Builds on the ap-docs-guide skill for shared conventions.

2026-06-0428

ap-docs-guide-example

pro-laico/atomic-payload

How to write the Example app pages for the Atomic Payload docs — docs/content/docs/examples/*.mdx (fonts-only, icons-only, styles-only). Use when creating, editing, or reviewing an example page. These document the minimal demo apps that exercise ONE standalone plugin in isolation. Builds on the ap-docs-guide skill for shared conventions.

2026-06-0428

ap-docs-guide-feature

pro-laico/atomic-payload

How to write the Feature guide pages for the Atomic Payload docs — docs/content/docs/features/*.mdx (styles, actions, forms, icons, media, fonts, site, tracking, atomic-blocks, seeding). Use when creating, editing, or reviewing a feature page. These are the friendly "what it does / how it works / how to use it" capability guides, each paired with a plugin reference page. Builds on the ap-docs-guide skill for shared conventions (frontmatter, tone, components, fences, links).

2026-06-0428

name	ap-docs-guide-getting-started
description	How to write the Getting Started pages for the Atomic Payload docs — docs/content/docs/getting-started/*.mdx (quick-start, existing-project, environment, project-structure). Use when creating, editing, or reviewing a getting-started page. These are procedural, do-this-then-that guides that land the reader on a working project. Builds on the ap-docs-guide skill for shared conventions.

Getting Started pages

Procedural setup guides under docs/content/docs/getting-started/. Goal: take the reader from nothing to a working project, step by step. Follow ap-docs-guide for shared conventions.

Structure

Intro — one sentence on the outcome ("Scaffold a new project and land on a running dev server.").
## Prerequisites — a short bullet list (Node version, pnpm, a database URL), where relevant.
The walkthrough — a <Steps> block; each <Step> has a ### heading, a short explanation, and a labeled command/code fence. Use <Tabs groupId="package-manager"> for npm/pnpm/yarn variants.
## Next — a one-line pointer (or <Cards>) to the next guide.

Notes

Imperative, second person ("Run…", "Copy…"). One action per step.
Commands and scripts must match the real template and CLI scaffolds — copy them, don't invent (verify against templates/atomic-payload and packages/create-atomic-payload).
Keep conceptual "why" short; link to a concept page for depth.

Checklist

Follows ap-docs-guide shared conventions.
Prerequisites (if any) → <Steps> walkthrough → Next.
Every command verified against the real scaffold/template.
Package-manager variants use <Tabs groupId="package-manager">.