Loading...
Loading...
Found 579 Skills
Yoast SEO platform help — the most widely used WordPress SEO plugin (13M+ installs) with a Shopify app. Covers content analysis, readability scoring, focus keyphrase optimization, schema/structured data output, redirect manager, internal linking suggestions, AI-generated meta descriptions, llms.txt for AI search, REST API for headless WordPress, and WooCommerce product SEO. Use when Yoast readability or SEO score won't turn green, schema markup isn't showing in Google Search Console, your site slowed down after installing Yoast, you need to set Yoast fields via REST API for headless publishing, Yoast update caused a critical error, or you want to configure Yoast for Shopify. Do NOT use for general SEO strategy without Yoast context (use /seo-audit or /sales-semrush).
MSW 아바타 코스튬 관리. 코스튬 조회/적용, CostumeManagerComponent 17슬롯, 아바타 유틸리티. DefaultPlayer뿐 아니라 모든 엔티티(NPC, 몬스터 등)에 적용 가능. Use for avatar costume get/set, CostumeManagerComponent 17 equip slots, avatar utilities. Keywords: costume, avatar, equip, slot, 코스튬, 아바타, 장비, 꾸미기, 모자, 상의, 하의, 무기.
Corporate event-driven analysis via Longbridge Securities — captures and classifies events that create pricing dislocations: major-shareholder increases/decreases, equity incentives, private placements, rights issues, buybacks, M&A/restructuring, index rebalancing, and management changes. Combines filings, corporate actions, and shareholder data to produce event signals. Triggers: "公司事件", "事件驱动", "大股东增持", "大股东减持", "股权激励", "定增", "配股", "回购", "并购重组", "指数调整", "管理层变更", "公告分析", "公司事件", "事件驅動", "大股東增持", "大股東減持", "股權激勵", "定增", "配股", "回購", "並購重組", "指數調整", "corporate event", "event-driven", "share buyback", "equity incentive", "major shareholder increase", "rights issue", "M&A arbitrage", "index rebalancing", "insider buying", "corporate action analysis".
UX critique — hierarchy, clarity, anti-slop. No code changes unless asked. Invoke when the user asks for critique on their UI, or mentions 'critique' alongside design / UI / frontend work.
Top-level workflow skill for USD performance diagnosis and optimization. Use for slow loading, high memory, low FPS, or 'optimize my scene' requests; delegates auth/runtime setup to Phase 0 owners.
Use whenever researching a technical question — a library, tool, API, error, version, or "what's the best way to X" — or whenever you're about to answer from memory. Forces multiple real searches over primary sources (official docs, source code, high-vote Stack Overflow, maintainer blogs) instead of one search plus training-data filler, and rejects SEO content-farm slop. Trigger on "research X", "look into", "what's the best library for", "how does X work", "is this still true", "find out".
Use when build times are slow, investigating build performance, analyzing Build Timeline, identifying type checking bottlenecks, enabling compilation caching, or optimizing incremental builds - comprehensive build optimization workflows including Xcode 26 compilation caching
Use when designing or reviewing concurrent Python code — selecting between asyncio, threads, or multiprocessing; structuring cancellation and deadline propagation; bounding fan-out and backpressure. Also use when diagnosing race conditions, deadlocks, slow throughput, or thread/task leaks under load.
Create distinctive, bold UI designs that avoid generic AI aesthetics. This skill should be used when users want frontend components with strong visual identity, creative typography, intentional color palettes, and production-grade animations - specifically to avoid the bland, safe, homogeneous "AI slop" that plagues most generated interfaces.
Diagnose ClickHouse disk usage, compression efficiency, part sizes, and storage bottlenecks. Use for disk space issues and slow IO.
Optimize React apps for 60fps performance. Implements memoization, virtualization, code splitting, bundle optimization. Use for slow renders, large lists, bundle bloat. Activate on "React performance", "slow render", "useMemo", "bundle size", "virtualization". NOT for backend optimization, non-React frameworks, or premature optimization.
Optimize Ollama configuration for maximum performance on the current machine. Use when asked to "optimize Ollama", "configure Ollama", "speed up Ollama", "tune LLM performance", "setup local LLM", "fix Ollama performance", "Ollama running slow", or when users want to maximize inference speed, reduce memory usage, or select appropriate models for their hardware. Analyzes system hardware (GPU, RAM, CPU) and provides tailored recommendations.