yysun

Build and maintain local code-project wikis under .wiki or language-specific wiki roots such as .wiki-cn and .wiki-fr. Use this skill whenever the user mentions "wiki", "ingest", "refresh wiki", "update wiki", "lint wiki", "check wiki", "document the codebase", "export wiki", "bundle wiki", "archive wiki", or asks a question that can be answered from wiki pages. Also use it when the user asks how something works in the project and a wiki page could capture the answer for future reference.

Create, review, audit, and validate AI workspaces for agent hosts such as Codex, Copilot, Gemini, and similar desktop or CLI runtimes. Use when the user asks to design an agent-ready repo, scaffold AGENTS.md and event handlers, create an API-backed or domain knowledge workspace, audit AGENTS.md or SKILL.md quality, or improve how a repo exposes behavior to coding agents.

Scaffold, review, audit, and validate skill-based AI workspaces for agent hosts. Use when the user wants an AI workspace built around SKILL.md plus event handlers, references, templates, scripts, data, and output instead of AGENTS.md; when they want knowledge distillation workflows packaged as a reusable skill; or when they want to convert an AGENTS.md workspace pattern into a skill-owned workspace.

Use when user needs to plan, storyboard, review, critique, or rewrite a presentation outline or slide deck, including SCR presentations, BBP/Beyond Bullet Points presentations, scene-based decks, headline development, bitmap visual generation, and handoffs to Markdown, Marp, or PPTX production.

Use when creating, modifying, refactoring, reviewing, or organizing a React web app that uses Tailwind or utility-first CSS. Trigger for requests involving React pages, routes, layouts, components, feature UI, styling systems, app shells, frontend folder structure, UI architecture, import boundaries, thin routes, component placement, or avoiding catch-all folders such as `components` and `lib`. Especially relevant when deciding whether code belongs in foundations, primitives, patterns, features, pages, shell, or shared utilities.

Design or review business operation pages, workbenches, and review or follow-up pages as task-centric workspaces. Use when working from requirement docs, business workflows, wireframes, screenshots, HTML, or frontend page proposals.

Use the converter script to render a MusicXML file to SVG markdown image output.

Use this skill for NotebookLM tasks to create notebooks, add sources, query content, and generate artifacts through the NotebookLM CLI.

Build, refactor, review, or organize a React + Tailwind web app using a layered UI architecture: `src/foundations`, `src/primitives`, `src/patterns`, `src/features`, `src/pages`, `src/shell`, and `src/shared`. Use this skill whenever the user asks to create or change pages, routes, layouts, components, styling, feature UI, or app structure, especially when deciding where code belongs, how dependencies should flow, how to keep routes thin, or how to avoid dumping code into catch-all folders like `components` or `lib`.

Enforce three-layer UI architecture (Foundations → Primitives → Patterns) for React + Tailwind projects. Use this skill whenever the user creates, modifies, reviews, or refactors React components, UI styling, CSS variables, Tailwind tokens, or design system code. Also use when the user asks where a component belongs, how to organize UI code, whether something should be a primitive or pattern, or how to avoid duplication in their component library — even if they don't mention "design system" or "three layers" explicitly.

End-to-end guidance for AppRun apps in TypeScript using MVU including component patterns, event handling, state management (including async generators), routing/navigation with params and guards, and testing with vitest. Use when designing or reviewing AppRun components, wiring routes, managing state flows, or writing AppRun tests.

Use when the user intends to create, initialize, run, continue, route, eval, test, verify, validate, confirm, check, smoke-test, inspect, or debug an Agent World workflow, including requests that mention Agent World, agent-world, agent world, world.json, world.eval.md, or command-like forms such as agent-world: init. Treat command-like forms as natural-language requests, not tool calls.

Answer CRM questions against the live CRM API through scripts/data-tool.js. Use for CRM account, contact, note, action, status, triage, and next-move planning questions in the RLP CRM workspace.

Use this skill for software development tasks that should follow the RPD workflow: requirements, architecture planning, implementation, debugging, tests, E2E checks, code review, commits, done docs, or worktrees. Trigger on natural-language requests for those workflow stages, or when any of these keywords appears with command-like intent: RPD, REQ, AP, AR, SS, DF, DD, ET, TT, CR, VR, GC, WT, !!. The keyword must be surrounded by message boundaries, punctuation, or whitespace. Match examples like `REQ`, `REQ:`, `REQ-`, `REQ,`, `REQ -`, and `'REQ'`. Match middle or end forms like `please REQ: add login` or `ship it SS`. Do not match when a letter, digit, or underscore touches the keyword. Ignore keywords inside fenced code blocks or inline code spans.

Use the converter script to render a MusicXML file to SVG markdown image output.