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

maintain-docs-spine

スター0

フォーク0

更新日2026年7月13日 18:07

Maintain the Programmers Loop documentation spine and Markdown quality contract. Use when adding, moving, linking, or revising repository docs, prompt routes, skill routes, architecture pages, or planning guidance.

インストール

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

Manusで実行

ソース

ParkerRex

ParkerRex/little-loop

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

ダウンロード

Manusで実行

Maintain Docs Spine

Start at docs/index.md; read the nearest owning page before editing.
Update the narrowest canonical document. Avoid duplicating contract details into indexes, skills, prompts, or root guidance.
Give first-class spine documents title, summary, status, read_when, and Owns, Does Not Own, and Next sections.
Use repository-relative Markdown links and valid heading anchors.
When adding a durable route, update src/docs/spine.ts and the nearest index together.
Run programmers-loop docs lint, repair every issue, then run the narrowest affected tests.

Do not add unreachable doctrine or a second source of truth for an existing contract.

このリポジトリの他の Skills

同じリポジトリ

run-exec-plan

ParkerRex/little-loop

Write, lint, grill, execute, repair, and validate one Programmers Loop ExecPlan. Use when a bounded implementation slice needs self-contained context and deterministic acceptance commands.

2026-07-140

run-program

ParkerRex/little-loop

Advance a Programmers Loop Program from evidence through convergence, immutable planning briefs, ordered ExecPlan slices, refresh, and completion. Use for initiatives too ambiguous or large for one ExecPlan.

2026-07-140

programmers-loop

ParkerRex/little-loop

Operate durable Assignment, Program, and ExecPlan loops in repositories using Programmers Loop. Use for ambiguous multi-slice work that needs checked-in decisions, bounded execution, critique, recovery, and deterministic acceptance.

2026-07-130

workshop-system

ParkerRex/little-loop

Shape an ambiguous coding-system request before creating Programmers Loop artifacts. Use when scope, source of truth, dependencies, failure modes, proof, or the choice between a Program and one ExecPlan is still unclear.

2026-07-130

diagnose-programmers-loop

ParkerRex/little-loop

Diagnose local and GitHub health for a Programmers Loop repository. Use for missing tools, invalid packets, broken configuration, agent availability, authentication, remote setup, or lifecycle drift.

2026-07-130

plan-assignment

ParkerRex/little-loop

Create or update a Programmers Loop Assignment packet. Use when one coherent body of work needs durable scope, shared evidence, Programs, standalone ExecPlans, or lifecycle status.

2026-07-130

name	maintain-docs-spine
description	Maintain the Programmers Loop documentation spine and Markdown quality contract. Use when adding, moving, linking, or revising repository docs, prompt routes, skill routes, architecture pages, or planning guidance.

Maintain Docs Spine

Start at docs/index.md; read the nearest owning page before editing.
Update the narrowest canonical document. Avoid duplicating contract details into indexes, skills, prompts, or root guidance.
Give first-class spine documents title, summary, status, read_when, and Owns, Does Not Own, and Next sections.
Use repository-relative Markdown links and valid heading anchors.
When adding a durable route, update src/docs/spine.ts and the nearest index together.
Run programmers-loop docs lint, repair every issue, then run the narrowest affected tests.

Do not add unreachable doctrine or a second source of truth for an existing contract.