Start with a task, not a blank chat.
These templates show how to give HeyCC a concrete job, keep the user in control, and inspect the deliverable. Features vary by platform, version, selected model service, permission and configuration.
Voice note → action planSeparate decisions, actions and open questions before saving anything.
Calendar and RemindersRead first, propose a change, then approve the final write.
Web research → cited fileKeep source links beside claims and mark uncertainty.
Create a Markdown or PDF documentApprove the outline, check the file, and avoid unsupported Office claims.
Multi-bot project teamGive research, drafting and review separate responsibilities.
Work and life botsUse different roles and rules without treating a bot name as a security boundary.
Python and shell tasksInspect the sandbox first and treat Python availability as conditional.
HTML slides, reports and CSVName the real output format and inspect every file.
Recurring AI tasksDefine timezone, missed-run behavior, notifications and a stop rule.
Model choice and permissionsSeparate provider configuration, billing, HeyCC rules and Apple permission.
App data and iCloud syncKeep local storage, selective sync and model requests distinct.
Apple Watch and widgetUse companion entry points without assuming full iPhone parity.
How to use the library
Copy the structure
Replace the bracketed task details, then review the model, permissions, destination and output format before running it.
Inspect the result
A fluent answer is not proof. Open saved files, verify Apple system changes, and check sources before relying on the output.