touch-grass

Touch Grass

Translate the user's request into the bundled touch-grass CLI. Prefer the executable named touch-grass when it is on PATH. Otherwise run node <plugin-root>/bin/touch-grass.mjs, where <plugin-root> is the plugin directory containing this skill under skills/touch-grass/.

At the start of every Touch Grass interaction, run touch-grass welcome. It prints the first-use explanation only once. When it prints text, show that text before the requested outcome. When it prints nothing, continue normally.

Present welcome and settings output verbatim. Do not add companion names, rotation behavior, popup-delivery details, or other product facts to those introductions.

Do not edit ~/.touch-grass/config.json directly. The CLI validates and atomically saves changes.

The product vocabulary is intentionally human. Do not expose implementation labels such as idle reset, delivery, order, activeMs, state files, or raw configuration unless the user explicitly asks for developer diagnostics. When the user asks what they can change, run touch-grass settings and present its natural-language examples rather than a settings inventory.

Each reminder has its own schedule. Do not translate a reminder-specific request into one global interval.

Common requests:

• “Remind me to walk around every 40 minutes” → touch-grass reminders interval walk 40
• “Remind me to drink water every 45 minutes” → touch-grass reminders interval water 45
• “Move my snack reminders to 11 AM and 4 PM” → touch-grass reminders times snack 11:00,16:00
• “My bedtime is 11:30 PM; warn me 30 minutes before” → touch-grass reminders bedtime 23:30 --wind-down 30
• “Keep quiet from 10 PM to 8 AM” → touch-grass config set quiet-hours 22:00-08:00
• “Turn snack reminders off” → touch-grass reminders disable snack
• “Turn bedtime reminders back on” → touch-grass reminders enable bedtime
• “Add a breathing reminder every 45 minutes” → touch-grass reminders add breathing --title "Breathing break" --message "Take five slow breaths." --interval 45
• “Add a breathing reminder using this GIF” → the same command plus --gif "/absolute/path/breathe.gif". Only pass --gif when the user supplies an animation; without one the reminder shows both bundled companions.
• “Use my cat Juniper from this folder” → touch-grass companions add juniper --name "Juniper" --dir "/absolute/path"
• “Rotate my cats” → touch-grass companions use rotate
• “What can I customize?” → touch-grass settings
• “Pause reminders for 30 minutes” → touch-grass snooze 30
• “Don't use Nian” / “only show my own cat” → touch-grass companions remove nian (bundled cats are hidden, not deleted)
• “Bring Nian back” → touch-grass companions use nian, or touch-grass companions add nian with no --dir. A hidden bundled cat is never gone; do not ask the user for animation files to restore one.

When the user says reminders have stopped, are not appearing, or seem broken, run touch-grass doctor first. If popupReady is false, tell them the reminder companion is not running and to open “Touch Grass.app”. If helperVersionMatches is false, tell them the companion is an older build and needs rebuilding with npm run install:macos-helper. Do not guess at causes before running it.

When the user does not dictate the exact banner wording, write --title and --message yourself in the voice of the built-in reminders: a short plain title, then one warm sentence that says what to do. Read presets.json for the house voice rather than inventing a new one, and keep the user's own words when they supplied them.

For a companion folder, require animated .gif or .webp files named water, stretch, snack, walk, eyes, and bedtime. Those six cover every reminder: the bedtime animation serves both the wind-down and bedtime stages, and the snack animation covers lunch and dinner unless the folder also has lunch and dinner files of its own. Do not invent asset paths; inspect the supplied folder first when needed.