使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jimweller/clanker-skills --skill md-style開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
<!-- markdownlint-disable-file MD041 -->
README Style Guide
Write concise, direct README files for experienced engineers.
Voice
Prose style is not defined here. The clanker-prose plugin's prose-contract owns it, injected via a SessionStart hook pointer to its two sections:
Ghostwriting for Other Humans- a README is read by another human, so it takes the ghostwriting
contract: minimum facts, one fact per sentence, the deletion test on every word
Banned Patterns in All Writing- the catalog of forbidden words and constructions, including
hype vocabulary, opposing phrases, phantom-foil contrast, emojis, and emdashes
This skill covers what belongs in a README and in what order.
Principles
- No fluff - Skip tables of contents, verbose explanations, development history
- No roadmaps - Document current state only, not plans or decisions. Readme is an engineering specification. Not a project plan or changelog.
Structure
Sections in order: Overview, Prerequisites, Usage, Architecture, Configuration, Testing, File Structure. One-line purpose statement at top under H1.
Exclude
- Tables of contents
- Verbose troubleshooting guides
- Development decisions/history
- Future plans/roadmaps
- Lengthy explanations of concepts
- Multiple examples of similar things
Formatting
- Tables for structured data (components, variables, test coverage)
- Code blocks for commands and examples
- Bold for emphasis sparingly
