Moves a completed project WHOLE from / / / to / / /, flips its frontmatter status: active → status: done, and regenerates the parent Area's index.md (thin-Areas model — no artifact-promotion step). All paths come from the Configuration section in root CLAUDE.md — read those first. Use this whenever the user says…
Interactive first-run setup for a fresh fork of the second-brain-os — THE entry point every fork user runs once to configure their identity, name their assistant's persona (no default name — fork users always name their own), pick a design system, create the PARA workspace, and write the Configuration token block in…
Morning chief-of-staff briefing — composes available signal sources (email, calendar, messaging, issue-tracking, code-hosting) plus local sources (contacts, active projects, USER.md priorities) into one self-contained HTML brief at / /briefings/morning-briefing-YYYY-MM-DD.html. Detects tool availability at runtime in…
Write-mode skill — append a new interaction entry to a matched contact's ## Interaction log section in / /contacts/ .md and auto-bump the lastinteraction frontmatter to today's date. Append-only via Edit (never Write — preserves prior entries + About / Recurring topics / Open commitments sections). Entry text…
Read-only display of a contact's profile from / /contacts/ .md — fuzzy-matches a name, then surfaces frontmatter summary, last interaction, open commitments, About, and recurring topics. Use for "/contact ", "who is X?", "what's my context with Y?", or "tell me about ". PRECEDENCE: /contact wins when a contacts file…
A long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
Run a 5-dimension expert design review on any HTML artifact in the project — Philosophy / Visual hierarchy / Detail / Functionality / Innovation, each scored 0–10. Outputs a single self-contained HTML report with a radar chart, evidence-backed scores, and three lists: Keep / Fix / Quick-wins. Use when the brief asks…
Admin / analytics dashboard in a single HTML file. Fixed left sidebar, top bar with user/search, main grid of KPI cards and one or two charts. Use when the brief asks for a "dashboard", "admin", "analytics", or "control panel" screen.
A documentation page — left nav, scrollable article body, right-rail table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".
Quarterly / monthly financial report — masthead with KPIs, revenue and burn charts, P&L summary table, top-line highlights, and an outlook paragraph. Use when the brief mentions "financial report", "Q3 report", "MRR review", "P&L", or "财报".
Meeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".
Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".
A standalone pricing page — header, plan tiers, feature comparison table, and an FAQ. Use when the brief asks for "pricing", "plans", "subscription tiers", or a "compare plans" page.
Single-page SaaS landing with hero, features, social proof, pricing, and CTA. Respects the active DESIGN.md color/typography/layout tokens. Trigger keywords: "saas landing", "marketing page", "product landing". Use when the user says "saas landing", "marketing page", "product landing".
Single-file horizontal-swipe HTML deck. Built by copying the seed assets/template.html (which carries the proven 5-rule iframe nav script) and pasting slide layouts from references/layouts.md. Pitch decks, product overviews, study material. Use when the user says "deck", "slides", "ppt", "presentation".
OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".
Wrap any HTML artifact with a side panel of live, parameterized controls — accent color, type scale, density, motion, theme — that rewrite CSS custom properties in real time and persist to localStorage. Lets the user explore variants of a design without re-prompting the agent. Use when the brief asks for "variants"…
General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed assets/template.html and pasting section layouts from references/layouts.md. Default for any landing / marketing / docs / SaaS page when no more specific skill matches. Use when the user says "prototype", "mockup"…
Single-file horizontal-swipe slide deck for a weekly team update — shipped, in flight, blocked, metrics, asks. 6–8 slides. Use when the brief mentions "weekly update", "team update slides", "weekly status", "周报演示".
Recall layer for the second brain. Searches across / /, /, /, / (HQ workstations, now PARA Areas), and memory/ for a topic — by filename and content — then merges, ranks, and optionally synthesizes matches with file citations. Use whenever the user asks to recall existing knowledge before generating new content …
Confirmation-gated intake and cleanup for three surfaces: the workspace Inbox, misplaced workspace-root items, and loose Mac Desktop or Downloads files. Also surfaces unmigrated Projects folders missing CLAUDE.md. Use for "process inbox", "Friday cleanup", "clean up root", "organize my desktop", "clean up downloads"…
Bring a user's EXISTING work into their second-brain-os PARA workspace by reading past local Cowork sessions, discovering real projects, and scaffolding only approved non-code entries in Projects or Resources. Read-only discovery, one approval gate, copy-never-move writes, no fabrication, and no auto-commit. Runnable…
Scaffolds a new workspace project using the PROJ or COD naming convention, or creates an Area-owned app repository with optional GitHub integration. Use when the user wants to start, kick off, scaffold, set up, or create a project, app, or repo. Routes personal one-video projects to /new-video-project.
OS reference manual — for fork users in their first 30 days AND for Claude Code self-correcting mid-session on an OS-shaped mistake. Routes the question to its canonical source file, reads at runtime, answers with file:line citations. Topics — PARA, Configuration tokens, memory model, contacts schema, tools…