Skip to content
Baseworks KB

Session Continuation — Voice Guide + Blog Post Finalization

Created 2026-03-25
Type session-handoff
Status active

Prepared by Claude Code on Patrick’s Mac, 2026-03-25

Use this document to pick up where the previous session left off. Paste it as context when starting a new terminal session.

What Was Completed This Session

Section titled “What Was Completed This Session”

Blog Post: “From Three Forms to Twenty-One”

Section titled “Blog Post: “From Three Forms to Twenty-One””

File: 02-areas/website/blog-articles/2026-03-winter-study-group-recap.md

All 10 of Asia’s feedback points were reviewed, voice-corrected, and applied. Patrick also made his own edits directly in VS Code. Key changes:

  • Opening paragraph rewritten in first person with corrected timeline (studio 2003, interdisciplinary space, Baseworks progressive from ~2010, exclusive by ~2012, core group ~decade)
  • Point 1: Counter-intuitive features sentence added (voice-corrected: dropped “rather than” negative frame)
  • Point 2: Master classes paragraph added (Patrick’s edited version: “highlight” not “produce,” past tense, “designed for”)
  • Point 3: Primer priming sentence added (“focuses attention on what would otherwise continue running on autopilot”)
  • Point 4: Smart Revisit capitalized, “practice lessons” specified, reframed as “re-encounter”
  • Point 5: Period after “meant,” “physical shape” instead of “model”
  • Point 6: Orientation expanded with “automatic patterns we all default to in daily life”
  • Point 7: “Monday” removed
  • Point 8 (critical): Guylaine paragraph completely replaced. “Movement educator with a yoga teaching background who leads online classes.” Sarah’s account removed entirely.
  • Point 9: PrimerPrint section reframed to tie uniqueness to Smart Revisit
  • “Programmatic material” → “educational material,” “programs” → “collaborations”
  • Practice Platform hyperlink changed from practice.baseworks.com to the filming article
  • Spelling: “practise/practising” → American English “practice/practicing” throughout
  • Patrick made additional edits: new hyperlinks (Practice Sessions, Gridlines and Symmetry), restructured sentences, contractions, punctuation fixes, new PrimerPrint photo placeholder

Voice Guide Updates (now at v2.1 draft)

Section titled “Voice Guide Updates (now at v2.1 draft)”

File: 03-resources/voice-guides/VOICE-GUIDE-UNIFIED.md

  • Smart Revisit and PrimerPrint added to capitalization table
  • “Running on autopilot” added to Allowed Metaphors (occasional use, max once per piece)
  • 6 new Good vs. Needs Revision entries (negative framing patterns, metaphors, “transform” usage)
  • Spelling changed to American English: “practice/practicing” (v2.1)

Other Files Updated

Section titled “Other Files Updated”
  • 02-areas/method-admin/core/taxonomy.md — Platform Features section added (Smart Revisit, PrimerPrint)
  • 02-areas/method-admin/core/history.md — Timeline corrected (2003 studio opening, progressive transition from ~2010, exclusive by ~2012, broader programming noted)
  • 02-areas/website/blog-articles/_feedback-winter-study-group-asia.md — Full “Patrick’s Review” section added documenting every decision and voice reasoning
  • 00-inbox/asia-inbox.md — Voice guide v2.0 notes for Asia added

What Needs to Happen Next

Section titled “What Needs to Happen Next”

1. Voice Guide Structural Improvements (the main thread to continue)

Section titled “1. Voice Guide Structural Improvements (the main thread to continue)”

Patrick identified a systemic problem: when Asia works with Claude, the AI output defaults to a marketing-heavy, polarizing, negative-framing tone drawn from older content in the vault. The voice guide corrects for this but isn’t weighted heavily enough during text generation.

Three approaches were discussed but not yet implemented:

(a) Strengthen the voice guide front matter — Add a blunt “default AI tone” warning section near the top of the unified guide, before Core Principles. Something that explicitly names the pattern: AI-generated text defaults to polarizing, stone-throwing, deficit-framing language. Every sentence needs to pass three filters: (1) Does it describe what something IS? (2) Is it free of generated metaphors? (3) Does it lead with the positive?

(b) Tighten the /write-blog-post skill — The skill loads voice guides but could be more explicit about this specific failure mode. Currently says “voice compliance is non-negotiable” but doesn’t flag the negative framing default.

(c) Consider a /voice-check skill — A post-generation pass that flags violations. Would run against any draft. This is a second step after (a) and (b).

Patrick also asked whether a dedicated skills.md file is needed for everything related to writing and tone.

2. Check Patrick’s Inbox for Asia’s Voice Guide Comments

Section titled “2. Check Patrick’s Inbox for Asia’s Voice Guide Comments”

Patrick mentioned there are items from Ksenia/Asia in his inbox related to the voice/communication guide. These should be reviewed as part of the voice guide work. Check:

  • 00-inbox/patrick-inbox.md — look for any open items from Asia about voice guide, communication, or tone
  • Also check: 00-inbox/blog-feedback-optimization-discussion.md (Asia’s Claude was working on something related during this session, per git log)

3. Blog Post Pre-Publication Remaining Items

Section titled “3. Blog Post Pre-Publication Remaining Items”

From the pre-publication checklist in the blog post’s Draft Notes:

  • Verify contact form URL (https://baseworks.com/contact/)
  • Verify Baseworks Primer landing page URL (currently linked to /primer/)
  • Patrick to select photos for 4 placeholders (+ new PrimerPrint side-by-side photo)
  • Final read-through before publication
  • Verify French interview quote translations

4. Memory: Practice Platform Linking Rule

Section titled “4. Memory: Practice Platform Linking Rule”

Already saved to memory but worth noting: practice.baseworks.com must NEVER be used as a public-facing hyperlink. Use baseworks.com/practice/ or the filming article URL. See memory file feedback-practice-platform-linking.md.

Key Voice Guide Rules Established This Session

Section titled “Key Voice Guide Rules Established This Session”

For quick reference in the next session:

  1. No “rather than” negative framing — drop the contrast clause, the positive statement stands alone
  2. No generated metaphors — “clicks into place,” etc. are not allowed; describe what happens
  3. “Running on autopilot” — approved for occasional use (max 1x per piece)
  4. “Transform” — can be used occasionally in formal copy where it doesn’t sound woo-woo, but default to “changes/shifts/recalibrates”
  5. Lead with the positive — “The idea is re-encounter” not “The idea is not repetition but re-encounter”
  6. American English — “practice/practicing” not “practise/practising”
  7. Smart Revisit, PrimerPrint — always capitalized as named platform features
  8. Occasional negative framing is fine — context dependent, but the default must be positive