create-readme

スター4

フォーク0

更新日2026年7月7日 13:31

Create a README.md file for the project

インストール

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

Manusで実行

ソース

ronload

ronload/dotfiles

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

ダウンロード

Manusで実行

Role

You're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read.

Task

Take a deep breath, and review the entire project and workspace, then create a comprehensive and well-structured README.md file for the project.
Take inspiration from these readme files for the structure, tone and content:
Do not use emojis, and keep the readme concise and to the point.
Do not include sections like "LICENSE", "CONTRIBUTING", "CHANGELOG", etc. There are dedicated files for those sections.
Use GFM (GitHub Flavored Markdown) for formatting, and GitHub admonition syntax (https://github.com/orgs/community/discussions/16925) where appropriate.
If you find a logo or icon for the project, use it in the readme's header.
Render callout-style blockquotes as GitHub alerts: open with [!NOTE], [!TIP], [!IMPORTANT], [!WARNING], or [!CAUTION] on the first line, every line prefixed with >, and pick the type by intent. Reserve a plain blockquote only for a verbatim quotation — never label a quote as an alert. Only these five markers are valid on GitHub; others fall back to plain blockquotes.

このリポジトリの他の Skills

同じリポジトリ

decompose-task

ronload/dotfiles

Decompose a large phase, cycle, milestone, or epic into a set of small, actionable issues that can each be completed in a single Claude Code session. Use this skill whenever the user says things like "break this down", "拆 issue", "decompose this phase", "create issues for this milestone", "把這個大任務拆成小的", "plan this cycle", or references breaking work into subtasks, tickets, or stories. Also trigger when the user provides a SPEC.md, PRD, or feature description and asks to generate implementation tasks from it. If Linear MCP is connected, this skill can create issues directly in Linear.

2026-04-124

recon

ronload/dotfiles

Research external best practices and real-world case studies before making any architectural, design, or implementation decision. Use this skill whenever the user wants to plan, design, architect, or structure anything non-trivial — especially when they say "research first", "how do others do it", "best practices", "evidence-based", "case study", or want to avoid reinventing the wheel. Also trigger when the user is about to make a significant technical decision and hasn't yet looked at how mature projects handle it.

2026-04-084

name	create-readme
description	Create a README.md file for the project

Role

You're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read.

Task

Take a deep breath, and review the entire project and workspace, then create a comprehensive and well-structured README.md file for the project.
Take inspiration from these readme files for the structure, tone and content:
Do not use emojis, and keep the readme concise and to the point.
Do not include sections like "LICENSE", "CONTRIBUTING", "CHANGELOG", etc. There are dedicated files for those sections.
Use GFM (GitHub Flavored Markdown) for formatting, and GitHub admonition syntax (https://github.com/orgs/community/discussions/16925) where appropriate.
If you find a logo or icon for the project, use it in the readme's header.
Render callout-style blockquotes as GitHub alerts: open with [!NOTE], [!TIP], [!IMPORTANT], [!WARNING], or [!CAUTION] on the first line, every line prefixed with >, and pick the type by intent. Reserve a plain blockquote only for a verbatim quotation — never label a quote as an alert. Only these five markers are valid on GitHub; others fall back to plain blockquotes.