Learn to build complete projects by implementing the logic yourself.
Build From Skeleton provides project structure, function signatures, clear requirements, and tests. You turn the unfinished functions into a working application, one milestone at a time.
The repository is being prepared for its first Python project. There are no published learner projects yet. The expense tracker below is a specification, not an application you can install today.
| Project | Language | Prerequisites | Status |
|---|---|---|---|
| CLI expense tracker | Python | Functions, lists, dictionaries, exceptions, and basic file handling | Specified; implementation next |
You know basic programming syntax and want practice connecting functions into a complete application. The structure helps you get started; the implementation decisions and debugging remain yours.
Python is the initial focus. Additional languages can be proposed once the first projects establish a format maintainers can support.
- Fork this repository and clone your fork.
- Pick a published project and follow its own setup instructions.
- Read the requirements and implement the functions for the first milestone.
- Run that milestone's tests, then continue through the remaining milestones.
- Consult optional hints or the separately marked reference solution when needed.
Unfinished Python functions will raise NotImplementedError. Learner tests are
expected to fail until you implement the corresponding behavior. Setup and test
discovery should still work in an untouched skeleton.
Each project will have independent dependencies and commands. No virtual environment is included in a checkout; create one using the project's instructions.
Contributions can add project skeletons, improve instructions and hints, or fix tests. Keep learner exercises unfinished in contributed skeletons. Complete your own solutions in your fork; reference solutions belong in a separate, clearly marked location.
- Read CONTRIBUTING.md before opening a PR.
- Follow the skeleton standard.
- Propose substantial new projects through a new skeleton issue.
- Read the code of conduct.
Maintained by Basil Zafar. Review happens as maintainer time permits; there is no guaranteed response time.
The Week 1 checklist records the foundation work. The Week 2 backlog describes the first implementation. Future project ideas are proposals, not promises of availability.
Original repository material is available under the MIT license. Retain applicable copyright and license notices when reusing it. Third-party material, if introduced, must retain its own required notices and compatible terms.