00-system/skills/learning/learn-projects/SKILL.md
Learn how Nexus projects work. Load when user mentions: learn projects, how do projects work, projects vs skills, project tutorial, what is a project, project structure, project lifecycle, understand projects, explain projects. 8-10 min.
npx skillsauth add abdullahbeam/nexus-design-abdullah learn-projectsInstall 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 for proactive suggestion.
Check learning_tracker.completed.learn_projects in user-config.yaml. If false:
PROACTIVELY SUGGEST when user:
total_projects = 0Suggestion Pattern:
💡 Before creating your first project, would you like a quick 8-minute tutorial
on how Nexus projects work? It covers:
- When to use projects vs skills
- Project structure and lifecycle
- How to track progress effectively
Say 'learn projects' to start, or 'skip' to create your project directly.
DO NOT suggest if:
learning_tracker.completed.learn_projects: trueTeach how Nexus projects work through examples and decision framework.
Help user understand when to create projects vs skills, how projects are structured, and the project lifecycle. Uses concrete examples before abstract concepts.
Time Estimate: 8-10 minutes
Show what IS and ISN'T a project:
✅ PROJECTS:
- Build client proposal for Acme Corp
- Research competitors and write analysis
- Create onboarding docs for new hires
❌ NOT PROJECTS (these are skills):
- Generate weekly status reports (repeating)
- Qualify incoming leads (repeating)
- Format documents (repeating)
Pattern: Projects END. Skills REPEAT.
Ask: "What work are YOU planning? Let's classify it."
Question 1: Direction or Work?
• Direction = Goal (goals.md)
• Work = Project or Skill
Question 2: Does it repeat?
• NO → PROJECT (has endpoint)
• YES → SKILL (reusable)
ANTI-PATTERN:
❌ "weekly-report-week-1", "weekly-report-week-2"...
✅ ONE "weekly-report" SKILL used every week
📁 02-projects/05-client-proposal/
├── 01-planning/
│ ├── overview.md # What & why
│ ├── plan.md # How
│ └── steps.md # Tasks (checkboxes)
├── 02-resources/ # Reference materials
├── 03-working/ # Work in progress
└── 04-outputs/ # Final deliverables
PLANNING → IN_PROGRESS → COMPLETE → ARCHIVED
Explain each state briefly.
Ask: "Tell me 3 things you're planning to work on."
For each: apply decision framework together, explain reasoning.
To create a project, say:
• "create project for [description]"
• "new project: [name]"
Ready? Say "create project" to start one!
Actions (MUST complete all):
Mark skill complete in user-config.yaml:
learning_tracker:
completed:
learn_projects: true # ADD THIS LINE
Display completion:
✅ Learn Projects Complete!
You now understand:
• Projects vs Skills (projects END, skills REPEAT)
• Decision framework (Direction → Work → Repeat?)
• Project structure (planning → resources → working → outputs)
• Lifecycle states (PLANNING → IN_PROGRESS → COMPLETE)
Next steps:
• 'create project' - Start your first project
• 'learn skills' - Learn about reusable workflows
• 'learn nexus' - System mastery
Prompt close-session:
💡 When you're done working, say "done" to save progress.
learning_tracker.completed.learn_projects: 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.