Rapid Software Engineering Foundation Setup

Create initial foundation of a Software engineering project. You just have to create initial foundation and nothing else. Just normal README and initial working code solution with some indicators. Go through the attached html file. I want it immediately in 1 day. As a Project Admin, you are responsible for preparing your repository to receive contributors, managing the contribution workflow throughout the program season, and ensuring your project is genuinely improved by the participation. The quality of your project's onboarding - documentation, issue descriptions, contributing guidelines - is the single largest determinant of the quality of contributions you will receive. Projects that invest in preparation receive measurably better work. Before the Program Begins Excellent README Your README must include: project purpose, tech stack, local setup instructions tested on a clean machine, contribution guidelines, and a contact channel. Instructions that only work on your machine are not sufficient. Structured Issue Labelling Create and apply labels: good first issue, bug, feature, help wanted, documentation. Every labelled issue must include enough context for a contributor to begin work without asking for clarification. Beginner-Friendly Issues Create at least five issues labelled good first issue that are genuinely appropriate for contributors with limited experience. Do not apply this label to complex architectural problems. [login to view URL] File Create a [login to view URL] that explains: pull request format and description requirements, commit message conventions, test expectations, code style, and your typical review timeline. CI/CD Checks Configure automated checks - tests, linting, formatting - that run on every pull request. This protects code quality and gives contributors immediate feedback without waiting for your review. During the Program Respond to Assignment Requests Quickly Respond to contributor issue assignment requests within 24 hours. Requests left unanswered for 48+ hours may be auto-assigned by the program platform. Review Every Pull Request Thoroughly Read every pull request carefully before merging. Add inline comments on specific lines. Do not merge pull requests you have only skimmed. Uphold Code Quality Standards Reject any pull request where the contributor cannot explain their implementation. Ask contributors to walk through their approach before you approve. This protects the long-term health of your project. Track Your Active Contributors Maintain awareness of which contributors are actively working on your repository. At program close, you will be asked to vouch for your most impactful contributors. Repository Standards All registered repositories must have an open source license (MIT, Apache 2.0, GPL 3.0, or equivalent) The default branch must be protected - no direct pushes, only reviewed pull requests CI/CD status checks must pass before a pull request can be merged Repositories must not contain personally identifiable information in the codebase or commit history Project admins must not merge their own pull requests without at least one other reviewer

Project ID: 40429385