Workspace Setup Notes

Translated from Korean

Dev Log

Workspace Environment Setup Log

February 14, 2026

As I began using Claude Code in earnest, I organized the workspace I'd haphazardly built up until now and set up the base environment.

CLAUDE.md Global Settings

Claude Code automatically reads the CLAUDE.md file at the start of a conversation to understand project context and rules. Its scope varies depending on location.

~/.claude/CLAUDE.md — Global. Applies regardless of the folder you open it in.
./CLAUDE.md — Applies only within the current project folder.
Can be placed in subfolders; global + project-specific settings can be combined

I created mine in the global location (~/.claude/CLAUDE.md) for personal settings (technical level, design preferences, code style, etc.) not tied to specific projects. Later, if project-specific build commands or unique rules arise, I can add a separate CLAUDE.md file in that folder.

About me: CS + Philosophy major, technical planner, not a full-time developer, still learning
Tech stack: HTML/CSS/JS primary, Python, gradually expanding to API/DB/server
Code rules: Korean comments, explain reasons when adopting new tech, simple and intuitive design
Design: Two styles - Atelier (default) and Terracotta. Detailed specs referenced via path in _design/ folder files
Writing: Prefer prose, Obsidian-compatible Markdown
Communication: Korean, concise

Note: No character settings like Popo (work) or Lolo (personal) used in web apps. Claude Code is a coding tool, so practical rules work better than personality guidelines.

Workspace Folder Structure Reorganization

Reconfigured haphazardly stacked folders into a flat, project-based structure.

Before

workspace/
├── creatorsmorinng/              ← 오타
├── taylor/                       ← 잡다한 모음 (대시보드, 날씨봇, 디자인, 회의록)
├── techforimpact/
├── terracotta-light-theme.md     ← 루즈한 파일
├── taylor-atelier-enhanced.skill ← 루즈한 파일
├── tfi-retro-archive(구버전)/    ← 폐기된 프로젝트
├── tfi-retro-library/
├── tfiplanning(2025)/
└── theorakim.github.io/

After

workspace/
├── _archive/                      관리 - 보관용 (구버전 등)
├── _design/                       관리 - 디자인 리소스 & 설정 파일
├── creatorsmorning/               개인 - 창작하는아침 캘린더
├── pangyo-weather-bot/            개인 - 판교 날씨 카톡봇
├── tfi-github/                    업무 - GitHub org 로컬 미러
├── tfi-meeting-notes/             업무 - 회의록
├── tfi-planning-docs/             업무 - 기획/전략 문서
├── tfi-retro-library/             업무 - 회고 아카이브
├── tfi-sustainable-dashboard/     업무 - 지속가능트랙 대시보드
└── theorakim.github.io/           개인 - 블로그

Organization Principles

Flat structure per project: Independent folders for each project without top-level categories (work/, personal/)
tfi- prefix: All Tech for Impact work projects start with tfi- to distinguish work/personal
_ prefix: Management folders not tied to projects (_archive, _design) are distinguished with underscores
Remove Korean characters/parentheses: Prevent path issues in folder names
Decompose taylor/: Separate miscellaneous contents into appropriate locations

Git Status Check

Also verified Git repo connection status within the workspace.

Personal Account (theorakim)

Local Folder	GitHub Repo
tfi-retro-library	theorakim/tfi-retro-library
tfi-sustainable-dashboard	theorakim/sustainabletrack
pangyo-weather-bot	theorakim/pangyo-action
theorakim.github.io	theorakim/theorakim.github.io
_archive/tfi-retro-archive	theorakim/tfi-retro-archive

Organization Account (tech-for-impact)

Local Folder	GitHub Repo
tfi-github/campus	tech-for-impact/campus
tfi-github/guidelines	tech-for-impact/guidelines
tfi-github/services	tech-for-impact/services

Folders without Git

_design/, creatorsmorning/, tfi-meeting-notes/, tfi-planning-docs/

Notes

tfi-retro-library and tfi-sustainable-dashboard are company work projects but are currently in personal repos. Need to review moving them to an organization repo later.
Added .DS_Store to .gitignore in tfi-retro-library and theorakim.github.io. These are files automatically generated by macOS and don't need to be tracked by git.

Lessons Learned

Feel free to use CLAUDE.md as you like. You don't need to strictly follow developer-specific coding rules; incorporating your own level and preferences is actually more practical.
Renaming folders has no effect on Git. Even if you rename the outer folder containing the Git repository, the internal .git directory and remote connections remain unchanged.
.gitignore excludes files from Git tracking, not deleting them. The files remain intact and Finder functions normally.

byminseok.com