Loading...
Loading...
Found 3,042 Skills
Craft CMS 5 front-end Twig development — atomic design, template architecture, component patterns, Vite buildchain. Covers the full site template surface: atoms, molecules, organisms, props/extends/block pattern, layout chains, view routing, content builders, image presets, Tailwind named-key collections, multi-brand CSS tokens, JavaScript boundaries (Alpine/DataStar/Vue), Vite asset loading. Triggers on: {% include ... only %}, {% embed %}, _atoms/, _molecules/, _organisms/, _views/, _builders/, _boilerplate/, component--variant.twig, _component--props.twig, image presets, Tailwind class collections, collect({}), utilities prop, multi-brand theming, data-brand, hero sections, card components, content builders, Matrix block rendering, craft.vite.script, vite.php, vite.config.ts, nystudio107, buildchain, asset loading, per-page scripts. Always use when creating, editing, or reviewing any Craft CMS front-end Twig template, component, layout, view, builder, or buildchain configuration.
Apply when building catalog or SKU synchronization logic for VTEX marketplace seller connectors. Covers the changenotification endpoint, SKU suggestion lifecycle, product data mapping, price and inventory sync, and fulfillment simulation. Use for implementing seller-side catalog integration that pushes SKUs to VTEX marketplaces with proper notification handling and rate-limited batch synchronization.
Provide instructions on how to build with Arc, Circle's blockchain where USDC is the native gas token. Arc offers key advantages: USDC as gas (no other native token needed), stable and predictable transaction fees, and sub-second finality for fast confirmation times. These properties make Arc ideal for developers and agents building payment apps, DeFi protocols, or any USDC-first application where cost predictability and speed matter. Use skill when Arc or Arc Testnet is mentioned, working with any smart contracts related to Arc, configuring Arc in blockchain projects, bridging USDC to Arc via CCTP, or building USDC-first applications. Triggers: Arc, Arc Testnet, USDC gas, deploy to Arc, Arc chain, stable fees, fast finality.
Analyze e-commerce performance using GA4 metrics, conversion funnel analysis, and key e-commerce KPIs. Use this skill when the user needs to evaluate online store performance, diagnose conversion drop-offs, set up e-commerce tracking, or create performance dashboards — even if they say 'why are sales down', 'optimize our online store', 'set up GA4 for e-commerce', or 'what metrics should we track'.
Execute automatic activation for all google vertex ai multimodal operations operations. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
Charlie Munger's Mental Lattice applied to a business idea. Spawns a team of specialist agents — Mathematician, Psychologist, Inverter, Economist, Moat Analyst — who each apply their discipline's elementary models to the idea. The lead synthesizes into a lollapalooza analysis: which forces stack, which fight you, and the honest Munger verdict. Use when the user says "munger this", "apply the lattice", "what would Charlie think", or proposes a business idea and wants multidisciplinary analysis. Works as a standalone analysis or after /office-hours.
Transync AI platform help — real-time AI meeting translation with near-zero latency (<0.5s) dual-screen bilingual display across 60+ languages, AI voice broadcast, AI meeting notes with summaries, custom domain terminology via AI Assistant, system audio sharing (no bot/plugin) for Zoom/Teams/Meet/WhatsApp. Use when setting up Transync AI for multilingual meetings, Transync AI translation accuracy dropping with accents or technical terms, Transync AI dual-screen display not showing translations, Transync AI meeting notes not generating summaries, choosing between Transync AI Personal Premium vs Enterprise plan, Transync AI time card top-up running out mid-meeting, Transync AI voice broadcast not working, or Transync AI vs JotMe or Talo or Langfinity for real-time meeting translation. Do NOT use for general note-taker comparison across all platforms (use /sales-note-taker) or enterprise RSI with human interpreters (use /sales-kudo or /sales-interprefy).
Workbench agent panel system — ef-edit CustomEvent pipeline, registry roll-up, selector grouping, and element property schema. Use when adding new GUI edit capture points, expanding the inspector schema, or continuing development of the EFAgentPanel feature.
Programmatic security management in Neo4j — RBAC/ABAC, user lifecycle (CREATE/ALTER/DROP USER), role lifecycle (CREATE/GRANT ROLE/DROP ROLE), privilege grants and denies (GRANT/DENY/REVOKE on graph, database, DBMS), property-level access control, sub-graph access control, SHOW PRIVILEGES inspection, and auth provider config reference (LDAP, OIDC/SSO). Use when an agent needs to manage users, roles, or privileges programmatically via Cypher on the system database. Does NOT handle Cypher query writing — use neo4j-cypher-skill. Does NOT handle cluster ops or backups — use neo4j-cli-tools-skill. Property-level security and ABAC require Enterprise Edition.
Find composition and state-lifting refactor opportunities in a React codebase. Audits for boolean-prop bloat, monolith components with variant explosion, sibling clusters that should share lego-brick subcomponents, render-prop slots that can't reach outside the box, and state synced between siblings via useEffect. Use when the user wants to improve react code, audit react components, find react refactor opportunities, run a react composition review, or asks "improve react", "audit react", "react architecture review".
Use for tasks that may need brief clarification before implementation but don't warrant a full plan. If clear, dispatches an implementer immediately; if unclear, asks 1-3 questions, proposes an approach, gets approval, then dispatches. No plan file — lighter and faster than nash + stoudemire.
Initialize evo for the current repository by exploring the codebase, proposing unexplored optimization dimensions, constructing the benchmark inside a baseline worktree, and running the first experiment. Use when the user invokes /evo:discover, mentions setting up evo, wants to instrument a codebase for autonomous optimization, or asks to start a new evo run on a project.