ワンクリックでManusで任意のスキルを実行

wf-readme

スター5

フォーク0

更新日2026年7月23日 09:22

Use when a project README already exists and the user asks to preserve, merge, modernize, optimize, or clarify repository documentation during harness install or documentation work.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

zingspark

zingspark/create-harness-vibe-coding

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

README Optimizer

Improve README.md without breaking project-owned public docs.

Load

root README.md
package files and scripts (package.json, pyproject.toml, go.mod, etc.)
CI files when present
Harness/PROGRESS.md
Harness/tasks/<task-id>/PLAN.md when available
Harness/project/architecture.md only when an architecture summary or diagram is requested

Cache Discipline

Follow Harness/specs/runtime/context-loading.md#Cache-First Context Contract: load project facts in the listed order, inspect only relevant README/package/CI sections, and keep unknowns or command output in the dynamic suffix.

Mode

Ask the user which mode they approve when the existing README is meaningful:

Mode	Use when	Allowed edit
Preserve + append	default for existing projects	Add only a compact Development, Test, Build, Git, or Harness section
Structure pass	README is stale, hard to scan, or missing operational docs	Reorganize with headings, tables, command blocks, and links while preserving facts
Full rewrite	user explicitly wants a polished public README	Rewrite after approval; keep claims source-backed

If unanswered, use Preserve + append.

Rules

Preserve existing product, package, API, and public-facing content unless the user approves a rewrite.
Do not invent features, benchmarks, roadmap, support policy, badges, install commands, or CI status.
Use tables for command matrices, environment variables, endpoints, and deployment notes when facts are known.
Use Mermaid or ASCII architecture diagrams only when the structure is observed or approved; label uncertain diagrams as proposed.
Keep detailed architecture in Harness/project/architecture.md; README may link to it or show a short overview.
Keep agent rules in CLAUDE.md/AGENTS.md, not README.
Record the chosen mode and any skipped README improvements in Harness/tasks/<task-id>/PLAN.md when available.

Output

Before broad edits, return:

chosen mode
sections to preserve
sections to add or reorganize
facts still unknown
verification command or manual review step

このリポジトリの他の Skills

同じリポジトリ

wf-browser

zingspark/create-harness-vibe-coding

Built-in browser automation and E2E verification workflow. Use for Claude /wf-browser, Codex $wf-browser or /skills wf-browser, Browser Use, Playwright, Chrome DevTools/CDP, screenshots, forms, UI verification, and browser-visible acceptance.

2026-07-265

wf-help

zingspark/create-harness-vibe-coding

Codex compatibility: use $wf-help or /skills wf-help in Codex to show the Harness WF command table. Claude Code and OpenCode use the direct /wf-help command.

2026-07-265

wf-max

zingspark/create-harness-vibe-coding

Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex. WF-MAX is explicit only — the user must type /wf-max, $wf-max, or /skills wf-max.

2026-07-265

subagent-orchestrator

zingspark/create-harness-vibe-coding

Use when work needs bounded subagent coordination, parallel read-only exploration, independent review gates, broad context partitioning, or controlled handoffs.

2026-07-235

tdd

zingspark/create-harness-vibe-coding

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

2026-07-235

wf-agents-docs

zingspark/create-harness-vibe-coding

Source-backed CLI invocation guide for Claude Code, Codex, and OpenCode automation. Use when invoking peer CLIs, writing batch tests, collecting cache telemetry, debugging command-line flags, or documenting cross-runtime agent usage for Harness workflows.

2026-07-235

README Optimizer

Improve README.md without breaking project-owned public docs.

Load

root README.md

package files and scripts (package.json, pyproject.toml, go.mod, etc.)

CI files when present

Harness/PROGRESS.md

Harness/tasks/<task-id>/PLAN.md when available

Harness/project/architecture.md only when an architecture summary or diagram is requested

Cache Discipline

Mode

Ask the user which mode they approve when the existing README is meaningful:

Mode

Use when

Allowed edit

Preserve + append

default for existing projects

Add only a compact Development, Test, Build, Git, or Harness section

Structure pass

README is stale, hard to scan, or missing operational docs

Reorganize with headings, tables, command blocks, and links while preserving facts

Full rewrite

user explicitly wants a polished public README

Rewrite after approval; keep claims source-backed

If unanswered, use Preserve + append.

Rules

Preserve existing product, package, API, and public-facing content unless the user approves a rewrite.

Do not invent features, benchmarks, roadmap, support policy, badges, install commands, or CI status.

Use tables for command matrices, environment variables, endpoints, and deployment notes when facts are known.

Use Mermaid or ASCII architecture diagrams only when the structure is observed or approved; label uncertain diagrams as proposed.

Keep detailed architecture in Harness/project/architecture.md; README may link to it or show a short overview.

Keep agent rules in CLAUDE.md/AGENTS.md, not README.

Record the chosen mode and any skipped README improvements in Harness/tasks/<task-id>/PLAN.md when available.

Output

Before broad edits, return:

chosen mode

sections to preserve

sections to add or reorganize

facts still unknown

verification command or manual review step

name	wf-readme
description	Use when a project README already exists and the user asks to preserve, merge, modernize, optimize, or clarify repository documentation during harness install or documentation work.