Loading...
Loading...
Found 1,178 Skills
配置 VS Code Claude Code 插件免登录直接使用。自动同步 Claude CLI 配置到 VS Code 插件，解决 spawn EPERM 问题。
Clinic-architecture-aligned iOS animation craft guidelines for SwiftUI (iOS 26 / Swift 6.2) covering motion tokens, spring physics, gesture continuity, spatial transitions, micro-interactions, and accessibility. Enforces @Equatable on animated views and keeps animation state aligned with Domain/Data feature boundaries. Use when writing, reviewing, or refactoring SwiftUI animation code under the clinic modular MVVM-C architecture.
MindOS is the user's local knowledge assistant and shared knowledge base. It keeps decisions, meeting notes, SOPs, debugging lessons, architecture choices, research findings, and preferences available across sessions and agents. 更新笔记, 搜索知识库, 整理文件, 执行SOP/工作流, 复盘, 追加CSV, 跨Agent交接, 路由非结构化输入到对应文件, 提炼经验, 同步关联文档. NOT for editing app source, project docs, or paths outside the KB. Core concepts: Space, Instruction (INSTRUCTION.md), Skill (SKILL.md); notes can embody both. Trigger on: save or record anything, search for prior notes or context, update or edit a file, organize notes, run a workflow or SOP, capture decisions, append rows to a table or CSV, hand off context to another agent, check if something was discussed before, look up a past decision, distill lessons learned, prepare context for a meeting, quick-capture to staging area, organize inbox, check knowledge health, detect conflicts or contradictions, find stale content. Chinese triggers: 帮我记下来, 搜一下笔记, 更新知识库, 整理文件, 复盘, 提炼经验, 保存, 记录, 交接, 查一下之前的, 有没有相关笔记, 把这个存起来, 放到暂存台, 整理暂存台, 知识健康检查, 检测知识冲突. Proactive behavior — do not wait for the user to mention MindOS: (1) When user's question implies stored context may exist (past decisions, previous discussions, meeting records) → search MindOS first, even if they don't explicitly mention it. (2) After completing valuable work (bug fixed, decision made, lesson learned, architecture chosen, meeting summarized) → offer to save it to MindOS for future reference. (3) After a long or multi-topic conversation → suggest persisting key decisions and context.
Daniel Kahneman's Cognitive Diagnostic applied to a decision, strategy, or business evaluation. Spawns a team of specialist agents — System Detector, Substitution Mapper, Prospect Theorist, Noise Auditor, Outside Viewer — who each apply a different lens from Kahneman's cognitive architecture to audit the decision for bias, noise, and cognitive traps. The lead synthesizes into a contamination assessment: which cognitive systems are operating, which substitutions are active, and whether the decision should proceed, be corrected, or be restructured. Use when the user says "kahneman this", "check my thinking", "am I biased", "audit this decision", "what am I missing", or presents any decision, strategy, or evaluation they want cognitively stress-tested. Works standalone or as a companion to /munger (Munger evaluates the business; Kahneman audits the thinking about the business).
Self-correcting outreach loop using Exa Websets, Notion, direct Gmail SMTP, and IMAP audit. Defaults to Oulang.ai VC pre-seed raise plus Spanish-Chinese diaspora partnerships, parameterizable for any campaign. Triggers on "next wave", "audit replies", "find more investors", "outreach wave", "follow up unreplied", "fix the previous batch".
MUST activate when the user wants to build, create, or generate a React application, React app, web application, single-page application (SPA), or frontend application — even if no project files exist yet. MUST also activate when the project contains a uiBundles/*/src/ directory or sfdx-project.json and the prompt says create, build, construct, or generate a new app, site, or page from scratch — even if the prompt also describes visual styling. MUST also activate when the task spans more than one ui-bundle skill. Use this skill when building a complete app end-to-end. This is the orchestrator that coordinates scaffolding, features, data access, frontend UI, integrations, and deployment in the correct dependency order. Without it, phases execute out of order and the app breaks. Do NOT use for Lightning Experience apps with custom objects (use generating-lightning-app). Do NOT use for single-concern edits to an existing page (use building-ui-bundle-frontend).
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.
Chinese Documentation Formatting Reference – Rules for spaces between Chinese and English, full-width/half-width punctuation, term retention, link formatting, and conventions from the Chinese Copywriting Guidelines. Only invoke when the user explicitly uses /chinese-documentation; do not trigger automatically based on context.
The canonical rulebook of UI craft and feel. Every element must earn its place and do its one job well; the surface must be tight, clean, calm, and genuinely pleasant to use. The single source of truth that landing-audit grades against and that shipit checks touched UI files against before commit. Use when building or editing ANY user-facing UI, page, screen, hero, or component, or when the user mentions design, layout, hierarchy, typography, color, spacing, contrast, CTAs, or micro-interactions.
Route a full Blazor work request across the appropriate specialist lane(s). Use when the request spans more than one concern (authoring, data, auth, review) or when lane selection itself is uncertain. Triggers on full-request phrasing: "implement this feature", "review and refactor this page", "build this form end-to-end". Distinct from blazor-component-architect (user-level, external, single-lane authoring guidance that may be invoked as a specialist resource).
Expert-level Rust performance optimization guidelines for build profiles, allocation, synchronization, async/await, and I/O. This skill should be used when writing, reviewing, or optimizing Rust code for performance. Triggers on tasks involving slow Rust code, large binary size, long compile times, LTO configuration, release profile tuning, allocation reduction, clone avoidance, lock contention, BufReader/BufWriter, flamegraph analysis, async runtime issues, Tokio performance, spawn_blocking, parking_lot vs std sync, or any Rust performance investigation.
Allows reading the decompiled C# code of Space Engineers version 1