القائمة
Generate an 'Awesome' style README.md with Table of Contents, Contributors, License, and Star History. Use when asked for 'awesome readme' or 'professional github readme'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Write master's-level academic theses in Vietnamese with formal scholarly style, IEEE citations, and bilingual terminology. Use when writing thesis chapters, research papers, or academic content in Vietnamese.
Generate context summary for a PRD. Use when user wants to create context, summarize PRD for onboarding, create a cheat sheet, or says 'context PRD-XXX', 'summarize PRD', 'context for PRD'.
Brainstorm and document a project or feature idea. Use when user wants to brainstorm, capture an idea, explore a concept, or says 'idea', 'brainstorm', 'I want to build', 'new feature idea'.
Create implementation plan from a PRD. Use when user wants to implement a PRD, create technical spec, plan implementation, or says 'implement PRD-XXX', 'build PRD-XXX', 'plan implementation'.
Generate or update project overview document. Use when user wants a project overview, system architecture, big picture, high-level view, or says 'overview', 'architecture overview', 'project summary', 'how does everything connect'.
Create PRD (Product Requirements Document) for a project. Use when user needs to write PRD, create product requirements, plan features, or mentions PRD/product requirements/feature spec.
| name | awesome-readme |
| description | Generate an 'Awesome' style README.md with Table of Contents, Contributors, License, and Star History. Use when asked for 'awesome readme' or 'professional github readme'. |
You are an expert open-source maintainer and technical writer. Your goal is to write a README.md that matches the top-tier "Awesome" repository standards on GitHub (e.g. antigravity-awesome-skills format).
Use this skill when:
An awesome README must have the following exact sections with Emojis:
Start with an Emoji + Header 1. Followed by a catchy description line. You can optionally include badges (CI/CD, Version, License) here.
For badges, use this standard format:
## Table of Contents
- [🚀 Quick Start](#quick-start)
- [🛠️ Installation](#installation)
- [📦 Features](#features)
- [🤝 How to Contribute](#how-to-contribute)
- [💬 Community & Support](#community--support)
- [👥 Repo Contributors](#repo-contributors)
- [⚖️ License](#license)
- [🌟 Star History](#star-history)
---
Provide a 1-minute quick start and precise installation instructions, using tables or clear code blocks.
Use a Markdown Table to display features elegantly if possible, or bold bullet points with emojis.
## How to Contribute
We welcome contributions! Please follow these steps:
1. **Fork** the repository.
2. **Create a new branch** for your feature.
3. **Submit a Pull Request**.
## Support the Project
If this repository saves you time, please star the repository!
Use contrib.rocks to dynamically generate a contributor image based on the repository slug.
Format:
## Repo Contributors
<a href="https://github.com/USERNAME/REPO_NAME/graphs/contributors">
<img src="https://contrib.rocks/image?repo=USERNAME/REPO_NAME" alt="Repository contributors" />
</a>
Made with [contrib.rocks](https://contrib.rocks).
Note: Infer the USERNAME/REPO_NAME from package.json, .git/config or ask the user.
## License
MIT License. See [LICENSE](LICENSE) for details.
## Star History
[](https://star-history.com/#USERNAME/REPO_NAME&Date)
sickn33/antigravity-awesome-skills). If missing, use placeholder your-username/your-repo or extract from git remote.