From pocket-space
This skill should be used when the user asks "where does this go", "what folder should I use", "where is the product stuff", "find the marketing docs", or needs help navigating the Pocket Space folder structure. Provides a map of the shared drive so files land in the right place.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pocket-space:folder-navigationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pocket Space is a SocialFi web app facilitating real-life interactions where people can create clubs for IRL meetings using bonding curve mechanics.
Pocket Space is a SocialFi web app facilitating real-life interactions where people can create clubs for IRL meetings using bonding curve mechanics.
Pocket Space/
├── _Active/ — Current working documents (start here)
├── _Archive/ — Historical documents from previous pivots
├── _Meeting_Notes/ — Chronological team meeting notes (YYYY-MM subfolders)
├── Plugins/ — Plugins and integrations
└── README.md
Organized by department:
Core product planning and design work.
Design/ — User flows, screen mockups, UI inventoryGeneral_Research/ — Market analysis, competitive research, bonding curve mechanicsBrainstorming/ — Open questions, roadmap, ideation, future featuresFinancial modeling, projections, and budget assumptions.
Assumption_Research/ — Research backing the financial modelAll marketing strategy, channel planning, and go-to-market work.
Branding/ — Brand strategy and visual directionCustomer_Acquisition/ — Acquisition strategies by channel (Customer_Side, Host_Side, Go_to_Market, Grassroots_Marketing, Influencer_Marketing, Partnerships, Social_Media, Traditional_Ads, Other)Marketing_Budget/ — Budget planning and allocationMarketing_Ops/ — Operational tooling (Analytics, SEO, Technology_Stack)General_Research/ — Marketing-specific researchLegal considerations, compliance, and regulatory research.
General_Research/ — Deep-dive legal and regulatory researchOperational assets like API key tracking and avatar management.
When research leads to a .docx deliverable, everything lives in a self-contained topic folder:
[Department_Folder]/
└── [Topic_of_Research]/ ← Topic folder
├── [Topic_of_Research].docx ← Final deliverable
└── Research/ ← All source .md files
├── README.md
├── Landscape_Research.md
├── Comparison_Matrix.md
├── Segment_A/ ← Deeply nested by segment
│ ├── Segment_A_Deep_Dive.md
│ └── Sub_Topic/
│ └── Sub_Topic_Research.md
└── Segment_B/
└── Segment_B_Deep_Dive.md
This pattern applies anywhere a .docx is produced. The topic folder goes inside the relevant department folder.
| Content Type | Goes In |
|---|---|
| Product specs, wireframes, user flows | _Active/Product/Design/ |
| Market research, competitor analysis | _Active/Product/General_Research/ |
| Feature ideas, roadmap items | _Active/Product/Brainstorming/ |
| Financial models, projections | _Active/Finance/ |
| Research backing financial assumptions | _Active/Finance/Assumption_Research/ |
| Brand assets, identity work | _Active/Marketing/Branding/ |
| Growth strategies, acquisition plans | _Active/Marketing/Customer_Acquisition/ |
| SEO, analytics, marketing tools | _Active/Marketing/Marketing_Ops/ |
| Marketing research | _Active/Marketing/General_Research/ |
| Legal research, compliance docs | _Active/Legal/General_Research/ |
| API keys, ops assets | _Active/Operations/ |
| Meeting transcripts/notes | _Meeting_Notes/YYYY-MM/ |
| Outdated docs from old pivots | _Archive/ |
npx claudepluginhub fangdav/pocket-space-plugins --plugin pocket-spaceCreates, opens, and manages project workspaces in LiveDocs for cross-session memory, long-term tracking like diets or investments, and saving key outputs.
Organizes Obsidian notes using the PARA folder structure with rules for placement by note type and descriptive naming conventions.
Organizes an Obsidian vault: adds documents with auto-categorization, restructures misplaced files, processes meeting notes, and runs health checks.