worth knowing

The fastest way to learn a domain is to spend time working in it.

The problem is that useful details often sit just outside the question you knew to ask. A default that changes an implementation. A limit you only discover in production. The origin of a convention that suddenly makes the whole system easier to understand.

Worth Knowing adds those details while you work.

Every few substantive replies, your AI adds one short, practical piece of knowledge about the domain already in front of you.

npx @gomzkov/worth-knowing

Worth Knowing is a small behavior layer for Claude Code, Cursor, and Codex. It waits until the answer is complete, then occasionally adds one useful detail:

Worth knowing: A JWT travels with every authenticated request, so adding claims increases bandwidth on every call and can eventually hit proxy header limits.

Each detail is:

• Collected in the context of real work. It comes from what you are actually doing.
• Short and practical. One useful line, not another explanation to read.
• Relevant to the current domain. No generic trivia or random facts.
• Worth remembering later. Defaults, limits, numbers, mechanisms, origins, use cases, and conventions.

It does not browse the web, call another service, or interrupt the answer. If there is nothing useful to add, it stays quiet.

The different mechanisms are intentional. Each agent gets the smallest supported integration that fits how it loads persistent instructions.

Worth knowing: SQLite's INTEGER PRIMARY KEY is an alias for the internal row ID, but adding AUTOINCREMENT changes reuse behavior and adds overhead.

Worth knowing: A five-point satisfaction scale often produces a ceiling effect, while a seven-point scale gives satisfied users room to distinguish “good” from “excellent.”

Worth knowing: Optical alignment often places a play icon slightly to the right of mathematical center because the triangle carries more visual weight on its left edge.

Worth knowing: The QWERTY layout was shaped by early typewriter mechanics, which is why modern keyboards still carry constraints from machines with physical typebars.

Run the interactive installer with Node.js 22 or newer:

npx @gomzkov/worth-knowing

Choose:

1. Claude Code, Cursor, Codex, or all three
2. A global installation or the current project

Existing settings and instruction files are preserved. Running the installer again refreshes the managed files without creating duplicate configuration.

For scripts and dotfile setup:

npx @gomzkov/worth-knowing install --agent all --scope global

Supported values:

• --agent claude|cursor|codex|all
• --scope global|project

• Claude Code: installs the skill and an exact-cadence hook. Start a new session after installing.
• Cursor project scope: installs an always-applied project rule and the skill.
• Cursor global scope: installs the personal skill. Cursor decides when to load it, so cadence is approximate.
• Codex: installs the skill and adds a clearly marked block to the applicable AGENTS.md.

npx @gomzkov/worth-knowing uninstall

The uninstaller removes only Worth Knowing files, its Claude Code hook entry, and its marked Codex instruction block. Other hooks, settings, skills, rules, and AGENTS.md content stay untouched.

For non-interactive removal:

npx @gomzkov/worth-knowing uninstall --agent all --scope global --yes

Set these environment variables before starting Claude Code:

Silent turns add no context. Eligible turns inject one short instruction, and the model can still skip the line when it would be forced or repetitive.

• Zero runtime dependencies.
• No install or postinstall script. Nothing changes until you explicitly run the CLI.
• The hook never executes, saves, or interpolates prompt text.
• Session IDs are reduced to safe filename characters before they touch the filesystem.
• Writes are atomic and existing configuration is merged instead of replaced.
• Managed-file symlinks are rejected rather than followed.
• Install and uninstall are idempotent and covered by a local self-test.

npm ci
npm test
npm pack --dry-run

The package is built from strict TypeScript. npm test compiles the installer and exercises global and project install/uninstall flows for all supported agents inside a temporary directory.

The release workflow checks the version tag and publishes through npm trusted publishing. See CONTRIBUTING.md for the local and release workflows.

MIT © Evgeni Gomziakov