TreeMap
무료 오픈소스 디스크 사용량 시각화 도구로, 사각형 트리맵·중복 파일 탐색·디스크 가득 예측·정리 시 파일을 휴지통으로만 이동한다
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A personal time and activity tracking application — a visual, day-and-night timeline for planning and logging how you actually spend your time, built as a real product rather than a prototype: a React client backed by a Postgres database (Supabase), with real accounts and local-first sync.README 전문 보기 ↗A personal time and activity tracking application — a visual, day-and-night timeline for planning and logging how you actually spend your time, built as a real product rather than a prototype: a React client backed by a Postgres database (Supabase), with real accounts and local-first sync.
Your whole day, as two rows — Day (6a–6p) and Night (6p–6a) — with activities placed on a real timeline rather than a flat to-do list. Every activity carries an arbitrary duration (8 minutes, 37 minutes, 2 hours — never rounded to fit a grid), belongs to one of nine wellness categories (Sleep & Rest, Food & Nourishment, Personal Care, Downtime & Errands, Movement & Body Therapy, Work & Projects, Nature & Spirit, Growth & Connection, Home & Chores), and can optionally carry an activity quality, any number of chronic symptoms, a protective-response flag (Trauma response, Stress response, Fear response, Anger response), and freeform notes — the sensitive fields (flags, quality, symptoms, notes) encrypted at rest, visible only to you.
The whole interface is a single monochrome light/dark theme — no per-category or per-item colour anywhere — toggled instantly by the Sun/Moon icons beside the two timeline rows, and persisted per-device.
Two ways to schedule something — dragging an activity onto the timeline, or selecting a slot and picking an activity — go through the exact same underlying logic, so they can never drift into two different sets of rules.
Implemented and running: real email/password accounts, a Postgres backend with row-level security, local-first writes (every change saves instantly to the device and syncs in the background — the app never waits on the network), a real date picker for any past or future day, and real weather + city-based location.
See BACKLOG.md for exactly what's shipped, what's mid-flight, and what's next — it's kept current and is the fastest way to get oriented.
npm install
npm run dev # starts the Vite dev server
npm test # runs the test suite (vitest)
npm run typecheck # tsc, no emit
npm run build # production build
The app runs fully offline/local-only with zero setup — no backend required to explore the timeline. To connect it to a real Supabase project, copy app/.env.example to app/.env and fill in VITE_SUPABASE_URL / VITE_SUPABASE_PUBLISHABLE_KEY (the publishable/anon key — safe to be public; every real permission boundary is enforced by row-level security on the database, not by keeping this key secret).
| File | What it's for |
|---|---|
PRODUCT.md | What this product is, who it's for, and why it's built this way |
FEATURES.md | What's actually built and working today |
ROADMAP.md | Where the product has been and what's genuinely being considered next |
UX.md | The interaction model — how scheduling, editing, and navigation actually work |
UI-DESIGN.md | The visual design system as built |
BACKLOG.md | The current priority and everything confirmed-but-deferred — the living source of truth for "what's next" |
OPEN-QUESTIONS.md | Genuinely unresolved product/design decisions |
PRODUCT-HANDOFF.md | Historical: the original prototype's full spec, superseded by the above but preserved for context |
CLAUDE.md | Engineering constitution — product philosophy, design system rules, and the architecture/rules the project's engineering agent works against |
React 19 + TypeScript + Vite, Tailwind CSS + shadcn/ui-style components + Radix primitives, Lucide icons. Backend: Supabase (Postgres, row-level security, real-time-capable, email/password auth). Deployed on Vercel.
WORKFLOW.mdRequired branching and release process — cut from develop, test against the test database, never merge directly to main |