NB Notes FAQs

Question 1

Can I organize notes with specific categories or tags?

Accepted Answer

Yes, the skill uses a standardized tagging system. You can categorize entries using tags like #technical-decision, #bug-fix, #code-pattern, and #deferred-task, making it easy to filter and retrieve specific types of information later.

Question 2

How does NB Notes differ from the TodoWrite tool?

Accepted Answer

The key distinction is persistence. TodoWrite is intended for managing active work-in-progress within a single session. In contrast, NB Notes is for long-term knowledge management, capturing insights and tasks that should persist and be searchable in future conversations.

Question 3

How does this skill improve my workflow with Claude?

Accepted Answer

It builds a long-term 'memory' for your project. By storing preferences, conventions, and past decisions in NB Notes, Claude can search this knowledge base in later sessions to provide more accurate, context-aware suggestions that align with your established patterns.

Question 4

What is the NB Notes skill for Claude Code?

Accepted Answer

NB Notes is a specialized capability that enables Claude to interface with the nb command-line system. It allows Claude to create, manage, and retrieve persistent technical notes, architectural decisions, and deferred tasks that remain accessible across different development sessions.

Question 5

When should I use the NB Notes skill during development?

Accepted Answer

You should use it proactively after solving complex bugs, making significant architectural choices, or discovering specific codebase patterns. It is also the ideal tool for logging deferred tasks or technical debt that you don't intend to address immediately.

NB Notes

NB Notes

主要功能

使用场景

主要功能

使用场景