Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
111 commits
Select commit Hold shift + click to select a range
031b2e9
feat(cad): Add Screw Tolerance Test and update docs #29
jamro Sep 17, 2026
aae2fe2
feat(firmware): add an optional kaomoji expression library (#37)
AndreLYL Sep 17, 2026
1497f1a
feat(firmware): integrate kaomoji eyes into animations via eyes_style…
jamro Sep 17, 2026
7694193
feat(cad): Prepare models for external 3D printing with PCBWay #40
jamro Sep 18, 2026
c45b281
fix(cad): add missing bell mount hole
jamro Sep 18, 2026
a537d8f
feat(cad): update 3D model for Neck to make assembly orientation easier
jamro Sep 19, 2026
804529a
docs: add measured M2 screw list and shopping list (sg90) (#41, #15)
mjspe Sep 19, 2026
c5bc77d
feat: add mechanical assembly guide (#44, #16)
jamro Sep 19, 2026
e24cb0d
docs: enhance docs
jamro Sep 19, 2026
fdcb5a7
fix(cad): Tighten the S90 servo mount #43
jamro Sep 19, 2026
4730562
fix(cad): Move lamp base opening to better align with ESP32 LED #42
jamro Sep 20, 2026
ab3b9eb
feat: enhance parts exporter functionality by input parmams
jamro Sep 20, 2026
33ac5ee
feat(firmware): implement servo PWM switch off mechanism and enhance …
jamro Sep 20, 2026
280c857
fix(firmware): start sleep-inertia OLED at wakeup t=0
jamro Sep 20, 2026
57ed328
feat(anim): implement dead state with audio feedback and update relat…
jamro Sep 20, 2026
92bca3d
feat(pcb): add compact-carrier-board for ESP32-C3-Zero (#32)
jtruland Sep 21, 2026
44122c0
feat(pcb): add main-control-board MVP (#35)
jamro Sep 21, 2026
1143b01
docs: update CAD and integration documentation with new parts and wor…
jamro Sep 26, 2026
2682979
doc: add missing links to main readme
jamro Sep 26, 2026
ecea0fe
feat(firmware): introduce 'cover' eye style for OLED display
jamro Sep 27, 2026
aa2d0ac
docs: add information about upcoming assembled Main Board in README
jamro Sep 27, 2026
cd5480a
docs: update contribution guidelines to include new 'mods' scope for …
jamro Sep 27, 2026
5cbdede
chore: remove unused audio files from the project
jamro Sep 28, 2026
16cc7e7
docs: add README for assets including audio clips and logo details
jamro Sep 28, 2026
694ad25
feat(anim): add 'dots' eye style for OLED display
jamro Sep 28, 2026
842c5c2
feat(anim): extend sleep nod-off animation for eye display.
jamro Sep 28, 2026
8975e63
fix(integrations): skip cursor hooks with empty conversation or gener…
jamro Sep 28, 2026
2741738
feat(cad): add a parametric bottom cover and chair mounts (#49)
Hilo-Hilo Sep 29, 2026
b834339
refctor(cad): simplify bottom cover design
jamro Sep 29, 2026
fe90f1c
docs: enhance contribution guidelines and README
jamro Sep 29, 2026
23ea9c7
feat(mods): add hallowing pumpkin head example (#51)
jamro Oct 1, 2026
759187d
update halloween mod preview
jamro Oct 1, 2026
18df470
fix(mod): remove duplicated f3d halloween model
jamro Oct 1, 2026
d71eb42
fix(cad): Keyboard keys may not extrude after increasing servo size #31
jamro Oct 2, 2026
2621994
feat(firmware): add over-the-air firmware and filesystem updates (#55)
Mechazawa Oct 4, 2026
dd0ebbd
feat(firmware): bake firmware version into the build
jamro Oct 4, 2026
8b1744b
chore(ci): store binaries as CI/CD artifacts
jamro Oct 4, 2026
8f53afa
chore(ci): add bootloader and partitions to build artifacts
jamro Oct 4, 2026
82c7709
feat(web): implement web-based firmware flashing and UI enhancements
jamro Oct 4, 2026
107b601
feat(web): enhance firmware flashing UI and update manifest handling
jamro Oct 4, 2026
3cbcacd
feat(web): implement flash catalog generation and update deployment w…
jamro Oct 4, 2026
0d19f4c
docs: update flashing instructions and enhance web flash integration
jamro Oct 4, 2026
324c185
docs: add information about new main control board and interest check
jamro Oct 4, 2026
268ad4b
feat(pcb): design integrated PCB for Tiny Engineer electronics (#46, …
jamro Oct 5, 2026
f8bbe75
doc: update main readme
jamro Oct 5, 2026
dd0ca0f
feat(pcb): update component properties and add missing attributes
jamro Oct 5, 2026
e7a4950
chore(pcb): update .gitignore to exclude production directory patterns
jamro Oct 5, 2026
a3ffa52
fix(cad): mark polarization of LEDs in silkscreen
jamro Oct 5, 2026
ec87ad7
feat(http): stream a WAV over POST /play while the robot talks (#57)
Mechazawa Oct 6, 2026
ecb1d10
refactor(http): serve web UI from LittleFS, bundled with Vite (#60)
Mechazawa Oct 8, 2026
c718397
feat(integrations): tiny engineer client CLI (#71)
jamro Oct 8, 2026
ef5dbb3
fix(firmware): turn off green LED after wifi connect
jamro Oct 10, 2026
562dd53
fix(integrations): replace Node.js command with portable shell script…
jamro Oct 10, 2026
611b554
feat(animation): add audio-reactive talking animation and related aud…
jamro Oct 10, 2026
c7afe96
refactor(http): build the web UI with Vite and embed it gzipped in th…
Mechazawa Oct 11, 2026
80949ac
feat(wifi): advertise the setup AP as a captive portal over DHCP (#76)
Mechazawa Oct 11, 2026
22afc31
feat(cad): support of EMAX ES-9051 servos (#70)
jamro Oct 12, 2026
7460d31
fix(docs): include breakout photo in assembly guide
jamro Oct 12, 2026
0157b19
feat(settings)!: store up to five wifi networks (#75)
Mechazawa Oct 12, 2026
738d8d6
refactor(http): rewrite the web UI in TypeScript and Preact, clean up…
Mechazawa Oct 13, 2026
a04653c
refactor(hardware): enhance haltWithRgbCode to always include reason …
jamro Oct 16, 2026
65dabc2
fix(settings): improve handling of missing NVS keys and namespace ini…
jamro Oct 16, 2026
8821a07
docs(flash): clarify requirements for flashing ESP32-C3-Zero and upda…
jamro Oct 16, 2026
dbbcc30
feat(integrations): add USB serial control and connection mode (#73, …
jamro Oct 17, 2026
3c9c854
chore(integrations): release tiny-engineer 0.2.0
jamro Oct 17, 2026
29f0e33
feat(firmware): guided-servo-calibration (#84)
jamro Oct 18, 2026
b0fcb06
docs(firmware): update main specs with usb serial communication and g…
jamro Oct 18, 2026
db9a5a0
feat(servos): park before upload and restore last pose
jamro Oct 18, 2026
f03e6ae
refactor(ui): enhance StatusBar component with dismiss button and imp…
jamro Oct 18, 2026
8292162
docs(cad): add detailed instructions for printing the LampDiffuser wi…
jamro Oct 18, 2026
e52d798
feat(cli): add version command to print package version
jamro Oct 19, 2026
1d64aa9
feat(cli): store user-level config shared between projects
jamro Oct 19, 2026
261adc2
chore(cli): release tiny-engineer CLI 0.3.0
jamro Oct 19, 2026
c56eb5a
fix(cad): add a flexible belly joint to unload the torso servo shaft …
jamro Oct 21, 2026
7c04f88
refactor(firmware): remove servo_hold setting and related references
jamro Oct 22, 2026
8f0da46
fix(footer): update footer link to point to the new website tinyengin…
jamro Oct 22, 2026
eabb3b9
feat(pcb): main control board rev3 (#66, #62)
jamro Oct 22, 2026
31edbd0
feat(pcb): add HTML redirect page for Tiny Engineer PCB rev3
jamro Oct 23, 2026
7b32626
feat(pcb): update main control board design with new silkscreen graph…
jamro Oct 23, 2026
6e34ea4
feat(cursor): add new hooks for execution events and failure handling
jamro Oct 24, 2026
ab5515a
refactor(cursor): update postToolUseFailure handling to avoid false p…
jamro Oct 24, 2026
5bf2730
feat(web): enhance landing page content and structure
jamro Oct 24, 2026
218b4fd
feat(cad): add printable laptop screen inserts and generator (#88)
jtruland Oct 27, 2026
4cf5de3
fix(web): prevent Object URL memory leaks in laptop screen generator …
Abhishek-Jalkhare Oct 28, 2026
f391a6d
fix(web): handle image loading failures in laptop screen generator (#98)
ShryukGrandhi Oct 30, 2026
6e39294
feat(firmware): add PCBA test environment and documentation (#99)
jamro Nov 1, 2026
aefc852
fix(firmware): update I2S configuration and tone generation parameter…
jamro Nov 1, 2026
2c86cb6
feat(web): document web assembly (#101)
nntin-bot Nov 5, 2026
2513083
refactor(web): simplify web assembly viewer (#103)
jamro Nov 6, 2026
4e2ebf6
feat(web): add guided build (#104)
jamro Nov 8, 2026
5c2a32a
fix(ci): update caching key and refine environment setup for KiCad Ap…
jamro Nov 8, 2026
c085c2e
feat(firmware,cli): push button extension (#90)
jamro Nov 8, 2026
3f6a69a
chore: add .cache to .gitignore to exclude cache files from version c…
jamro Nov 8, 2026
a39ff51
feat(ci): inject Clarity tracking script into HTML files
jamro Nov 8, 2026
9d5cf32
feat(web): enhance thumbnail rendering with device pixel ratio adjust…
jamro Nov 8, 2026
10e887d
fix(cli): enhance daemon status reporting and improve serial connecti…
jamro Nov 9, 2026
93fb444
feat(firmware): enhance wakeup behavior and state management
jamro Nov 9, 2026
dea343e
chore(cli): bump version to 0.4.0 in package.json and package-lock.json
jamro Nov 9, 2026
e690532
chore(cli): bump version to 0.4.1 and update README with new daemon c…
jamro Nov 9, 2026
12db6bc
feat(actions): implement on-device event-action bindings
jamro Nov 9, 2026
45da17c
docs(mod): update assembly and README to include new action rules for…
jamro Nov 9, 2026
a86b810
feat(web): enhance landing page and styling for customise tile hub
jamro Nov 11, 2026
567fcc8
feat(ci): inject Umami tracking script into HTML files
jamro Nov 12, 2026
d37f5b1
feat(firmware): kawaii eyes (#109)
blakelton Nov 15, 2026
3beabf4
docs: sync docs of on-device Actions management for event-triggered …
jamro Nov 15, 2026
a156934
feat(web): add eye styles gallery and integrate into customise hub
jamro Nov 15, 2026
e901f3c
refactor(web): simplify shop section of assembly guide
jamro Nov 15, 2026
baf5d04
fix(firmware): I2C fault recovery upstream (#111)
blakelton Nov 17, 2026
b2ca081
servos: map SERVO_SPECS channels to the harness as actually wired
jtruland Sep 20, 2026
6e0c037
servos: default ranges to this robot's measured calibration
jtruland Sep 20, 2026
13a5091
Merge fork main into bitz-fw-2026-11-17
jtruland Nov 17, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
8 changes: 4 additions & 4 deletions .agents/hooks.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"tiny-engineer": {
"PreInvocation": [
{
"command": "tiny-engineer-antigravity PreInvocation",
"command": "node packages/tiny-engineer-cli/bin/tiny-engineer.js hook antigravity PreInvocation",
"timeout": 3
}
],
Expand All @@ -11,7 +11,7 @@
"matcher": "*",
"hooks": [
{
"command": "tiny-engineer-antigravity PreToolUse",
"command": "node packages/tiny-engineer-cli/bin/tiny-engineer.js hook antigravity PreToolUse",
"timeout": 3
}
]
Expand All @@ -22,15 +22,15 @@
"matcher": "*",
"hooks": [
{
"command": "tiny-engineer-antigravity PostToolUse",
"command": "node packages/tiny-engineer-cli/bin/tiny-engineer.js hook antigravity PostToolUse",
"timeout": 3
}
]
}
],
"Stop": [
{
"command": "tiny-engineer-antigravity Stop",
"command": "node packages/tiny-engineer-cli/bin/tiny-engineer.js hook antigravity Stop",
"timeout": 3
}
]
Expand Down
202 changes: 202 additions & 0 deletions .claude/commands/opsx/apply.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,202 @@
---
name: "OPSX: Apply"
description: "Implement tasks from an OpenSpec change (Experimental)"
allowed-tools: Bash(openspec:*)
category: "Workflow"
tags: ["workflow", "artifacts", "experimental"]
---

Implement tasks from an OpenSpec change.

**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `schemas`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.

**Project check:** These steps expect a project that already uses OpenSpec. Before the first step that writes anything (`new change`, `archive`, `sync specs`, or authoring an artifact file), confirm the project has a root: run `openspec list --json` (with `--store <id>` when a store is selected, since the store is then the root) and read `root`. A root object means the project is set up. `"root": null` means it is not - there is no `openspec/` directory here, and a write such as `openspec new change` would create one as a side effect. The command also exits non-zero, which is that answer rather than a broken CLI, so read the JSON instead of retrying or working around it.

One `"root": null` is not about setup: when a `status` error message starts with `Declared in` or `Invalid store declaration in` and names this project's `openspec/config.yaml` (or `config.yml`), the project does use OpenSpec through a store it declares, which this machine cannot resolve (the store is not registered, or the `store:` line is malformed). Do not treat it as uninitialized and skip the branches below: stop before writing and show the user that error's `message` and `fix`.

Otherwise, with no root, what happens next depends on how this workflow was reached:

- **Auto-selected**: you chose this workflow yourself, without the user naming OpenSpec, naming this skill, or running its slash command. Stop using OpenSpec and answer the request normally, as you would with no OpenSpec installed. Do not ask them to set anything up and do not mention OpenSpec setup.
- **Explicit OpenSpec request**: the user named OpenSpec, named this skill, or ran its slash command. Stop before writing and ask how to proceed: set this project up (`openspec init`), target a store they already have (`--store <id>`), or continue without OpenSpec for this request. Wait for their answer.

In both branches, never create the root as a side effect: do not run `openspec init` until the user asks for it, do not hand-create `openspec/` files, and do not let a command create it.

**Input**: Optionally specify a change name (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

**Steps**

1. **Select the change**

If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run `openspec list --json` to get available changes and ask the user to select one

Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).

2. **Check status to understand the schema**
```bash
openspec status --change "<name>" --json
```
Parse the JSON to understand:
- `schemaName`: The workflow being used (e.g., "spec-driven")
- `planningHome`, `changeRoot`, and `actionContext`: planning scope and edit constraints
- Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)

3. **Get apply instructions**

```bash
openspec instructions apply --change "<name>" --json
```

This returns:
- `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
- Progress (total, complete, remaining)
- Task list with status, source path, and source line
- Dynamic instruction based on current state
- Optional `context`: current required project instruction input from the selected root
- Optional `operationGuidance`: current advisory guidance for apply
- `missingArtifacts` (when present): required artifact ids with no output

**Handle states:**
- If `state: "blocked"`: show the message and pause implementation.
- If `missingArtifacts` is non-empty: suggest completing the missing artifacts. Run `openspec status --change "<name>" --json`, select the next `ready` artifact (not `skipped` or `blocked`), and use `openspec instructions "<artifact-id>" --change "<name>" --json` for its rules and template. Keep the selected `--store <id>` on both commands.
- Otherwise, follow the CLI instruction to create or repair the schema-configured tracking file from existing planning artifacts. Do not assume another artifact is ready or start implementation while blocked.
- If `state: "all_done"`: report that all tracked tasks are complete and suggest review or verification as appropriate before archiving
- Otherwise: proceed to implementation

Treat `context` as a required prompt-level input. Read and consider it, and
apply relevant project facts, conventions, and constraints while implementing.
Treat `operationGuidance` as optional additive advice. Read and consider every
entry, and follow entries that are applicable and compatible with the built-in
workflow.

Keep both fields separate from CLI-returned state, missing artifacts, tasks,
progress, `contextFiles`, and the built-in `instruction`. They are not
evidence of task completion, do not replace the built-in instruction, and do
not permit bypassing a blocked state. If context conflicts with the built-in
instruction, an explicit user choice, or a CLI-controlled value, report the
conflict and preserve the controlling value. If guidance is inapplicable or
conflicts with those controlling inputs, do not follow it and explain why.
These are prompt-level behavior contracts, not enforceable checks.

4. **Read context files**

Read every file path listed under `contextFiles` from the apply instructions output.
The files depend on the schema being used:
- **spec-driven**: proposal, specs, design, tasks
- Other schemas: follow the contextFiles from CLI output

Do not copy `context` or `operationGuidance` verbatim into implementation
files or planning artifacts unless the user separately asks for that content.

5. **Show current progress**

Display:
- Schema being used
- Progress: "N/M tasks complete"
- Remaining tasks overview
- Dynamic instruction from CLI

6. **Implement tasks (loop until done or blocked)**

For each pending task:
- Show which task is being worked on
- Make the code changes required
- Keep changes minimal and focused
- Before editing, confirm the checkbox at the returned `sourcePath` and `line` still matches the task description; if it does not, rerun the apply instructions and use the refreshed location
- Mark the task complete at its returned `sourcePath` and `line`: `- [ ]` → `- [x]`
- Rerun the apply instructions and confirm that task is now done and progress changed
- Continue to next task

**Pause if:**
- Task is unclear → ask for clarification
- Implementation reveals a design issue → suggest updating artifacts
- A task needs work beyond what the spec and tasks describe, or you are tempted to drop, narrow, defer, or accept exceptions to specified behavior to make it fit → surface the added scope and ask; do not absorb it silently
- Error or blocker encountered → report and wait for guidance
- User interrupts

7. **On completion or pause, show status**

Display:
- Tasks completed this session
- Overall progress: "N/M tasks complete"
- If all done: report that tracked tasks are complete and suggest review or verification as appropriate before archiving
- If paused: explain why and wait for guidance

**Output During Implementation**

```
## Implementing: <change-name> (schema: <schema-name>)
Working on task 3/7: <task description>
[...implementation happening...]
✓ Task complete
Working on task 4/7: <task description>
[...implementation happening...]
✓ Task complete
```

**Output On Completion**

```
## Implementation Complete
**Change:** <change-name>
**Schema:** <schema-name>
**Progress:** 7/7 tasks complete ✓
### Completed This Session
- [x] Task 1
- [x] Task 2
...
All tracked tasks are complete. Review or verify the change as appropriate
before archiving. You can archive this change with `/opsx:archive`.
```

**Output On Pause (Issue Encountered)**

```
## Implementation Paused
**Change:** <change-name>
**Schema:** <schema-name>
**Progress:** 4/7 tasks complete
### Issue Encountered
<description of the issue>
**Options:**
1. <option 1>
2. <option 2>
3. Other approach
What would you like to do?
```

**Guardrails**
- Keep going through tasks until done or blocked
- Always read context files before starting (from the apply instructions output)
- If task is ambiguous, pause and ask before implementing
- If implementation reveals issues, pause and suggest artifact updates
- Keep code changes minimal and scoped to each task
- Update task checkbox immediately after completing each task
- Pause on errors, blockers, or unclear requirements - don't guess
- When a task needs work beyond what the spec describes, surface the added scope and pause - never silently narrow, defer, or simplify away specified behavior
- Only mark a task `- [x]` when its specified behavior is fully implemented, not when it is partially done or deferred
- Use contextFiles from CLI output, don't assume specific file names
- Use each task's sourcePath and line to update its exact checkbox
- Do not use context or operation guidance as proof that a task is complete
- Apply relevant project context; report conflicts with controlling workflow inputs
- Consider every guidance entry; explain any inapplicable or conflicting advice
- Do not copy runtime context or operation guidance into implementation files or planning artifacts
- Preserve CLI-controlled blocked/ready/all-done behavior and completion criteria

**Fluid Workflow Integration**

This skill supports the "actions on a change" model:

- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
Loading
Loading