Authoring guide for Halo digital humans (automation apps). Read before calling create_automation_app or update_automation_app.
important!!! Must read and follow before writing or editing any code, and equally before planning, designing, or discussing architecture for this codebase (module placement, directory layout, IPC channels, theme, i18n) — decisions made while planning are what…
Halo's product design principles. Halo is a performance-sensitive Electron app — performance first, features restrained, never block startup or user interaction; the AI is a partner, not a tool; users never have to learn the tool; a working AI hears new…
Must be invoked when adding or changing a failure path (drop/skip/ignore/timeout/catch), a long-lived stateful link (connection, session, subscription, federation/sync link, IM channel), a log on a hot path (stream/IPC event handler, per-request or…
Must be invoked when the user asks to commit review.
How to report findings, diagnose behavior, and propose changes to the human owner of this repo. Load this before answering any question about why the product behaves a certain way, whether a feature should exist, what is broken, or what to change. The owner…
Work with Microsoft Word documents. Use whenever a .docx file is the input or the deliverable: reading or summarizing a Word document, creating a report/memo/letter/contract as a .docx, editing text in an existing .docx (find-and-replace, filling a template),…
Verify that the bundled Office library runtime (halo-node shim + pure-JS office libraries) is working. Use when the user asks to check or debug Office document capabilities, or when an Office skill fails with module-resolution errors.