القائمة
Launch the ADHD Copilot generative UI control plane (Vite + Svelte) and run the apprentice loop that turns the user's clicks into drafted Codex work. Use when the user wants the visual control plane, the dashboard, the UI, or to start ADHD Copilot.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Map a user's ADHD-aware focus system and create the first ADHD Copilot setup plan. Use when someone suspects ADHD, was diagnosed late, or wants an AI control plane across goals, bottlenecks, calendar, tasks, phone, computer, environment, and local memory.
Turn messy thoughts, notes, obligations, or inbox items into a trusted triage: do now, schedule, delegate, park, memory, or skill candidate.
Create a private ADHD Copilot daily focus brief from bounded calendar, email, document, project, or thread context. Use when the user wants help choosing what to do next, scheduling action, offloading open loops, or creating continuity memory.
Create an ADHD-friendly focus operating system across phone, computer, calendar, tasks, workspace, routines, and Codex apprentice workflows.
Convert bounded source material into a derived ADHD Copilot focus state store without retaining or republishing raw private content.
Synthesize daily focus briefs, action plans, or work logs into a weekly repair loop with repeated themes, completed actions, avoided actions, focus-system breakdowns, skill candidates, and one recommended bet for next week.
| name | adhd-copilot-console |
| description | Launch the ADHD Copilot generative UI control plane (Vite + Svelte) and run the apprentice loop that turns the user's clicks into drafted Codex work. Use when the user wants the visual control plane, the dashboard, the UI, or to start ADHD Copilot. |
This is the front door. The UI is a deterministic compiled Svelte app, not HTML you generate each session. Your job is to launch it and act as the apprentice that reacts to what the user captures — never to re-author the interface.
$HOME/.adhd-copilot/ single source of truth (created by the bridge plugin)
state.json current control-plane state (the handoff packet)
intents.log append-only: user actions awaiting you, one JSON per line
outbox/ where you write drafts; the UI shows them live
memory.md continuity memory (append only with approval)
A Vite plugin (vite-plugin-adhd-bridge.js) serves the app and exposes /api/* that
reads/writes those files. You only ever touch the files. Nothing leaves the machine.
npm install (first run only).npm run dev (defaults to http://localhost:7890,
data dir $HOME/.adhd-copilot; override with ADHD_COPILOT_DIR).ADHD Copilot connects to the user's real context by default, read-first:
Codex integrates with these natively, so keep it simple: start with Google Drive (everyone uses and shares with it); Notion can come later. Read freely to ground a draft; never write, send, or modify anything in these surfaces without explicit per-action approval. Surface a diff/preview in the Codex Channel first.
Watch $HOME/.adhd-copilot/intents.log for new lines (read it at the start of each turn,
or poll in the background). Each line is an intent:
{ "type": "setup_plan", "state": { ...full handoff packet... }, "ts": 0 }
{ "type": "apprentice", "module": "phone", "action": "Draft a per-app notification audit…", "state": { … } }
For each new intent:
state snapshot (goal, bottleneck, module decisions, open loops).setup_plan → run adhd-copilot-onboarding against the packet.apprentice → produce the specific module draft named in action.$HOME/.adhd-copilot/outbox/<slug>.md. The UI long-poll
surfaces it in the Codex Channel within ~1s. No need to message the file contents into chat.retention: don't write memory.md unless write_local_memory is true or the user
approves; never plan a network sync unless sync_to_teach_api is true.