31 lines
2.1 KiB
Markdown
31 lines
2.1 KiB
Markdown
---
|
|
title: "Scratchpad"
|
|
description: "Personal notes and ideas — postcards pipeline, Veo gate transitions, remote terminal proxy, asset registry"
|
|
type: design
|
|
status: draft
|
|
---
|
|
|
|
# Scratchpad
|
|
|
|
Personal notes and random thoughts. Not acted upon unless explicitly instructed.
|
|
|
|
---
|
|
|
|
- Pipeline to create postcards for each world — visuals for in-game dossiers
|
|
- Investigate using Veo to create gate transition movies — based on planetary profiles, postcards, and game visual style
|
|
- Capture discussion with Gemini about setting up a 3D to 2D pipeline
|
|
- Improve asset generation pipeline: proper asset registry, status tracking per asset, prompt storage/versioning, pre-sprint prompt preparation pass to maintain visual/audio cohesion across batches
|
|
- Remote terminal proxy for Claude Code — mobile notification + interaction bridge for monitoring progress away from desk. Full feature scope:
|
|
- Capture permission prompts across all terminals/worktrees in a project
|
|
- Push notifications to phone (Ntfy/Gotify/Pushover/custom — self-hostable)
|
|
- Summary of last assistant message for context (what Claude is doing and why it's asking)
|
|
- Support AskUserQuestion mode: render multiple-choice options, free-text input
|
|
- Support permission approve/deny with the tool call details
|
|
- Basically a full terminal proxy that adapts to Claude Code's interactive elements
|
|
- Starting point: peon-ping already hooks into the right events (PermissionRequest, Notification, Stop, etc.) via ~/.claude/hooks/
|
|
- Hook event JSON includes: hook_event_name, notification_type, session_id, cwd, permission_mode
|
|
- Gap: hook event data may not include prompt content (tool call details, AskUser question text, multiple choice options) — investigate what's in the full event payload
|
|
- Architecture: extend peon-ping's send_notification pattern to push to a remote service, add a response channel back to the terminal
|
|
- NPC-to-NPC conversations should be informed by contextual world state: weather changes, local news, local economics, inter-system news, inter-system economics. Also idle chit-chat about personal preferences like favorite brands and colors
|
|
|