Prompting guide

How to describe your project so Flempy generates what you actually want.

The one-line rule

Say what it does, how it's powered, and which MCU. Those three choices drive 80% of Flempy's decisions. Skip any of them and the AI picks defaults you might not want.

Example:

Soil moisture sensor on 2×AA batteries with ESP32. Reports readings to Home Assistant over Wi-Fi every 30 minutes.

That's 28 words and it pins down: function, power, MCU, interface, duty cycle.

Prompt patterns that work

Be specific about power

  • 2×AA → Flempy adds a boost converter for 3.3V.
  • 5V USB → Flempy drops in an AMS1117 or similar for the 3.3V rail.
  • 18650 Li-ion → Flempy adds protection circuitry (battery chargers, over-discharge cutoff).

Name the MCU when you have a preference

ESP32, Arduino Uno, RP2040, ATmega328P, Teensy 4.0. If you don't care, Flempy picks based on the use case (Wi-Fi → ESP32, low-power → ATmega, real-time audio → Teensy or RP2040).

Call out the interface

"OLED screen" is vague. "SSD1306 128×64 I²C OLED" gets you pull-ups on the right pins.

Patterns that confuse Flempy

  • Mains voltage. We refuse anything involving AC mains for safety.
  • Unprotected lithium. Flempy nudges toward protected cells or adds charger ICs when it sees LiPo / Li-ion.
  • Contradictory constraints. "High-power amp on a coin cell" will produce something technically, but it'll be weird.
  • Safety-critical designs. Flempy isn't for medical, aerospace, or automotive use.

Editing an existing design

Once you have a schematic, you can ask for changes in place:

  • "Change R4 to 1kΩ" — one-field patch.
  • "Swap the regulator for a MCP1700" — component replacement + rewire.
  • "Add a power LED on the 3.3V rail" — add component + connect.
  • "Remove the SD card slot" — drop a component + its wiring.

When Flempy is wrong

The AI misses things. Catch issues in the chat panel: if you see null Ω on a resistor, tell Flempy — "R3 has no value, make it 10k" usually fixes it. The trace solver occasionally routes a wire under a component; "redraw the VCC net cleanly" gets a fresh pass.

Next up: FAQ.