AeroTools
Home AI Prompts Develop a UI Library for ESP32

Develop a UI Library for ESP32

chatgpt development 13 uses
Free
What is this prompt for?

Written for developers: it directs the model to produce, review or debug code with a clear brief instead of a vague request.

What it actually does: Act as an Embedded Systems Developer. You are an expert in developing libraries for microcontrollers with a focus on the ESP32 platform.

Main use cases:
  • Reviewing pull requests with practical suggestions
  • Generating clean, readable code
  • Spotting security flaws and fixing bugs
Benefits and results:
  • Generated code that is easy to extend and integrate
  • Less time spent on review inside the team
  • Clearer documentation, so the project stays maintainable
Prompt length: 206 words Reading time: ~2 min Best with: Claude Sonnet (recommended for code), GPT-4o, GitHub Copilot

Prompt

Act as an Embedded Systems Developer. You are an expert in developing libraries for microcontrollers with a focus on the ESP32 platform.

Your task is to develop a UI library for the ESP32 with the following specifications:

- **MCU**: ESP32
- **Build System**: PlatformIO
- **Framework**: Arduino-ESP32
- **Language Standard**: C++14 (modern, RAII-style) Compiler flag "-fno-rtti"
- **Web Server**: ESPAsyncWebServer
- **Filesystem**: LittleFS
- **JSON**: ArduinoJson v7
- **Frontend Schema Engine**: UI-Schema

You will:
- Implement a Task-Based Runtime environment within the library.
- Ensure the initialization flow is handled strictly within the library.
- Conform to a mandatory REST API contract.
- Integrate a C++ UI DSL as a key feature.
- Develop a compile-time debug system.

Rules:
- The library should be completely generic, allowing users to define items and their names in their main code.

This task requires a detailed understanding of both hardware interface and software architecture principles.

Your responsibilities:
- Develop backend logic for device control and state management.
- Serve static frontend files and provide UI-Schema and runtime state via JSON.
- Ensure frontend/backend separation: Frontend handles rendering, ESP32 handles logic.

Constraints:
- No HTML, CSS, or JS logic in ESP32 firmware.
- Frontend is schema-driven, controlled via JSON updates.

Related Prompts

AeroTools

AeroAssistant

Online AI
Hello! I am your official AeroTools AI Assistant. How can I help you use our tools today?