TrailCurrent Claude Skills

A growing library of Claude skills that we use in TrailCurrent's R&D processes — from authoring embedded GUIs to running our hardware tooling.

We're publishing these as we extract them from our day-to-day work, so that other teams building hardware and embedded products can reuse the same workflows we rely on internally.

What is a Claude skill?

A skill is a folder containing a SKILL.md file with YAML frontmatter (name, description) plus optional supporting scripts and references. When Claude Code encounters a task that matches a skill's description, it loads the skill and follows its instructions — encoding domain knowledge that would otherwise have to be re-derived every session.

See Anthropic's skills documentation for the format spec.

Skills in this repo

Skill	What it does
eezstudio/	Author and debug EEZ Studio LVGL projects (.eez-project JSON files) programmatically. Covers measuring widget geometry against real TTF fonts, bisecting silently-failing project files, the Docker full simulator (0.26+) and what it constrains, LVGL 9 specifics, and the EEZ Studio → idf.py build handoff for ESP32 / LVGL firmware. Ships the verifier and preview scripts the skill's gates call (verify_project.py, verify_no_canvas_divergence.py, render_pages.py, font_metrics.py) plus a SCHEMA_REFERENCE.md derived from the EEZ Studio source.
freecad-automation/	Drive FreeCAD over an MCP server to build parametric PartDesign models, App::Link assemblies, and CAM (Path) jobs. Covers the failure modes that report success while producing nothing — inert CAM jobs, empty DXF exports, pockets that cut air, and modelled dogbones that never survive the toolpath offset.
blender-automation/	Drive Blender over an MCP server for product renders and multi-stage assembly animations built from CAD. Covers the CAD → glTF handoff (never STL), lighting matte-black enclosures without them going mid-grey, and the parenting, visibility, and sandbox traps that make an animation silently render the wrong thing.

More skills will be added as we extract them — pinout diagram generation, KiCad library tooling, CAD-to-photo rendering, and others currently live in our internal toolbox.

Using a skill

Copy the skill directory into your Claude Code skills location:

# User-scope (available in every project)
cp -r eezstudio ~/.claude/skills/

# Or project-scope (available only inside one project)
cp -r eezstudio /path/to/your/project/.claude/skills/

Claude Code picks the skill up automatically — it appears in the available-skills list at session start and is invoked when a task matches its description.

Contributing

Issues and pull requests are welcome. If you add a skill, please:

1. Place it in its own top-level directory.
2. Include a SKILL.md with the required name and description frontmatter fields. The description should make clear when the skill should be invoked, not just what it does.
3. Add a row to the table above.

License

MIT — use, modify, and redistribute freely.