Attaky-Firmware-Builder

KO | EN

gitlite — search

#ui #react-native #react #terminal #shell #csharp #containers #data-science #nlp #kubernetes

Attaky-Firmware-Builder

(★ 9)

Open-source AI skill chain that turns plain-language ideas or existing firmware into compiled, flashed, and boot-verified builds for Attaky modular handhelds.

File Explorer

ZIP Download

- marketplace.json
- plugin.json
- plugin.json
- attaky-logo-horizontal.png
- aw9523-driver-patterns.md
- collaboration-mode.md
- connectivity-patterns.md
- display-and-lvgl-gotchas.md
- esp32-bringup-and-rtos-patterns.md
- hardware-catalog.md
- imu-driver-patterns.md
- module-detection-and-safe-boot.md
- persistence-patterns.md
- realtime-audio-patterns.md
- screenshot-debug.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- - SKILL.md
- build-dist.sh
- claude-ai-descriptions.json
.gitignore
AGENTS.md
LICENSE
NOTICE
README.md

# Use via CDN

jsDelivr

jsDelivr serves any public GitHub repository as a CDN with zero setup. Pick a version and a file to get a ready-to-paste link and snippet.

Version

File

Link

Example

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<h2>Idea-to-firmware AI skill chain for Attaky modular handhelds</h2>

<a href="https://attaky.com">Attaky home</a>
  &nbsp;·&nbsp;
  <a href="https://discord.attaky.com">Discord</a>

</div>

> Describe what you want your Attaky to do, in plain language. The skill
> chain turns that into a concept, a spec, screen designs, and real
> firmware source — then compiles it, flashes it over USB, and verifies
> the boot on your actual device. You make the product calls; every
> technical decision is handled for you.

## Compatible devices

Attaky modular handhelds — any Complete Build assembled around the
Attaky Core, across the Mesh, Retro, Radio, and Agent Series, as well
as custom module assemblies that follow the combination rules in the
bundled hardware catalog. `firmware-brainstorm` recommends the best-fit
Complete Build for your idea as part of the flow.

## What it does

Seven skills cover the full path:

1. **firmware-brainstorm** — Describe what you want. Get a high-level concept (software interaction + hardware combination + feature list) and a best-fit Complete Build recommendation. Iterate until the concept is approved.
2. **firmware-spec** — Once the concept is approved, generate the detailed implementation spec: bill of materials, module combination, software PRD, dev plan.
3. **firmware-ui** — Optional visual design pass for firmware with visible UI. Generate style tokens, screen layouts, sprites, and a browser preview.
4. **firmware-codegen** — Generate the firmware source project from the spec and optional UI package. Two supported toolchains; the chain picks silently and records why.
5. **firmware-build** — Compile the source to a flashable `.bin`. Both toolchains supported.
6. **firmware-deploy** — Flash to your Attaky device locally via esptool and verify the boot over serial. The Attaky web flasher and firmware-store upload paths are staged in the skill and activate when those services ship.
7. **firmware-port** — Alternate entry: port an existing open-source firmware to Attaky hardware. Survey the upstream, check the license, plan the port at the upstream's own board seam, implement, then join the chain at firmware-build for milestone-gated bring-up.

Each skill can also be invoked on its own — drop in at any stage if you already have the upstream artifact.

## Highlights

- **You choose how to work.** Every run starts with a collaboration-mode choice: let the chain build a working first version end-to-end and refine it together, or check in step by step at each stage. Technical decisions stay out of your way in both modes.
- **Grounded in real hardware facts.** A bundled public hardware catalog documents every Attaky module — capabilities, wiring, combination rules, recommended libraries — so generated code targets what the hardware actually is, never a guess.
- **Safe on the wrong hardware.** Every generated firmware verifies at boot that the attached modules match the build it was made for. On a mismatch it parks every module pin and drops to a safe Core-only mode with an on-screen explanation — a wrong flash cannot misdrive another module's pins. Harmless extras (say, an attached keyboard the firmware doesn't use) pass with a note, and holding the Boot button for 5 seconds force-starts anyway if you know what you're doing.
- **Bring-up discipline built in.** First-flash self-test baselines for both toolchains, opt-in milestone-gated generation with a real-hardware check between milestones, and a deploy stage whose definition of done is the device visibly doing what you asked.
- **Hardware-validated.** The reference templates compile as-is, the bring-up self-tests for both toolchains have run on real boards, and the whole chain has been validated end-to-end on real Attaky hardware — from a fresh idea to confirmed on-device behavior.

## Quick start

1. Install on your platform of choice (see [Install](#install)).
2. Tell your assistant what you want:

> "I want my Attaky to be a pocket dice roller — shake it and two dice tumble on the screen."

3. The chain takes it from there: concept → your approval → spec → screens → code → build → flash → you confirm it works on the device.

## Install

One caveat applies everywhere: **single-skill copies must use the vendored builds** (`tools/build-dist.sh` output, published as release assets) — copying a folder straight out of `skills/` breaks its `../../shared/` links. Whole-repo installs keep those links working as-is.

- **Claude Code** — the repo is its own plugin marketplace: `/plugin marketplace add Attaky-Module/attaky-firmware-builder`, then `/plugin install attaky-firmware-builder@attaky`.
- **Codex** — install as a plugin: `codex plugin marketplace add Attaky-Module/attaky-firmware-builder` (or browse `/plugins` in-session); bundled skills load on install. Alternatively drop vendored skill folders from the release assets into `~/.agents/skills/`.
- **claude.ai** — download the per-skill ZIPs from the GitHub release assets (the `claude-ai/` variants carry claude.ai's shorter description limit) and upload via Settings → Capabilities → Skills, one ZIP per skill.
- **OpenCode** — clone the repo and add its `skills/` path to `opencode.json` under `skills.paths`; or drop vendored skill folders into `.claude/skills/` / `.agents/skills/` (auto-discovered). A `skills.urls` index (`opencode/index.json` in the release assets) is provided but experimental — remote-skill invocation has a known upstream bug.
- **Kilo Code** — clone the repo and add its `skills/` path to `kilo.jsonc` under `skills.paths`; or drop vendored skill folders into `.kilo/skills/` (compat dirs `.agents/skills/` and `.claude/skills/` also work).

## Status

Draft (v0.9.0).

- All seven skills written, with reference templates and hardware-validated bring-up self-tests for both toolchains, plus a fully implemented worked example (PlatformIO).
- Full chain validated end-to-end on real Attaky hardware: idea → concept → spec → UI → code → clean first build → flash → confirmed on-device behavior.
- Boot-time module detection and safe mode validated on real hardware, including the mismatch and force-boot paths (see `shared/module-detection-and-safe-boot.md`).
- Installable on Claude Code, Codex, claude.ai, OpenCode, and Kilo Code; marketplace submissions follow the public release.

## Support

- **This plugin / Attaky hardware** — Attaky [Discord](https://discord.attaky.com), or file an issue in this repository.

## License

Apache License 2.0 — see [`LICENSE`](LICENSE) for the full text and [`NOTICE`](NOTICE) for trademark and attribution requirements.

The Apache License grants you the right to use, modify, and redistribute the source. It does **not** grant a license to Attaky's trademarks (including the "Attaky" name, module names like Core / Expand / Power, and Complete Build / SKU names like Mesh Pocket / Retro Arcade / Agent Station). Derivative works must rename and remove Attaky-branded marks — see `NOTICE` for details.

Attaky-Firmware-Builder

File Explorer

# Use via CDN

Was this content helpful?

Recent Feedback

Download README