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

implementation-plan-wiki

스타0

포크0

업데이트2026년 7월 2일 20:08

Build or update a Vercel-hosted static wiki for Git-tracked implementation plans, with left-sidebar accordion navigation from plan index to docs, task queues, and individual task pages; include validation, protected hosting, and review gates.

설치

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

Manus에서 실행

출처

voundbrand

voundbrand/image-creation-magic

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

다운로드

Manus에서 실행

Implementation Plan Wiki

Use this skill when turning implementation_plans/ into a hosted internal wiki or updating the wiki generator for another project.

Workflow

Keep Git-tracked plan files canonical. The hosted wiki is generated output.
Generate real static HTML pages, not only a client-side SPA:
- / for all plans.
- /plans/<plan>/ for plan overview.
- /plans/<plan>/tasks/ for parsed queue rows.
- /plans/<plan>/tasks/<task-id>/ for one task.
- /plans/<plan>/docs/<doc-slug>/ for source docs.
Use a left sidebar accordion with plans, docs, task queues, and individual tasks. Add breadcrumbs so users can drill down and back up.
Preserve canonical source links for every generated page.
Protect hosted output with Vercel Deployment Protection / Vercel Authentication. If production aliases are public on the current plan, deploy real wiki content only to protected preview/deployment URLs and deploy a harmless production placeholder.

UI Conventions

The shell is a dense, calm docs/wiki UI. Keep these conventions when editing it:

