agentleFS
mementomori-comementomori-co/maker-mastery/.claude/skills/led-budget/SKILL.md

led-budget

Skill2 starsChanged 26 days agoMITView on GitHub

Use when an LED, wiring or power question needs numbers (current per LED, PSU size, injection points, wire gauge, level shifting, capacitors). Runs the electronics-engineer in a fresh context and returns the budget with datasheet URLs; the lead saves it beside the build.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read knowledge\08-electronics-lighting\ (for example the WS2812B power note: the WorldSemi datasheet gives a per-channel current.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Input: $ARGUMENTS: strip type and density, length or count, controller (for example Raspberry Pi or ESP32), supply. Output: the budget in the reply (electronics-engineer has no Write tool).

When to use

Any lighting or low-voltage wiring plan; before /pi-power-budget when the LED rail dominates.

Steps

  1. Read knowledge\08-electronics-lighting\ (for example the WS2812B power note: the WorldSemi datasheet gives a per-channel current; the often-quoted 60 mA per LED is a community rule of thumb) and cite.
  2. Compute LED count, worst-case and realistic current, PSU with a stated margin, injection points, wire gauge with a resistance source, series resistor, bulk capacitor; level shifting with VIH math and a named part with its datasheet URL.
  3. Label every value: datasheet / official / community / computed.
  4. Return the table and the wiring list.

Common rationalizations

RationalizationReality
"60 mA per LED, everyone uses it."Check the datasheet's per-channel figure; 60 mA is a community rule. Say which you used.
"3.3 V drives WS2812B fine."VIH is 0.7 x VDD, which is 3.5 V at 5 V supply; use a level shifter.

Red flags

  • A PSU size without the margin stated.
  • Feeding LEDs from a single-board computer's 5 V header.

Verification

  • Every number labelled by source class with a URL.
  • Level shifter named with datasheet.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.