Skip to content

docs(procedures): add think-tank directory documentation #1007

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
atxtechbro wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(procedures): add think-tank directory documentation #1007

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions knowledge/procedures/think-tank.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Think-Tank Directory

A designated space for personal content that lives outside the codebase but needs version control.

## Purpose
Store personal documents, notes, and drafts that:
- Don't belong in code directories
- Need to persist across development sessions
- Require version control for safety

## Location
**Always use**: `/think-tank/` in the main repository
**Never use**: Worktree locations (they're ephemeral)

## What Belongs Here
✓ Personal notes and brainstorming
✓ Resume drafts and career documents
✓ Learning notes and research
✓ Project ideas and planning docs
✓ Personal scripts or configurations

## What Doesn't Belong Here
✗ Code documentation (use `/docs/`)
✗ Project-specific notes (use project directories)
✗ Sensitive credentials (use `.bash_secrets`)
✗ Generated files or build artifacts

## Key Principle
Think-tank content is personal workspace material. It's tracked by git but kept separate from the technical ecosystem of the dotfiles.