Home / Ops / More in this area

Sol's Claude Desktop Setup (v1, 2026-07-09)

Updated Jul 09, 2026 · Affirmology_SolClaudeDesktop_Setup_v1.md

Sol's Claude Desktop Setup (v1, 2026-07-09)

Gets Sol's Claude Desktop (chat only, older Mac, Pro plan) fully wired into Affirmology: reading the shared project knowledge, holding the right rules, and able to send work back to Jeff and the system.

IMPORTANT CONTEXT FIRST: Sol's Claude tried to clone github.com/jeffparkerlove22/jpl-knowledge and hit an auth wall. That repo was PLANNED in Affirmology_StudioDeploy_Runbook_v1.md but the onboarding doc says "repo link to come once it's created," so it almost certainly does not exist yet. Nothing is broken. Part A creates it. Do NOT make it public; the GitHub invite + Claude's GitHub connector handle private access cleanly.

The repo contents are already staged and safety-checked at AFFIRMOLOGY/jpl-knowledge/ (curated per the runbook: craft, plan, system, Sol's lane, a from-sol outbox, a README that is Knowledge Pack v2, a .gitignore safety net; the runbook's equity/ownership grep ran clean). One deliberate call: Affirmology_BusinessPlan_v5.docx is NOT in the repo because it contains ownership and pool material and Colin will likely get this same repo later. Share the business plan with Sol directly by email instead.

PART A: Jeff does this first (about 10 minutes)

Step 1. Check whether the repo already exists. Open this in your logged-in browser: https://github.com/jeffparkerlove22/jpl-knowledge . If it 404s, it was never created (expected).

Step 2. Create and push it. EITHER paste this into Terminal:

cd "/Users/jeffreyparker/CLAUDE/AFFIRMOLOGY/jpl-knowledge"
git init
git branch -M main
git add -A
git commit -m "Knowledge pack v2: initial curated share for Sol"
gh repo create jpl-knowledge --private --source . --push

