a9a7a328e6
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
1.3 KiB
1.3 KiB
When you need library or framework documentation, check in this order:
-
If Context7 MCP tools (
mcp__context7__*) are available in your environment, use them:- Resolve library ID:
mcp__context7__resolve-library-idwithlibraryName - Fetch docs:
mcp__context7__query-docswithlibraryId(the ID from step 1) andquery
- Resolve library ID:
-
If Context7 MCP is not available (custom subagents cannot see project-scoped
.mcp.jsonservers — they only inherit user-scoped~/.claude/mcp.json, so a context7 server configured at the project scope is invisible to spawned agents), use the CLI fallback via Bash:Step 1 — Resolve library ID:
if command -v ctx7 &>/dev/null; then ctx7 library <name> "<query>" else echo "ctx7 not found — install with: npm install -g ctx7 (verify at npmjs.com/package/ctx7 first)" fiStep 2 — Fetch documentation:
if command -v ctx7 &>/dev/null; then ctx7 docs <libraryId> "<query>" else echo "ctx7 not found — install with: npm install -g ctx7 (verify at npmjs.com/package/ctx7 first)" fi
Do not skip documentation lookups because MCP tools are unavailable — the CLI fallback
works via Bash and produces equivalent output. Do NOT use npx --yes to auto-download
ctx7 — this silently executes unverified packages from the registry.