Twenty steps. Prompts collapsed. Her Team window first.

Two things, as complete as you can, in my original language, no preamble:
1. Everything you remember about me and my work: who I am, my company and role, people and who they are to me, clients and suppliers, preferences, how I like answers, recurring tasks, ongoing projects. Grouped bullets, small details included.
2. How I use you: the kinds of tasks (most frequent first), the format and tone I prefer, things I keep correcting, instructions I repeat, processes I walk you through step by step, and weekly or monthly tasks I could hand to an assistant.

I'm archiving this project. For each chat title below, find it with past-chat search and write: title and date; 2-4 lines on what it was about and the outcome; decisions, with reasons; facts about my business, people, clients, prices, dates; anything still open. If you can't find one, write "NOT FOUND: <title>". Keep my original language. No preamble. End with "COVERED x of y".

Titles:

{{PASTE UP TO 15 ★ TITLES}}

Next, same format:

{{PASTE THE NEXT TITLES}}

Package my skill "{{SKILL NAME}}" as a zip file, exactly as it is. If you can't create files, print SKILL.md and every other file in the skill in full, each in a code block headed with its path.

Read {{KIT PATH, e.g. ~/Downloads/workspace-setup}}/MAC_PLAYBOOK.md and keep it as your instructions for this whole session. You are the Mac role in a Claude account migration. When I type "job N", do job N exactly as written and report in the format it asks for. Don't start any job until I ask. Confirm when you've read it, in one line.

Without guessing: summarise this project's instructions in 3 bullets, list the files you can see, and give the 3 most important facts in this project's knowledge.

Answer each question from this project's knowledge and your memory. If you don't know, write "not known". Don't guess. One line per answer, same numbering.

{{PASTE THE QUIZ BLOCK FROM load/}}

Test each connector without sending, deleting or changing anything. Gmail: find my last email from {{A KNOWN CONTACT}} and create a one-line reply as a DRAFT. Calendar: list tomorrow's events. Drive: find the folder "Company" and list its files. monday.com: list my workspaces and boards and the 3 most recently updated items. Report each as OK or FAILED with the reason.

Using monday.com, create three new boards. Ask me which workspace first, and don't touch any existing board.
1. "Agent Desk": From (dropdown: {{DEPARTMENTS}}), To (same), Status (New, Working, Done, Blocked, Needs founder), Due (date). Handoff text goes in each item's update.
2. "Company Ledger": Owner (dropdown: {{DEPARTMENTS}}, {{HER NAME}}), Status (open, waiting on {{HER NAME}}, waiting external, blocked, done), Priority (Urgent, Normal), Due (date), Next action (text).
3. "Job Runs": Job (text), Ran at (date and time), Result (OK, Nothing needed, FAILED), Note (text).
Show me what you created, with links.

You are the {{DEPARTMENT}} agent of {{COMPANY}}. Before any task, read ORG.md, RULES.md and departments/{{department}}/AGENT.md from this project's files, then check the monday.com board "Agent Desk" for items with To = {{DEPARTMENT}} and Status = New. ORG.md's rules override everything: nothing is sent outside the company, bought or deleted without {{HER NAME}}'s explicit yes; draft instead. When you finish something, update its board item and say exactly what you changed; "done" means you saw it work. When {{HER NAME}} corrects you, propose a one-line rule for RULES.md → Lessons. Answer decision first, then only what's needed to act.

{{A REAL REQUEST THAT NEEDS TWO DEPARTMENTS, e.g. "A new client just signed. Make sure they get invoiced and receive a welcome email."}} Route it per ORG.md: create the handoffs on the Agent Desk, add a Company Ledger line, and tell me exactly what you created.

Check the Agent Desk for items with To = {{DEPARTMENT}} and Status = New. Take the oldest, set it to Working, do it (drafts only), then set it to Done or Needs founder with a one-line result.

Morning brief for {{HER NAME}}. Use the briefs skill, following ORG.md and RULES.md in the Drive folder Company. Sources: today's Google Calendar, Gmail since yesterday 18:00, the monday.com boards Company Ledger, Agent Desk and Job Runs. Change nothing except one row in Job Runs (Job: Morning brief; Result: OK or FAILED with the reason). If a source can't be reached, say so first.

Inbox triage. Use the inbox-triage and brand-voice skills, following ORG.md and RULES.md in the Drive folder Company. Read Gmail since the last run (the last 2 hours if unsure). Drafts only: never send, archive or delete. Real actions become Agent Desk items for the right department. Add one Job Runs row (Job: Inbox triage; Result: OK, Nothing needed or FAILED; Note: counts). If nothing needed attention, say "checked N, nothing needed".

Meeting prep. Use the meeting-to-actions skill in prep mode for each of today's meetings with people outside the company: Google Calendar, Gmail history, PEOPLE.md in the Drive folder Company, and the Company Ledger. Change nothing except one Job Runs row (Job: Meeting prep).

Weekly review for {{HER NAME}}. Use the briefs skill: Company Ledger, Agent Desk, Job Runs and Gmail from the past 7 days. Change nothing except one Job Runs row (Job: Weekly review).

Watchdog. In the monday.com board Job Runs, check today's rows. Expected: Morning brief 1, Meeting prep 1, Inbox triage {{N}}, Weekly review 1 on Sundays. For each missing or FAILED job, create a Company Ledger item (Owner: Chief of Staff; Priority: Urgent; Next action: check why <job> didn't run). Add a Job Runs row (Job: Watchdog). If everything ran, say "all jobs ran" with the counts.

Use Gmail to read my last 40 sent emails (skip one-word replies and forwards). Fill in the attached brand-voice skill template from them: how I write, real phrases I use, what I never say, typical length, greeting and sign-off, and 3-5 short real examples, one per kind of email. Then ask me for the brand colors, fonts and where the logo is. Give me the finished SKILL.md as a downloadable file.

Use the skill-creator skill. Build a skill for this recurring task of mine: {{PASTE THE TOP ITEM FROM map/SKILL-CANDIDATES.md}}. Interview me briefly, write it, then test it on a real example of mine.

Use the sop-builder skill. I'll explain how I do {{PROCESS}}. Turn it into an SOP, save it in Drive Company/SOPs, and add it to SOPs/INDEX.md.

The setup is finished. Notes: {{what surprised you, what took longest, what was skipped}}. Fill the minutes per part in SETUP_LOG.md, fold every lesson into templates/workspace-setup/ (sheet, prompts, playbook, checklist, README), and list what to fix in the kit before the next setup.