yysun
- 22 skills
- 0 followers
- last month last updated
- ▌ Git Wiki 2 · yysun bundleBuild 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.
- ▌ Rpd · yysunRun or explain the RPD development workflow. Use for ordinary repository work and command-like invocations of RPD, REQ, AP, AR, SS, TT, ET, CR, VR, DD, GC, or !!.
- ▌ Agent World · yysun bundleUse 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, or to open, launch, or start Agent World Studio (a local visual workflow editor and observer), including requests that mention Agent World, agent-world, agent world, world.json, world.eval.md, Studio, agent-world studio, or command-like forms such as agent-world: init or agent-world: studio. Treat command-like forms as natural-language requests, not tool calls.
- ▌ Apprun · yysun bundleAppRun architecture guidance for building, reviewing, or fixing AppRun applications and the AppRun library itself. Use when work involves AppRun MVU components, state/update lifecycles, async generators, event directives, routing and navigation guards, custom elements, or AppRun test coverage. Focus on AppRun behavior and existing repo contracts, not generic build-tool, CSS-framework, or starter-app setup.
- ▌ Audit UI Design · yysun bundleAudit existing UI designs and implemented interfaces using evidence from screenshots, images, Figma exports, live URLs, local frontends, or multi-screen flows. Use when Codex needs to critique visual interface quality, find and prioritize design problems, compare UI variants, review hierarchy/layout/color/typography/consistency, reduce interaction cost, recommend concrete fixes, or recheck a design after changes. This is a UI design audit, not a substitute for user research or a complete accessibility conformance review.
- ▌ Audit UI Ops · yysun bundleAudit how difficult it is to complete a plain-language business operation through a visible UI. Use for fresh-user operational UX audits and controlled UI comparisons that need verified outcomes, interaction traces, and complexity metrics; do not use for visual design critique, scripted E2E testing, or API automation.
- ▌ Azure Devops Pr Review · yysun bundleReview an Azure DevOps pull request by numeric PR ID from its checked-out source branch, deriving the exact target branch from Azure DevOps metadata and using its merge base with HEAD, then automatically publish the completed final review as PR comments after verifying the reviewed commit was pushed and all publishing gates pass. Use when asked to inspect, audit, or code-review an Azure DevOps PR for actionable defects.
- ▌ Rlp Crm · yysun bundleAnswer 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.
- ▌ React Architect · yysunEnforce 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.
- ▌ React Tailwind Layered Web · yysunBuild, 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`.
- ▌ Test Manager · yysun bundleManage QA strategy, suites, cases, test execution, evidence, defects, traceability, and release gates as folder-native state under the current workspace's .tests directory. Use for testing work and quality decisions; do not use for product-delivery coordination, .projects state, standalone operational UX audits, or implementing product fixes unless separately requested.
- ▌ Project Manager · yysun bundlePlan, coordinate, execute, track, review, and report product-delivery work as folder-native .projects state. Use to manage outcomes, tasks, dependencies, blockers, evidence, executors, impact, and stakeholder reporting; do not use for QA suite, case, or run management under .tests.
- ▌ Git Wiki · yysun bundleBuild 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.
- ▌ React App · yysunUse 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.
- ▌ Notebooklm · yysunUse this skill for NotebookLM tasks to create notebooks, add sources, query content, and generate artifacts through the NotebookLM CLI.
- ▌ Story Deck · yysun bundleUse 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.
- ▌ AI Workspace · yysun bundleCreate, 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.
- ▌ Music To Svg · yysun bundleUse the converter script to render a MusicXML file to SVG markdown image output.
- ▌ Playwright CLI · yysun bundleAutomates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
- ▌ Youtube Search · yysun bundleUse this skill when the user asks to search YouTube or find videos by keyword. Trigger on phrases like "search youtube", "find on youtube", "look up on youtube", or when the user provides search keywords and wants YouTube results. Always use this skill for YouTube searches.
- ▌ Workspace Design · yysun bundleDesign 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.
- ▌ Apprun Skills · yysun bundleEnd-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.