notes
By bfollington
Manage personal notes, thinking trails, and knowledge in SQLite databases with provenance tracking, AI-generated breadcrumbs, FTS5 full-text search, and workflow stages. Ingest loose notes into linked inbox chunks, generate thinking snapshots, and review recent activity via headspace briefings.
npx claudepluginhub bfollington/terma --plugin notesComponent Overview
Component Details
Commands (3)
Generate a new breadcrumb snapshot of current thinking state using SQLite notes.
Ingest loose notes into the SQLite notes database at `.sqlite/notes.db`.
Get back in the loop. Review recent thinking across notes, breadcrumbs, reflections, and resources to surface what you've been working on and where the interesting threads are.
Skills (2)
General guide for using the sqlite3 CLI to build composable knowledge databases. Use this skill when creating SQLite databases, designing schemas, querying data, managing relationships, or building new sqlite-based domain skills. Provides the foundational patterns that all specialized sqlite skills build upon.
Personal note-taking, thinking trails, and knowledge management using plain SQLite. Supports capture-heavy workflows with clear provenance tracking, AI-generated thinking snapshots (breadcrumbs), and synthesis into permanent knowledge. Uses the sqlite3 CLI directly with SQL schemas for notes, resources, clippings, reflections, and breadcrumbs.
README
Terma (གཏེར་མ)
This is a highly-opinionated library of philosophy and process for developing software with LLMs, specifically Claude Code.
Distributed as a Claude Code plugin marketplace.
Installation
From within Claude Code:
/plugin marketplace add <git-url-or-local-path>
/plugin install terma@terma
/plugin install terma@tsal
Or test locally during development:
claude --plugin-dir ./plugins/terma --plugin-dir ./plugins/tsal
Quick Start
Use /terma:orient to begin each session. Use /terma:research :question to probe the codebase and write a report to /research. Then, use /terma:plan to plan a change to the application.
Use /terma:implement to spin up one or more well-instructed subagents to implement the plan.
Use /terma:code-review after implementation. Use /terma:ideate to brainstorm.
Core Commands
| Command | Purpose |
|---|---|
/terma:orient | Explore and summarize the project structure |
/terma:research | Deep-dive investigation, writes report to /research |
/terma:plan | Plan next steps without implementing |
/terma:implement | Delegate implementation to subagents |
/terma:code-review | Review code for quality and consistency |
/terma:ideate | Brainstorm using the ideation card deck |
Patterns
- feature dev:
/terma:orient,/terma:plan,/terma:implement,/terma:code-review - research:
/terma:orient,/terma:research - brainstorm:
/terma:ideate
Structure
.claude-plugin/marketplace.json # Marketplace manifest
plugins/terma/ # Process & philosophy plugin
.claude-plugin/plugin.json # Plugin manifest
agents/ # Subagent definitions
skills/ # Commands & meta skills
lib/ # Shared philosophy & process modules
plugins/tsal/ # Domain-specific skills plugin
.claude-plugin/plugin.json # Plugin manifest
skills/ # Domain skills (bevy, godot, strudel, etc.)
Customizing
Edit anything under plugins/terma/ or plugins/tsal/. The lib/ directory in terma contains composable modules referenced by skills via @ paths. Domain-specific skills live in tsal and can be modified independently.
Trivia
The subagent.md lib module encourages "ultrathinking", which may burn through usage quickly. Consider customizing it manually until we have variables.
License
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Similar Plugins
fullstack-dev-skills
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.