Scaffold a GitHub repository

You are an expert developer and project architect. I want you to scaffold a GitHub repository from scratch based on the following details: --- 📌 **Project Overview** - Name: [Your Project Name] - Description: [Short and concise summary of the project] - Purpose: [What problem it solves or what it's used for] --- 🧱 **Tech Stack** - Frontend: [e.g., React, Next.js, plain HTML/CSS] - Backend: [e.g., Flask, FastAPI, Node.js] - Database: [e.g., PostgreSQL, MongoDB, SQLite] - Tooling: [e.g., Docker, CI/CD with GitHub Actions, Linting tools, Testing frameworks] --- 🔐 **Security & Best Practices** - Add a `.env.example` for secrets. - Setup `.gitignore` properly. - Enforce PEP 8 (or equivalent standard for the chosen language). - Include README with setup, usage, and contribution guidelines. - Include a `LICENSE` file (MIT unless otherwise specified). - Include a `CODE_OF_CONDUCT.md` and optionally a `CONTRIBUTING.md`. --- 🧪 **Testing & Validation** - Add example test(s) using [e.g., pytest, unittest, Jest]. - Include GitHub Actions workflow to run tests and lint checks. --- 📁 **Directory Structure** Design a clean, modular, and scalable folder structure appropriate for the project. Use best practices for layout. --- 🚀 **Starter Code** Include minimal starter code for the app: - Hello world route or page - Health check endpoint - API versioning structure if applicable --- 🧩 **Optional Features** - Provide Dockerfile and docker-compose.yml - Add a `docs/` folder with Markdown docs scaffold - Setup pre-commit hooks - Include VSCode `.devcontainer` or `.vscode/settings.json` for editor config --- 📎 **Output Requirements** - Output as a Markdown-formatted list of all files and folders. - Include contents of each file inline (code blocks). - Organize the output into sections by file (README, main app, Dockerfile, etc). - Be production-ready, idiomatic, and secure-by-default. --- 💬 [Optional Instructions or Notes Here]

More Useful ChatGPT Prompt Bins