Practical Aether Workshop workflows for first prototypes, classroom demos, AI-assisted components, and cloud library maintenance.
Workflow 1: Light-Reactive Output
Section titled “Workflow 1: Light-Reactive Output”Use this for a first classroom or maker demo.
- Create a new project.
- Add Light Sense.
- Add
if. - Add RGB LED or LED Ring Act.
- Connect
Start -> Light -> if -> Act. - Assign ports.
- Verify code.
- Upload and tune the threshold.
Best practice: keep the first graph small and commit a project change log after hardware works.
Workflow 2: Custom Sensor Component
Section titled “Workflow 2: Custom Sensor Component”Use this when a sensor is not in the default library.
- Open Library.
- Create a new Sense component.
- Add pin requirements and compatible ports.
- Add external or source library dependencies.
- Write read code blocks.
- Add notes and AI profile.
- Test in a project.
- Commit component history.
- Push the library if it is cloud-linked.
Best practice: include a minimal example graph in project notes or team docs.
Workflow 3: Reusable Capsule Pattern
Section titled “Workflow 3: Reusable Capsule Pattern”Use this for repeated behavior.
- Build the behavior in a normal project graph.
- Move the repeated logic into a Capsule.
- Expose input/output interface ports.
- Convert fixed values into parameters.
- Test the Capsule as a project node.
- Commit Capsule history.
Best practice: keep Capsule interfaces stable after teammates start using them.
Workflow 4: AI-Assisted Project Draft
Section titled “Workflow 4: AI-Assisted Project Draft”Use this when exploring an idea quickly.
- Configure AI provider settings.
- Describe the desired behavior in Project AI.
- Mention known components with
@. - Review staged graph edits.
- Keep the graph only after checking node choices.
- Assign hardware, verify, and upload manually.
Best practice: ask AI for a small first graph before asking for a complete installation.
Workflow 5: Cloud Library Release
Section titled “Workflow 5: Cloud Library Release”Use this when publishing shared components or Capsules.
- Pull remote updates.
- Resolve local drafts.
- Commit each changed component/Capsule.
- Write a library structure commit message.
- Push.
- Invite Viewers or Editors as needed.
Best practice: use Viewer role for classrooms and Editor role only for maintainers.