State what the reader will build or learn. Open with a relatable scenario or clear goal: "In this guide, we'll..."
Required tools, accounts, or hardware
Link each tool/service on first mention
Brief context sentence, why this step matters. Use code blocks for commands, inline code for filenames and values.
Continue the pattern. Each build step = one phase of the build. Link to external repos for full code instead of pasting walls of code.
Add as many steps as needed. Each step should be a clear, actionable phase.
Tell the reader how to confirm it works. Describe expected output or show what success looks like. Mention common pitfalls briefly if relevant.
Summarize what was accomplished in 2–3 sentences. Suggest ideas for extending or remixing the project. Keep the tone forward-looking and inspiring.
Invite readers to share their results. Link to relevant community spaces. Close with genuine enthusiasm: "We'd love to see what you build!"
BRASA is an open-source, low-cost node that watches a home after its residents evacuate, uses on-device AI to detect a growing ember ignition, sprays only the affected zone, verifies the result thermally, and reports to responders over an encrypted offline LoRa mesh.
REMA is an offline Edge AI assistant designed to support people during emergencies and infrastructure failures. It identifies available resources, translates them into practical capabilities, and helps users prioritize those capabilities according to their immediate needs. Unlike a generic chatbot or survival guide, REMA uses a local resource capability map and validated safety rules to provide recommendations based on what is actually available. The system can update its recommendations when resources are added, removed, or depleted. REMA is designed to work without internet or cloud connectivity, making it useful when critical infrastructure is unavailable. When infrastructure fails, use what remains.