| name | prototyping |
| description | Methodologies for rapidly building software proofs-of-concept |
Prototyping Skill
United Philosophy
"Make it work, then make it right, then make it fast." - Kent Beck
1. Directory Structure
All prototypes should live in a results/demos/ directory in the root.
results/[YYYY-MM-DD]-[Topic]/demo/
├── demo_name/
│ ├── app.py (entry point)
│ ├── requirements.txt
│ └── README.md
2. Technology Stack Recommendations
Interactive Web Apps (Python)
- Streamlit: Best for data apps, dashboards, and ML demos. Fast iteration.
- Gradio: Best for exposing ML models with simple inputs/outputs.
- FastHTML: Good for pure Python dynamic web apps.
CLI Tools
- Typer or Click: For robust command-line interfaces.
- Rich: For beautiful terminal output.
Web Content
- HTML/JS (Vanilla): For simple visualizations or logic.
3. Best Practices
- Hardcode Data: Don't build a backend unless necessary. Mock data in JSON.
- Single File: Keep it simple initially. One
app.py is often enough.
- Readme: Always include instructions on how to run it (e.g.,
pip install -r requirements.txt && streamlit run app.py).