Stay dependency-free static HTML/CSS/JS. No framework, no SPA conversion, no decorative gradients or marketing hero sections.
Theme: CSS custom properties in src/styles.css define a light token set on :root, a dark set on :root[data-theme="dark"], and the same dark set under @media (prefers-color-scheme: dark) scoped to :root:not([data-theme="light"]) so JS-disabled pages still follow the system theme. A tiny inline <head> script (themeBootScript in build-site.mjs) applies the stored choice before paint to avoid a flash; the .theme-toggle button in the topbar flips and persists wiki-theme in localStorage via src/app.js.
Mobile: at <= 860px the sidebar becomes a fixed off-canvas drawer toggled by the .nav-toggle button and a .scrim backdrop (handled in src/app.js). Keep .table-wrap { overflow-x: auto } and overflow-wrap: anywhere on body text so content never overflows horizontally.
Typography is compact (14px base, ~1.5 line-height). Use the --mono font for task IDs, file/source paths, plan slugs, and status badges. Keep headings clear but not oversized (h1 ~1.55rem).
Active nav state uses .nav-sub.active (accent left-border + tint). The sidebar filter (#nav-filter) hides non-matching .nav-plan/.nav-sub items.

Review And Validation

Run the local checks before reporting completion:

npm run check --prefix implementation_plans/site
PLAN_PUBLIC_PLACEHOLDER=1 npm run build:public-placeholder --prefix implementation_plans/site
PLAN_PUBLIC_PLACEHOLDER=1 node implementation_plans/site/scripts/smoke-site.mjs
git diff --check

For non-trivial generator or plan changes:

use the repo review loop (.claude/skills/pr-review-loop/SKILL.md) when creating a review branch or draft pull request (GitHub by default; Azure DevOps or GitLab also work);
run or read CodeRabbit feedback when available;
use an independent review pass for schema, parser, or deployment-protection changes;
keep merge, policy bypass, protected-branch, credential, and public-sharing actions human-gated.

Scaffold Into A New Project

This skill bundles a ready-to-use generator under template/. To stand up the wiki in another repo:

Copy the template into the target repo's plans area:

mkdir -p <repo>/implementation_plans/site
cp -R .claude/skills/implementation-plan-wiki/template/. <repo>/implementation_plans/site/
cd <repo>/implementation_plans/site && npm install

Adjust the project-specific knobs in scripts/build-site.mjs (plansRoot, excludedPlanDirs, planDocOrder, and the parseTaskQueue column expectations) and set name in package.json. The template README lists each knob.

Validate locally:

npm run check
PLAN_PUBLIC_PLACEHOLDER=1 npm run build:public-placeholder

Link and deploy with protection (see "Hosting" in the template README); keep dist/ and .vercel/ out of Git.

Keep template/ in sync when you improve the live generator under implementation_plans/site/ — the template is the reusable seed, not a fork.

Do not copy .vercel/, dist/, local env files, or deployment URLs between projects.

이 저장소의 다른 Skills

같은 저장소

identity-image-pipeline-guide

voundbrand/image-creation-magic

Teach or plan reliable identity-preserving AI image generation, face swapping, face inpainting, and ComfyUI workflows using InstantID, PuLID, IP-Adapter FaceID, ReActor, InsightFace-style verification, retry/repair loops, and consent/privacy gates. Use when someone asks how to build repeatable image generation with consistent people or automated multi-face identity preservation.

2026-07-020

overnight-agent-runbook

voundbrand/image-creation-magic

Run implementation work unattended/overnight with a review-driven PR loop. The agent picks one reviewable slice, owns its branch through an agnostic code review (CodeRabbit CLI or a fresh independent reviewer), may integrate agent-owned non-main branches after green gates, never merges to main, and reports a structured closeout. Replaces the retired kanban/dispatcher/polling model. Use when prompting an agent to work autonomously against a task queue or implementation plan.

2026-07-020

pr-review-loop

voundbrand/image-creation-magic

Agent-owned CodeRabbit review loop for implementation branches. Use when reviewing or fixing a branch before closeout, with or without a hosted pull request.

2026-07-020

name	implementation-plan-wiki
description	Build or update a Vercel-hosted static wiki for Git-tracked implementation plans, with left-sidebar accordion navigation from plan index to docs, task queues, and individual task pages; include validation, protected hosting, and review gates.

Implementation Plan Wiki

Use this skill when turning implementation_plans/ into a hosted internal wiki or updating the wiki generator for another project.

Workflow

Keep Git-tracked plan files canonical. The hosted wiki is generated output.
Generate real static HTML pages, not only a client-side SPA:
- / for all plans.
- /plans/<plan>/ for plan overview.
- /plans/<plan>/tasks/ for parsed queue rows.
- /plans/<plan>/tasks/<task-id>/ for one task.
- /plans/<plan>/docs/<doc-slug>/ for source docs.
Use a left sidebar accordion with plans, docs, task queues, and individual tasks. Add breadcrumbs so users can drill down and back up.
Preserve canonical source links for every generated page.
Protect hosted output with Vercel Deployment Protection / Vercel Authentication. If production aliases are public on the current plan, deploy real wiki content only to protected preview/deployment URLs and deploy a harmless production placeholder.

UI Conventions

The shell is a dense, calm docs/wiki UI. Keep these conventions when editing it:

Stay dependency-free static HTML/CSS/JS. No framework, no SPA conversion, no decorative gradients or marketing hero sections.
Theme: CSS custom properties in src/styles.css define a light token set on :root, a dark set on :root[data-theme="dark"], and the same dark set under @media (prefers-color-scheme: dark) scoped to :root:not([data-theme="light"]) so JS-disabled pages still follow the system theme. A tiny inline <head> script (themeBootScript in build-site.mjs) applies the stored choice before paint to avoid a flash; the .theme-toggle button in the topbar flips and persists wiki-theme in localStorage via src/app.js.
Mobile: at <= 860px the sidebar becomes a fixed off-canvas drawer toggled by the .nav-toggle button and a .scrim backdrop (handled in src/app.js). Keep .table-wrap { overflow-x: auto } and overflow-wrap: anywhere on body text so content never overflows horizontally.
Typography is compact (14px base, ~1.5 line-height). Use the --mono font for task IDs, file/source paths, plan slugs, and status badges. Keep headings clear but not oversized (h1 ~1.55rem).
Active nav state uses .nav-sub.active (accent left-border + tint). The sidebar filter (#nav-filter) hides non-matching .nav-plan/.nav-sub items.

Review And Validation

Run the local checks before reporting completion:

npm run check --prefix implementation_plans/site
PLAN_PUBLIC_PLACEHOLDER=1 npm run build:public-placeholder --prefix implementation_plans/site
PLAN_PUBLIC_PLACEHOLDER=1 node implementation_plans/site/scripts/smoke-site.mjs
git diff --check

For non-trivial generator or plan changes:

use the repo review loop (.claude/skills/pr-review-loop/SKILL.md) when creating a review branch or draft pull request (GitHub by default; Azure DevOps or GitLab also work);
run or read CodeRabbit feedback when available;
use an independent review pass for schema, parser, or deployment-protection changes;
keep merge, policy bypass, protected-branch, credential, and public-sharing actions human-gated.

Scaffold Into A New Project

This skill bundles a ready-to-use generator under template/. To stand up the wiki in another repo:

Copy the template into the target repo's plans area:

mkdir -p <repo>/implementation_plans/site
cp -R .claude/skills/implementation-plan-wiki/template/. <repo>/implementation_plans/site/
cd <repo>/implementation_plans/site && npm install

Adjust the project-specific knobs in scripts/build-site.mjs (plansRoot, excludedPlanDirs, planDocOrder, and the parseTaskQueue column expectations) and set name in package.json. The template README lists each knob.

Validate locally:

npm run check
PLAN_PUBLIC_PLACEHOLDER=1 npm run build:public-placeholder

Link and deploy with protection (see "Hosting" in the template README); keep dist/ and .vercel/ out of Git.

Keep template/ in sync when you improve the live generator under implementation_plans/site/ — the template is the reusable seed, not a fork.

Do not copy .vercel/, dist/, local env files, or deployment URLs between projects.