Thank you for your interest in contributing! This repository shares high-quality, framework-specific, and stack-specific coding prompts and guidelines designed to help developers write better, cleaner, and more maintainable frontend code using Gemini CLI.
- ✍️ Add or improve instruction files — submit best practices, tips, or templates for popular frontend frameworks or stacks.
- 🐞 Fix typos or improve clarity — clear and concise instructions make the repo more valuable.
- 💡 Suggest new topics or frameworks — if you think something important is missing, open an issue or PR.
- 🧪 Add examples — practical prompt vs. output markdowns help others understand real-world use.
- 🚀 Report bugs or issues — flag outdated or incorrect info.
- Follow existing folder and naming conventions.
- Write in clear, concise English.
- Use consistent markdown formatting.
- Be respectful and constructive in reviews and discussions.
- Keep instructions practical and actionable for Gemini CLI users.
- For major changes, open an issue to discuss before submitting a PR.
- Fork the repository.
- Create a new branch for your change.
- Make your edits or add files.
- Commit with clear messages.
- Push your branch and open a Pull Request against the
mainbranch. - Respond to feedback and collaborate during review.
This project follows a Code of Conduct. Please be kind and respectful.
Thank you for helping improve Code Instructions Kit! 🙌