opensource-readme-generator
Open Source README Generator
This skill helps you generate professional, comprehensive, and visually appealing README files for open-source projects.
Usage Guidelines
When a user asks to create or improve a README:
-
Analyze the Project:
- Look at the files in the current directory (using
ls -Ror similar tools if allowed/safe) to understand the project type (Node.js, Python, Go, etc.). - Identify key components:
package.json,requirements.txt, source code folders, tests. - Determine the project name and purpose.
- Look at the files in the current directory (using
-
Gather Information:
- If the project purpose isn't clear from the code, ask the user for a brief description, "elevator pitch", or key features.
- Ask about specific sections if they are missing (e.g., "Do you have a demo link?", "What is the license?").
-
Use the Template:
- Read the template at
assets/all-star-readme-template.md. - Use this template as the structure for your output.
- Do not just copy the template blindly. Fill in the placeholders (
github_username,repo_name, etc.) with real data from the project or reasonable placeholders if unknown. - Customize the badges in the "Built With" section to match the technologies actually used in the project.
- Read the template at
-
Consult Guidelines:
- Refer to
references/readme-guidelines.mdto ensure you are meeting the "All-Star" criteria (clarity, visuals, completeness).
- Refer to
Workflow
- Understand: Read the user's request and explore the codebase to understand what the project does.
- Draft: Create a draft of the
README.mdin your mind or a scratchpad, mapping project details to the template sections. - Refine: Check against
references/readme-guidelines.md. - Output: Write the content to
README.md(or a file specified by the user) using thewrite_filetool.
Tips
- Badges: Always include badges. They make the repo look active and professional.
- Visuals: If you can't generate a screenshot, add a placeholder like
and tell the user to replace it. - Tone: Keep the tone professional, welcoming, and helpful.
More from irahardianto/qurio
frontend-design
Generates distinctive, production-grade frontend interfaces and artifacts (React, Vue, HTML/CSS). Prioritizes bold aesthetics, unique typography, and motion to avoid generic designs. Use when building websites, landing pages, dashboards, posters, or when the user requests to style, beautify, or create visually striking UI.
2debugging-protocol
Comprehensive protocol for validating root causes of software issues. Use when you need to systematically debug a complex bug, flaky test, or unknown system behavior by forming hypotheses and validating them with specific tasks.
2sequential-thinking
Performs dynamic, reflective problem-solving through iterative thought chains. Use for complex planning requiring revision, branching, backtracking, or hypothesis verification. Ideal for multi-step analysis where context maintenance is required or the full scope isn't initially clear.
2knowledge-searching
Retrieves implementation knowledge, code examples, and documentation references. Use to inform technical decision-making when the user requires specific library usage, framework patterns, or syntax details. Trigger on requests to 'search docs', 'find code examples', or 'check implementation details'.
2technical-constitution
Generates technical implementation plans and architectural strategies that enforce the Project Constitution. Use when designing new features, starting implementation tasks, refactoring code, or ensuring compliance with critical standards like Testability-First Architecture, security mandates, testing strategies, and error handling.
1