Nostr sdks 更新

Knowledge Refresh Task

You are running a knowledge refresh for the Nostr SDK knowledge base. This is a maintenance task — do NOT answer user questions, only update your agent memory.

Important: Write all findings to your agent memory directory ONLY. Never modify files in the plugin/skill directory — those are read-only artifacts managed by the plugin update mechanism.

If arguments were provided, focus on: $ARGUMENTS Otherwise, perform a full refresh.

Refresh Procedure

1. Fetch Latest from Library Repositories

Fetch README and recent release notes for each SDK:

For each source, capture:

• Current version numbers (npm, JSR, crates.io, Maven Central, PyPI, SwiftPM)
• New or modified API surfaces
• Newly supported NIPs / dropped NIPs
• Breaking changes or deprecation notices
• Last commit timestamp; flag stale projects (>180 days inactive)
• Archive status changes

2. Search for Recent Developments

Use WebSearch for:

• "rust-nostr release" — version bumps, new bindings
• "nostr SDK new library" — emerging libraries to consider tracking
• "nostr-tools" / "NDK" major release notes
• "nostr go library" / "fiatjaf.com/nostr" — Go ecosystem updates
• "nostr Kotlin Swift" — JVM/Apple binding updates

3. Verify Project Status

For each tracked SDK:

• Is it still active? (commits in last 90 days)
• Has it been archived, renamed, or moved?
• Have new forks or successors emerged?
• Have new bindings appeared (UniFFI, FFI, JNI)?

If a new SDK is observed in the ecosystem, add it to the matrix in agent memory (not the shipped supporting docs) for inclusion in a future update release.

4. Update Agent Memory

Write all findings to your agent memory directory. Never modify plugin files.

MEMORY.md — update with:

• last_fetch_date: <unix-timestamp>
• Current version numbers for each tracked SDK
• Summary of what changed since last fetch
• Any newly archived / renamed / forked projects

Topic files — update or create as needed:

5. Report

Output a concise summary of what was found:

• Key changes since last refresh
• New version numbers
• New or archived libraries
• Any corrections to the shipped supporting documents
• Issues encountered (404s, missing data, etc.)

Source: 941design/claude-plugins — distributed by TomeVault.