This is a personal knowledge management repository using Obsidian + Git for long-term learning and research.
knowledge-base/
├── atomic/ # Single-concept notes (core knowledge)
├── projects/ # Project-specific work (thesis, courses, etc.)
├── templates/ # Note templates for consistency
└── claude.md # This file
- One concept per note
- Stored in
atomic/
- Use template from
templates/atomic_note.md
- Link concepts using
[[note_name]]
syntax
- Use lowercase with underscores:
reml_criterion.md
- Be descriptive but concise
- No dates in filenames (use frontmatter)
- Links (
[[]]
): For specific concept relationships
- Tags (
#
): For broad categorization
- Always connect new concepts to existing notes
When I create atomic notes:
- Use the template structure from
templates/atomic_note.md
- Include proper frontmatter (date, tags)
- Suggest connections to existing notes
- Keep explanations clear but concise
When creating code implementations:
- Place in
projects/[project-name]/code/
- Include docstrings explaining the concept
- Link to relevant atomic notes in comments
For any project:
- Create project folder:
projects/[project-name]/
- Reference atomic notes for reusable concepts
- Keep project-specific notes separate from general knowledge
Type: Brief description
Types:
- Add: New note/concept
- Update: Revisions to existing notes
- Project: Project-specific work
- Code: Implementation work
Add: REML criterion derivation
Update: Clarify penalized regression explanation
Project: Thesis chapter 2 draft
Use these status indicators in notes:
- 🌱 seedling: Initial capture, needs development
- 🌿 growing: Partial understanding, actively developing
- 🌳 evergreen: Well-understood, stable reference
When I create files, I'll place them in appropriate locations:
- Atomic concepts →
atomic/[topic_name].md
- Code implementations →
projects/[project]/code/
- Templates →
templates/
List your active projects here as you work on them.
- Create atomic note in appropriate location
- Start with simple explanation
- Build up mathematical detail incrementally
- Include code examples when relevant
- Suggest related concepts to explore next
- Explain what the code does conceptually first
- Reference the mathematical formulation from atomic notes
- Include comments linking to note files
- Keep functions small and well-documented
- Go step-by-step, waiting for confirmation before proceeding
- Present one logical section at a time
- Explain the "why" before the "how"
- Build up complexity gradually
- Don't create nested folder structures without asking
- Don't dump large amounts of information at once
- Don't skip explanations of mathematical concepts
- Don't create files outside the defined structure without discussion
When creating a new atomic note:
- Check if related concepts already exist
- Use template structure
- Add frontmatter with date and initial tags
- Write "What is this?" summary first
- Add detailed notes
- List connections to other notes
- Include questions for future exploration
This is a long-term knowledge repository for:
- Learning and research notes
- Concept development across multiple domains
- Project work that builds on reusable knowledge
- Code implementations with clear explanations
The repository uses:
- Obsidian for note-taking and linking concepts
- Git for version control and long-term storage
- Atomic note structure for building connected knowledge over time