78 lines
4.2 KiB
Markdown
78 lines
4.2 KiB
Markdown
╭─── Claude Code v2.1.89 ──────────────────────────────────────────────────────╮
|
||
│ │ Tips for getting started │
|
||
│ Welcome back Willem! │ Run /init to create a CLAUDE.md fi… │
|
||
│ │ ─────────────────────────────────── │
|
||
│ ▐▛███▜▌ │ Recent activity │
|
||
│ ▝▜█████▛▘ │ No recent activity │
|
||
│ ▘▘ ▝▝ │ │
|
||
│ │ │
|
||
│ Opus 4.6 (1M context) · Claude Max │ │
|
||
│ ~/research/pi-allium │ │
|
||
╰──────────────────────────────────────────────────────────────────────────────╯
|
||
|
||
❯ /plugin update
|
||
⎿ (no content)
|
||
|
||
❯ I would like you to make an implementation plan in allium-port-plan.md with
|
||
[ ] check boxes and file locations, assuming we have allium main checked out in
|
||
allium-main, and our pi port is in pi-allium in the current directory. Add
|
||
file locations, relevant urls and anything else that is needed to give an agent
|
||
on my machine with pi (we can run pi -p to check and load the skill). I can
|
||
also checkout the 'turn-limit' skill as a subdirectory so we can define tests.
|
||
I like TDD and small steps. One of the phases (later) would be to find a
|
||
suitable way to implement agents. Etiher as a custom extension or using one of
|
||
the existing agents extensions from npm.
|
||
|
||
Searched for 1 pattern, read 1 file (ctrl+o to expand)
|
||
|
||
● Now let me read the individual skill files and check how pi.dev handles things
|
||
like auto_trigger and agents.
|
||
|
||
Read 7 files (ctrl+o to expand)
|
||
|
||
● Now let me check what pi.dev supports for skills/agents/hooks.
|
||
|
||
● Bash(pi --help 2>/dev/null | head -50 || echo "pi not found in PATH")
|
||
⎿ (No output)
|
||
|
||
Read 1 file, listed 2 directories (ctrl+o to expand)
|
||
|
||
● Good. Now I have everything I need. Let me write the plan.
|
||
|
||
● Write(allium-port-plan.md)
|
||
⎿ Wrote 146 lines to allium-port-plan.md
|
||
1 # Allium → Pi.dev Port Plan
|
||
2
|
||
3 ## Goal
|
||
4 Port allium (https://github.com/juxt/allium) to pi.dev, keeping
|
||
upstream files by reference where possible.
|
||
5 Test with the turn-limit extension (https://gitea.apps.sustainab
|
||
ledelivery.com/QWAN/monotonic-pi-extensions).
|
||
6
|
||
7 ## Directory layout
|
||
8
|
||
9 ```
|
||
10 pi-allium/ ← this repo
|
||
… +136 lines (ctrl+o to expand)
|
||
|
||
● The plan is at allium-port-plan.md. Seven phases, small steps with checkboxes:
|
||
|
||
1. Setup + smoke test — clone allium, create root skill with pi frontmatter,
|
||
symlink references, verify it loads
|
||
2. Port sub-skills — elicit, distill, propagate with symlinked references
|
||
3. TDD with turn-limit — distill a spec from your extension, propagate tests,
|
||
write them red-green
|
||
4. Rules content — fold the .allium syntax rules into the skill context
|
||
5. Agents (tend/weed) — three options to evaluate: skills-as-agents
|
||
(simplest), TypeScript extension, or npm package
|
||
6. Hooks (allium-check) — post-write validation for .allium files
|
||
7. Docs and upstream — README, LICENSE, blog post
|
||
|
||
The symlink approach means allium-main/ is the single source of truth — you
|
||
git pull to update. The SKILL.md files in .pi/skills/ are thin wrappers with
|
||
pi-compatible frontmatter.
|
||
|
||
I also included notes for the agent on your other machine: model config, how
|
||
to invoke skills, and the symlink requirement. Want to start on Phase 1?
|
||
|
||
✻ Worked for 1m 41s |