00-system/skills/learning/setup-workspace/SKILL.md
Organize your 04-workspace/ folder structure. Load when user mentions: setup workspace, organize folders, folder structure, configure workspace, my files, file organization, where to put files, workspace setup, directories, storage. 5-8 min.
npx skillsauth add abdullahbeam/nexus-design-abdullah setup-workspaceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This is an ONBOARDING skill with HIGH PRIORITY. Natural follow-up after setup-goals.
Check learning_tracker.completed.setup_workspace in user-config.yaml. If false:
PROACTIVELY SUGGEST when user:
workspace_configured: falseSuggestion Pattern (after setup-goals):
💡 Great, your goals are set! Next recommended step: 'setup workspace' (5-8 min).
This creates a practical folder structure in 04-workspace/ for your files,
tailored to your work patterns. Quick and makes file organization effortless.
Suggestion Pattern (file organization confusion):
💡 I notice you're working with files. Would you like to run 'setup workspace'
(5 min) to create a practical folder structure? It'll help keep your work
organized and make files easier to find.
Menu Integration:
When displaying menu with workspace_configured: false:
📁 WORKSPACE
Not configured ▸ 'setup workspace' (5 min)
DO NOT suggest if:
learning_tracker.completed.setup_workspace: trueGuide user through workspace folder design using just-in-time organization.
Create a practical folder structure in 04-workspace/ based on user's actual work patterns. Follows just-in-time principle: create only what you need now, add more later.
Time Estimate: 5-8 minutes
Read goals.md for role/goals context.
Ask: "What types of files and content will you work with?"
Listen for: document types, client/project categories, research vs output patterns.
Explain briefly:
━━━ KEY PRINCIPLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"Just-in-time organization": Only create folders you need NOW.
Don't over-organize on day 1. Structure emerges from real work.
We'll start with 3-5 essential folders.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Based on role, suggest 3-7 folders. Example for sales:
📁 04-workspace/
├── clients/
├── proposals/
├── research/
├── templates/
└── personal-notes/
Iterate until user is satisfied.
Create agreed structure in 04-workspace/.
Create/update 04-workspace/workspace-map.md with structure and usage notes:
# Workspace Map
> Auto-generated by setup-workspace skill
> Last updated: {date}
## Folder Structure
{folder tree with descriptions}
## Usage Notes
{any user-specified notes about organization}
Actions (MUST complete all):
Create workspace-map.md in 04-workspace/ (if doesn't exist)
Mark skill complete in user-config.yaml:
learning_tracker:
completed:
setup_workspace: true # ADD THIS LINE
Display completion:
✅ Setup Workspace Complete!
Created:
• {N} folders in 04-workspace/
• workspace-map.md with structure documentation
Principle: Just-in-time organization. Add folders when needed.
Next steps:
• 'learn projects' - Understand project workflow
• 'learn skills' - Create reusable workflows
• 'create project' - Start your first project
Prompt close-session:
💡 When you're done working, say "done" to save progress.
learning_tracker.completed.setup_workspace: true in user-config.yamldevelopment
Load when user says "mental model", "think through this", "structured thinking", "help me decide", "analyze this problem", "first principles", "pre-mortem", "stakeholder mapping", "what framework should I use", or any specific model name. Provides 59 thinking frameworks for decision-making, problem decomposition, and strategic analysis.
development
Generate comprehensive philosophy and standards documents for any domain (UX design, landing pages, email outbound, API design, etc.). Load when user says "create philosophy doc", "generate standards for [domain]", "build best practices guide", or "create benchmarking document". Conducts deep research, synthesizes findings, and produces structured philosophy documents with principles, frameworks, anti-patterns, checklists, case studies, and metrics.
development
Validate Nexus-v3 system integrity and fix common issues automatically. Load when user mentions "validate system", "check system", or "fix problems". Runs comprehensive checks on folder structure, metadata files, and framework consistency with auto-repair capabilities.
development
Load when user says "validate docs", "check documentation consistency", "docs vs implementation", or "find documentation mismatches". Systematically compares implementation code against documentation to identify and fix inconsistencies.