Files
claude-skills/.tasks/STATUS.md
vitya 9d7d25223c feat: setup-context7 skill + using-context7 prerequisites pointer
Split context7 concerns into two skills:
- using-context7 (policy, every-time): when to call, how to query well
- setup-context7 (infrastructure, one-time): install plugin, inject API
  key, clean manual MCP entries, with confirmation gates

setup-context7 reuses an existing CONTEXT7_API_KEY by searching, in order:
~/.claude/settings.json → ~/.claude.json (top-level + project-scoped) →
~/.claude/settings.local.json → env. Asks the user only if nothing found.
Cross-platform (paths identical on Win/Linux/macOS; only JSON validator
differs). Phase-2 confirmation gate before any write; per-edit JSON
validation; rollback procedure documented.

using-context7 gets a small Prerequisites section pointing at
setup-context7 when MCP tools are missing.

Bonus fix: scripts/build.sh PS multi-arg bug. Comma-joined -Names didn't
split into [string[]] when build.ps1 was invoked via -File. Now the bash
side loops one PS invocation per skill.

Wiki: extended .wiki/concepts/context7-setup.md with the design rationale
(why split policy from setup) — template for future "X plugin + how to
use X" pairs. index.md and log.md updated.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-28 11:56:22 +03:00

5.2 KiB

Task Board

Updated: 2026-04-28

Done

Create setup-context7 skill

  • Drafted skills/setup-context7/SKILL.md — 8 phases (discovery → plan → backup → install → inject → clean → smoke-test → restart) + rollback + cross-platform notes
  • API-key discovery in priority order: settings.json.claude.json (top-level + project-scoped) → settings.local.json → env → ask
  • Phase 2 confirmation gate (no mutations without explicit "ok"); Phase 6 validates JSON after each edit
  • Documented /plugin update gotcha
  • Added Prerequisites section in using-context7 pointing at setup-context7
  • Built + installed both skills (setup-context7 already in available_skills)
  • Updated .wiki/concepts/context7-setup.md with "Now captured as a skill" section explaining the policy/setup split rationale
  • Bonus fix: scripts/build.sh PS multi-arg bug — comma-joined -Names wasn't splitting into [string[]] when called via -File. Now loops in bash, one PS invocation per skill.

Switch context7 from manual MCP config to official plugin

  • Backup ~/.claude.json and ~/.claude/settings.json (suffix .bak-20260428-114532)
  • User installed context7@claude-plugins-official
  • Located installed plugin: ~/.claude/plugins/cache/claude-plugins-official/context7/unknown/
  • Injected --api-key flag into the plugin's .mcp.json (key sourced from settings.json, not echoed in chat)
  • Smoke-tested mcp__context7__resolve-library-id (returned 5 Nuxt entries — works in current session via legacy HTTP config; plugin takes over after Claude Code restart)
  • Removed three manual context7 entries (settings.json + 2 in .claude.json); JSON validity confirmed
  • Documented setup + plugin-update gotcha in .wiki/concepts/context7-setup.md
  • Wiki index + log + summary updated

Migrate this repo's .wiki/ to canonical Karpathy layout

  • git mv .wiki/source/*.md.wiki/concepts/ (rename detection preserves history)
  • Add type: concept frontmatter to each migrated page
  • Create .wiki/CLAUDE.md (schema, with Karpathy gist URL pinned at top)
  • Create .wiki/index.md (replaces SUMMARY.md)
  • Create .wiki/log.md with backfilled entries for prior decisions
  • Create .wiki/overview.md (project intro page)
  • Create .wiki/raw/README.md (replaces .gitkeep placeholder)
  • Empty .gitkeep in .wiki/entities/, packages/, sources/
  • Delete .wiki/SUMMARY.md, .wiki/source/, .wiki/raw/.gitkeep

project-bootstrap: align wiki init with Karpathy canon

  • Read Karpathy gist + wiki-maintainer SKILL.md — gap confirmed
  • Rewrite Step 3: create index.md, log.md, overview.md, .wiki/CLAUDE.md schema, raw/README.md, empty entities/ concepts/ packages/ sources/ with .gitkeep
  • Drop the bogus SUMMARY.md + WORKFLOW.md + source/ from the template
  • Pin Karpathy gist URL inside the schema file
  • Rebuild + reinstall project-bootstrap.skill
  • Document the realignment in .wiki/source/wiki-realignment.md

project-bootstrap: include active-platform trigger in CLAUDE.md template

  • Add we're on Windows line to assets/CLAUDE.md.template
  • Update embedded preview in SKILL.md Step 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.sh PS arg-passing bug (single-quotes were leaking into -Names value)
  • Build dist/active-platform.skill and 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/ to skills/
  • Write scripts/build.sh, scripts/build.ps1, scripts/install.sh
  • Document ZIP/PowerShell gotcha (.wiki/source/build-notes.md)
  • Build initial dist/*.skill archives (forward-slash entry paths verified)
  • Update root README with usage
  • Smoke-test install.sh to a temp dir
  • Remove legacy project-bootstrap.skill from repo root (replaced by dist/)

Backlog

  • Resolve compress vs caveman-compress duplication (look at both, decide if one should go).
  • Consider a PowerShell-native install.ps1 (current install.sh already 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-platform triggers based on real-world usage; add WSL handling if it comes up.
  • Consider running formal skill-creator eval loop on active-platform once we have ~5 real interactions to learn from.
  • Migrate this repo's .wiki/ to the canonical Karpathy layout (it was bootstrapped with the old buggy template). Directory rename + file moves; needs a conscious commit, not a silent piggyback.