Dev Workspace

Last updated: 2026-03-13 05:15

Short · Long · Dumb · Technical

---

Multi-project workspace. Dev holds many projects; structure scales for each.

Folder Structure

c:\dev\
├── .cursor\         ← commands, rules, forms (localhost project form)
├── projects\        ← one folder per project
├── ai\              ← cursor/docs, chats, projects
├── docs\            ← human docs; rambles/<project>/
└── .zips\           ← per project + misc (dev-zip outputs → misc/archives)

See .zips/README.md for .zips layout. See ai/cursor/docs/OVERVIEW.md for full structure.

Projects

Project	What	Stack
BluePeak Services	Multi-tenant SaaS — each business gets a workspace (website). Master admin creates/sells; admins run workspaces; visitors use the site.	Next.js 16, React 19, Supabase, Tailwind 4
Hub Ecosystem	Personal data hub — user-owned, modular, containerized. Runs on Pi, Linux, Windows. NAS-centric storage, snapshots, optional marketplace.	Python/FastAPI, React/Vite, k3s

---

Doc Structure

Location	Who	What
ai/cursor/docs/	AI	Overviews, plans, TODOs, features, version-log
ai/chats/	—	Exported transcripts (Claude.ai)
ai/projects/	AI	Per-project notes (links to cursor docs)
docs/	Human	Human-authored docs; docs/rambles/<project>/ for raw notes

---

Links

Doc	Purpose
ai/cursor/docs/AI_CONTEXT_INDEX.md	For AI tools: condensed context files by task
ai/cursor/docs/OVERVIEW.md	Full workspace overview
ai/cursor/docs/TEMPLATES.md	Project templates (uses, difficulty, cost)
ai/cursor/docs/DEV_OVERVIEW.md	Folder structure, AI vs human
ai/cursor/docs/COMPLIANCE_REPORT.md	Rules compliance audit
ai/cursor/rules/docs-conventions.mdc	Cursor rules
.zips/README.md	Zip structure, dev-zip commands
projects/README.md	Project code
ai/README.md	AI-related content
docs/README.md	Human docs, rambles

---

Short

Multi-project development workspace. AI does most code; human directs and reviews. Docs, rambles, and zips organized by convention per project.

---

Long

This is the root of a multi-project development workspace. AI (Cursor) handles most implementation; the human sets direction, reviews, and contributes. Each project has code in projects/, docs in ai/cursor/docs/<project>/, rambles in docs/rambles/<project>/, and zips in .zips/<project>/. Documentation is split between AI-created docs (ai/cursor/docs/), human docs and rambles (docs/), and AI chat exports (ai/chats/). Version control applies when projects are in production: rolling set of 3, pre-change archives, version-archives.

---

Dumb

This folder is where the work happens. It holds many projects. The AI writes most of the code; you tell it what to do and check the results. Everything is organized: project code in projects/, AI stuff in ai/, your notes in docs/, and zip backups in .zips/ (per project). When something goes live, we keep the last 3 versions and archive older ones. New projects get the same structure.

---

Technical

Path	Purpose
projects/	Project code — one folder per project
ai/cursor/	Cursor docs (docs/) and rules (rules/docs-conventions.mdc)
ai/chats/	Exported AI chat transcripts (Claude.ai)
ai/projects/	AI-specific notes per project (links to cursor docs)
docs/	Human-authored docs; docs/rambles/<project>/ for raw notes
.zips/	Per project: archives/, extracted/, versions/, pre-change/, version-archives/; misc for workspace zips

Conventions: AI docs in ai/cursor/docs/ only. Version control when in prod: v1.0+, pre-change archive+log before edits, keep 3 in versions/, archive older to version-archives/. Rules: ai/cursor/rules/docs-conventions.mdc