Pin every newly-bootstrapped project to Windows / PowerShell out of the box by adding a fifth trigger line to the CLAUDE.md template. The line activates the active-platform skill, which then governs all command/example output. - skills/project-bootstrap/assets/CLAUDE.md.template: append `we're on Windows` - skills/project-bootstrap/SKILL.md: sync the embedded preview in Step 5 and document the Linux/macOS substitution - CLAUDE.md (this repo): backfill the line — was created from old template - dist/project-bootstrap.skill: rebuilt - .wiki/source/active-platform-decision.md: append "Wired into project-bootstrap" Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2.0 KiB
2.0 KiB
Task Board
Updated: 2026-04-28
Done
project-bootstrap: include active-platform trigger in CLAUDE.md template
- Add
we're on Windowsline toassets/CLAUDE.md.template - Update embedded preview in
SKILL.mdStep 5 (with note about Linux/macOS substitution) - Backfill the line in this repo's own
CLAUDE.md - Rebuild + reinstall
project-bootstrap.skill
active-platform skill
- Draft
skills/active-platform/SKILL.md(RU+EN triggers, default=Windows/PowerShell, palette=Win/Linux/mac) - Fixed
build.shPS arg-passing bug (single-quotes were leaking into-Namesvalue) - Build
dist/active-platform.skilland install into~/.claude/skills/ - Document decision in
.wiki/source/active-platform-decision.md - Update
.wiki/SUMMARY.md
bootstrap-skills-migration
- Bootstrap repo (git, .wiki, .tasks, CLAUDE.md)
- Brainstorm and document repo layout (
.wiki/source/repo-layout.md) - Copy all 12 personal skills from
~/.claude/skills/toskills/ - Write
scripts/build.sh,scripts/build.ps1,scripts/install.sh - Document ZIP/PowerShell gotcha (
.wiki/source/build-notes.md) - Build initial
dist/*.skillarchives (forward-slash entry paths verified) - Update root README with usage
- Smoke-test
install.shto a temp dir - Remove legacy
project-bootstrap.skillfrom repo root (replaced bydist/)
Backlog
- Resolve
compressvscaveman-compressduplication (look at both, decide if one should go). - Consider a PowerShell-native
install.ps1(currentinstall.shalready works in git-bash, so low priority). - Revisit grouping/manifest if skill count grows past ~30.
- Decide whether to write a smoke-test that round-trips
skills/<name>/→dist/<name>.skill→ unpack → diff (would catch archive-shape regressions). - Tune
active-platformtriggers based on real-world usage; add WSL handling if it comes up. - Consider running formal
skill-creatoreval loop onactive-platformonce we have ~5 real interactions to learn from.