skills/beam-next-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 beam-ai-team/beam-next-skills 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
--- name: taste-skill type: skill version: '1.0' author: Leonxlnx (packaged by Zhichao Li) category: general tags: - frontend - design - anti-slop - landing-page updated: '2026-06-11' visibility: public description: Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. license: MIT.
development
Use when communicating quantitative information in any form — Slack updates, emails, reports, decks, dashboards, landing pages, product UI, public talks. Covers two integrated layers: (1) making numbers semantically meaningful (translation, anchoring, simplification, story-pairing) and (2) showing numbers cleanly (chart vs table vs prose, chart-by-message, pre-attentive emphasis, color discipline, decluttering). Distilled and integrated from *Show Me the Numbers* (Stephen Few) and *Make Numbers Count* (Chip Heath & Karla Starr). Not for raw data analysis or statistics — this is about communication of numbers, not their derivation.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
tools
Stateful multi-session tutor adapted for Beam — teach a stakeholder to understand, trust, and operate a specific agent, or teach a Solution Engineer a client's business process for delivery. Grounds every lesson in Knowledge Hub sources (real agent graphs, real tasks, transcripts, Linear) before any web resource. Also works for any general topic. Trigger on "teach me", "beam teach", "教我", "onboard <person> on <agent>", "help <stakeholder> understand the agent", "learn this client's process".