agentleFS
Sign inStart free
wedsamuel1230wedsamuel1230/embedded-engineering-skills/skills/enclosure-designer/SKILL.md

enclosure-designer

Skill28 starsChanged 30 days agoMITView on GitHub

Use when users need a 3D-printable enclosure for an Arduino, ESP32, or RP2040 project and need help with measurements, cutouts, print settings, or environmental protection.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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. Distinctive:

    Use this skill to design practical enclosures without loading a full mechanical guide up front.

    line 9
  2. Distinctive:

    Use this skill when the user asks for:

    line 24
  3. Very specific:

    Use assets/basic-template.scad or scripts/generate_enclosure.py when the user needs a concrete starting model.

    line 45
  4. Distinctive:

    Treat user measurements as authoritative over reference dimensions.

    line 50
  5. Distinctive:

    Add clearance deliberately for connectors, wiring, and print tolerance.

    line 51
  6. Distinctive:

    Do not promise waterproofing from geometry alone.

    line 53
  7. Distinctive:

    Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, …

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Enclosure Designer

Use this skill to design practical enclosures without loading a full mechanical guide up front.

Resources

  • assets/basic-template.scad - starting OpenSCAD template
  • scripts/generate_enclosure.py - enclosure generator script
  • references/design-workflow.md - measurement, parameter, and generator workflow
  • references/dimensions.md - common board and module dimensions
  • references/print-and-protection.md - wall thickness, print settings, ventilation, and waterproofing

When to Use

Use this skill when the user asks for:

  • an enclosure, case, box, or housing
  • mounting holes or cutout placement
  • OpenSCAD-based enclosure generation
  • board fit checks for Arduino, ESP32, or Pico-class boards
  • print-material or weather-resistance guidance

Workflow

  1. Gather the minimum physical inputs:
    • board dimensions
    • tallest component
    • connector locations
    • mounting method
    • environmental constraints
  2. Open references/design-workflow.md for the parameterization flow.
  3. Open references/dimensions.md if the user does not already have exact measurements.
  4. Open references/print-and-protection.md for material, wall, ventilation, or moisture guidance.
  5. Use assets/basic-template.scad or scripts/generate_enclosure.py when the user needs a concrete starting model.

Core Rules

  • Treat user measurements as authoritative over reference dimensions.
  • Add clearance deliberately for connectors, wiring, and print tolerance.
  • Separate fit problems from printability problems.
  • Do not promise waterproofing from geometry alone.

Verification

  • The board and connectors fit with explicit clearance.
  • Mounting points and cable exits are reachable.
  • The selected material and wall thickness match the use environment.
  • Print orientation and support strategy are named before finalizing the design.

Integration

  • Pair with battery-selector or power-budget-calculator if battery size drives the enclosure volume.
  • Pair with readme-generator when the enclosure should be documented for a project repo.

Shared Output Contract

Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, known limitations, and recovery/security notes.

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.

Check your setup, free