(If gh is not installed or not logged in, run brew install gh then gh auth login first. If the repo already existed in step 1, replace the last line with git remote add origin https://github.com/jeffparkerlove22/jpl-knowledge.git then git push -u origin main.)

OR paste this into a Claude Code window opened in the AFFIRMOLOGY folder:

In /Users/jeffreyparker/CLAUDE/AFFIRMOLOGY/jpl-knowledge: init a git repo on branch main and commit everything as "Knowledge pack v2: initial curated share for Sol". Check if the private repo jeffparkerlove22/jpl-knowledge exists; create it PRIVATE if not; push. Before pushing, re-run the safety grep from Affirmology_StudioDeploy_Runbook_v1.md (section "The knowledge repo for Sol and Colin") over the staged files and show me the result. Never add any Agreement, TermSheet, Equity, CapTable, or APIKeys files. Show me the repo URL when done.

Step 3. Invite Sol. On github.com open the repo, then Settings, then Collaborators, then "Add people," and enter Sol's GitHub username or her email solballard@gmail.com. Give her Write access (so she can upload into from-sol). If she has no GitHub account yet, she creates a free one first at github.com/signup (Part B step 1).

Step 4. Email Sol the Part B section below (copy it into an email or send her this doc) plus Affirmology_BusinessPlan_v5.docx attached separately if you want her to have it.

PART B: Sol does this (about 20 minutes, one time)

Hi Sol. This sets up your Claude so it knows the whole project, follows our rules, and can send your work back to us. Chat-only Claude is all you need; none of this requires the heavy desktop features.

1. GitHub account and invite

1. If you do not have a GitHub account: go to github.com/signup and create one with solballard@gmail.com.
2. Watch for the email inviting you to "jpl-knowledge." Click the green Accept button.
3. Bookmark the repo: https://github.com/jeffparkerlove22/jpl-knowledge . This is our shared project brain. You can open any file right in the browser.

2. Get the project files onto your Mac

1. On the repo page, click the green "Code" button, then "Download ZIP."
2. Unzip it and move the folder to Documents. Rename it "Affirmology" if you like.
3. Every week or two (or when Jeff says "I pushed updates"), download the ZIP again and replace the folder. That keeps you current.

3. Create your Affirmology Project in Claude

1. Open Claude Desktop, click "Projects" in the sidebar, then "Create Project." Name it "Affirmology."
2. Open the project's settings and paste the whole block below into the Project Instructions (sometimes labeled "Set custom instructions"):

You are helping Sol Ballard, co-founder of Affirmology. Affirmology turns a person's cosmic blueprint (astrology, Human Design, Gene Keys, numerology) into hyper-personalized, first-person affirmation audio called a Sacred Audio, framed as a software update for the Subconscious Operating System.

Hard rules, never break these:
1. No em dashes anywhere, ever. Use periods or commas.
2. Chart readings come from our agent system, not from you. If Sol asks what her chart or anyone's chart says, remind her to ask Hermes in the Atlas app (studio.affirmology.ai). You may help her phrase the question and work with the answer she brings back. Never improvise astrology, Human Design, Gene Keys, or numerology readings yourself.
3. All finished audio comes from our system. Help with scripts, words, and ideas freely, but never suggest generating audio with any outside text-to-speech tool.
4. Script craft: first person, present tense, spoken aloud, poetic but never cheesy. Recognition over instruction. Content comes only from the person's own chart. Never open with "close your eyes" or "take a deep breath" or "welcome." Be definite, never wishy-washy. No catastrophe framing; hope and power stay dominant. No present-tense negations; past-tense the old state and land in the new one.
5. Sol is "Sol" or "Soledad," never "Soul." Never name a specific meditation teacher; say "heart coherence breath" or "embodied gratitude induction."

Sol's lanes: music beds (Suno prompts are in the project knowledge), brand voice and story, social media, feedback on audios and readings. Jeff runs the engine, the code, and the system.

To send work to Jeff and the system: save it as a file and upload it to the from-sol folder in the jpl-knowledge GitHub repo, or email jeff@jeffparker.love. The project knowledge files in this Project are the reference; the freshest state always comes from Jeff or from Atlas.

3. Now add knowledge files. In the same Project, find "Project knowledge" and click add/upload. From your Documents/Affirmology folder, upload at least these (all of them if the size limit allows): - README.md (the master briefing) - everything in the craft folder - everything in the sol folder (your chart facts, your wealth reading transcript, the Suno music prompts) - plan/Affirmology_LaunchWeek_OnePage_v1.md - system/Affirmology_Atlas_Overview_v1.md

Every chat you start inside this Project now knows all of it automatically. No pasting needed.

4. Connect GitHub inside Claude (so Claude can read the repo live)

1. In Claude Desktop click your initials (bottom left), then Settings, then Connectors.
2. Find GitHub in the connector directory and click Connect (or "Browse connectors" then GitHub).
3. Sign in with YOUR GitHub account when it asks, and approve access.
4. Test it: in a new chat in your Affirmology Project, ask "Read the README of jeffparkerlove22/jpl-knowledge and summarize what changed." If it reads the file, you are fully connected.

If the connector gives you trouble, skip it. The ZIP-plus-Project-knowledge path in steps 2 and 3 gives you everything; the connector just makes updates automatic.

5. Sending things our way

• Files: open https://github.com/jeffparkerlove22/jpl-knowledge/tree/main/from-sol in your browser, click "Add file" then "Upload files," drag your file in, click "Commit changes." Name files with the date first, like 2026-07-09_bed-notes.md. Jeff's side pulls this folder into the system.
• Quick things: email jeff@jeffparker.love or text Jeff.
• Anything about your chart, readings, timing, or audios: ask Hermes in Atlas. That is also where finished audios get made and delivered.

6. What to try first

Ask your Claude: "Read the Suno bed prompts in my project knowledge and help me plan a music bed generation session for the Sleep and Journey categories." The music beds are the number one thing waiting on you and this is exactly what your setup is for.

Answers for Sol's Claude (from its earlier questions)

• The repo was not public and not findable because it had not been created yet. It exists now, private, invite-only. Do not make it public.
• The corpus figure discrepancy is resolved: roughly 12,900 records was the June 13 snapshot; the corpus is roughly 25,500 records today; the investor material saying 25,000 is correct for July. The v2 README carries the current number.
• The "scripting manifesto" rules it extracted are correct and are now carried in the Project Instructions above, so no pasted notes are needed.

Maintenance (Jeff)

• When docs worth sharing change, copy them into AFFIRMOLOGY/jpl-knowledge/, then commit and push (or tell Cowork "refresh the jpl-knowledge pack and give me the push commands").
• Check from-sol/ when pulling, and route anything actionable into the Test and Change Queue.
• Colin can be invited to the same repo later; it is already curated to the runbook's no-ownership-material standard.