learn-nexus_skill

Overview

This skill teaches the Nexus philosophy, design principles, and practical patterns so you can use the system reliably and avoid common mistakes. It’s a focused 15–18 minute walkthrough that turns conceptual understanding into concrete habits. By the end you’ll know why Nexus is structured the way it is and how to apply it to daily work.

How this skill works

The lesson presents Nexus as a living knowledge organism: executable files and metadata that the AI reads, loads, and acts on. It walks through the seven core problems Nexus solves, seven design principles, common pitfalls, collaboration patterns, and a short mastery quiz. The session finishes with required completion steps and a prompt to close the session so progress is saved.

When to use it

• After completing core onboarding skills as a natural graduation step
• When you want to understand why Nexus makes certain design choices
• If you see recurring AI errors (false progress, incomplete reads, over-engineering)
• When you plan to standardize workflows into reusable skills
• After several sessions using Nexus but before deep system customization

Best practices

• Treat every markdown and YAML as executable context, not passive documentation
• Prefer one reusable skill over many numbered project folders (e.g., weekly-report)
• Use progressive loading: metadata first, full content only when needed
• Always finish work with a close-session step to persist state
• Plan (one session) before executing (separate session) to avoid premature work

Example use cases

• Convert repetitive project folders into a single reusable skill (e.g., expense-report)
• Diagnose an AI claiming ‘files created’ by asking it to list or show those files
• Catch incomplete reads by asking the AI if it read the entire file and what’s at the end
• Stop over-engineering by asking for the minimum viable solution before building a full framework
• Run the planning pattern: structure and requirements in session 1, implementation in session 2