The Skill Learns Sunday, and the Changelog Learns to Read
Install the skill and it now knows the weekly form, your PSP folder, and your dashboard. And every changelog page here finally shows its words.
Why Care?
Most people in the cohort will never open this repo. They'll download the skill, drop it into Claude, and say "let's work on my PSP." Until today, the skill they installed knew how to write a plan but not how to carry one through a week. It didn't know the Sunday form, where your files live, or how to show progress. Now it does.
And if you clicked into this changelog before today, you saw a title, a lede, and then nothing. Every entry and every context doc on this site rendered an empty body. That's fixed too.
What's New?
In the skill (what you get when you install the zip):
The Sunday session and the weekly form. The form is due Sunday afternoon. Claude now catches up your week, scores it, asks for reasons on misses, takes your outcome readings, and drafts every answer your log supports, page by page. You paste it in; it never submits for you.
One folder, any setup. Claude works out whether it can write files, is in a Project, or is in a single chat, and tells you plainly what that means for keeping your plan between conversations.
Outcome progress. Between checkpoints, each outcome shows how far you've come and where your pace is heading, and says so when there's no number yet.
A dashboard, your way. Claude starts from how you already keep track. If you have no preference, it recommends our setup firmly: dailies, weeklies, biweeklies, and monthlies, each with a base and a stretch, and outcomes read every Sunday.
The 3 + 1 + 1 goal structure, reasons beside results, and longest-stretch habits like a fast.
On this site:
Four new cards under What's inside: the dashboard, Sunday, outcome progress, and the one-folder setup.
New principles ("Not logged isn't missed", "A reason beside the result"), a Sunday exchange in A day with Claude, and a tip to start your PSP in a Claude Project.
Changelog and context pages render their full text again.
How It Works
The skill stays short and points at five references, each loadable on its own:
| Reference | What it's for |
references/Weekly-Cadence.md | The Sunday-to-Saturday clock and the Sunday session, step by step |
references/Weekly-Form.md | Every question on the weekly form, and where its answer comes from |
references/PSP-Folder-and-Modes.md | One folder per member; folder, Project, or single chat |
references/Outcome-Progress.md | How far each outcome has come and where it's heading |
references/Dashboard-Dataviz.md | Showing habits and outcomes their way; ours when they have no preference |
They ship inside the skill zip, so they resolve the same way in the Claude app as on GitHub.
Under the Hood
Why the pages were blank. The splash loads changelog/ and context-v/ with a
custom loader that stores each file's frontmatter and raw body. A custom loader
doesn't get Astro's markdown rendering for free, so <Content /> had nothing to
render.
The fix is the Lossless Flavored Markdown pipeline content-farm's splash
already uses: @lossless-group/lfm 0.6.0 (latest, from JSR via .npmrc) parses
the body to an MDAST tree, and AstroMarkdown.astro walks it, with components for
callouts, code blocks, images, tables, and hex-code citations. Their styles are
remapped to this site's tokens.
Two small extras:
Wikilinks resolve.
Some-Doclinks to the context page when it's published here, to the file on GitHub when it's a path, and stays plain text otherwise.Dates stop slipping a day. Frontmatter dates are calendar days; formatting them in UTC keeps "Oct 4" from showing as "Oct 3" west of Greenwich.