Loading...
Loading...
Found 2,162 Skills
Use when the user is calling or debugging Spree 6's REST API v3 — the Store API (storefronts, mobile apps, customers), the Admin API (integrations, back-office tools) or the Seller API (marketplace sellers). Covers auth (publishable/secret keys, JWT audiences), scopes and permissions, prefixed IDs, the cart → order split, checkout `requirements[]`, order statuses, the `{data, meta}` envelope, expand/fields, Ransack filters, errors, idempotency, localization headers and rate limits. Common phrasings include "Spree API", "Store API", "Admin API", "publishable key", "secret key", "X-Spree-Api-Key", "X-Spree-Token", "API scopes", "403 required_scope", "cart_ vs or_", "complete cart", "cart 404 after checkout", "prefixed IDs", "expand", "Idempotency-Key", "429 rate limit", "v3 endpoint". For ADDING a new endpoint use spree-resource; for roles/permissions internals use spree-auth-permissions.
End-to-end web scraping workflow — from URL to working spider with web-poet page objects. Use this for full-site or multiple-page crawls that create a new scraping workflow. Do not use for fixing, debugging, or modifying an existing spider.
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses, failures, discrepancies. Covers Concurrent Agreements (CustomerAWSAccountId + LicenseArn), multi-product, CloudTrail Event History (90 days; never CloudTrail Lake), Seller Reports (Billed Revenue/Usage columns + CSV/SDDS parsing), existing-stack detection, metering region for BatchMeterUsage/MeterUsage (DisabledApiException), metered AMI/Container + IAM roles, where registration data lives (customer-profile table), legacy ProductCode + CustomerIdentifier, DuplicateRecord/CustomerNotSubscribed, bad LicenseArn. Also SCOPES adjacent asks — flat-rate/SaaS-Subscription "do I still meter", CCP included-units + overage, contract term/annual renewal, forecasting future bills/usage — with the right answer or a one-line redirect. Use for any BatchMeterUsage/ResolveCustomer or SaaS usage-billing question.
Your EYES into the user's live Chrome browser and Electron apps. This skill lets you SEE and INTERACT with the user's actual browser or Electron app — their open tabs, logged-in sessions, and live page state. You MUST use this whenever the user's request involves browser content or Electron app inspection in ANY way. TRIGGER THIS SKILL when the user: - References pages they have open: 'I have X open', 'my tabs', 'open tabs' - Asks to look at, compare, or analyze anything in their browser: 'compare these pages', 'which looks better', 'check this page' - Mentions UI/visual analysis of live pages: 'dashboard', 'UI', 'layout', 'design quality' - Asks for screenshots or page inspection: screenshot, inspect, debug, check the page - Refers to 'the page', 'the browser', 'my tab' in any context - Mentions console errors, page state, or anything requiring browser access - Mentions Electron apps or CDP connections: 'Electron', 'electron app', 'CDP', 'CDP_PORT', 'DevTools Protocol', 'desktop app', 'remote-debugging-port' CRITICAL: NEVER say you cannot see the user's browser or ask users to paste screenshots. You CAN see their browser through this skill. Use `list` to discover open tabs, then `perceive` or `shot` to see page content. Do NOT use Playwright — it launches an isolated browser without the user's login state, cookies, or open tabs.
zkLogin on Sui — architecture, protocol flow, integration, and security. Use when explaining how zkLogin works, integrating zkLogin into a Sui application, choosing an OpenID provider, understanding the address derivation scheme, debugging session lifetime or proof issues, or answering questions about zkLogin security properties (salt, ephemeral keys, JWT privacy). Also use when the user asks about OAuth-based wallet-less login on Sui.
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized Agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from a single current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and also on clear knowledge-closeout intent without the name: syncing or tidying project docs/rules/memory after development ("把文档和记忆整理一下", "收尾时把文档同步掉", "docs 和代码对不上了"), stale or conflicting CLAUDE.md/memory, a clean handoff to a teammate or a fresh session, or auditing whether workspace rules are actually followed. Do not trigger for pure coding/refactoring/debugging tasks, tidying data or prose (JSON, weekly reports, changelog announcements), or a bare "整理" with no project-knowledge context.
Container and deployment standards for FastAPI and Python API services - multi-stage Dockerfiles, .dockerignore, uvicorn behind a proxy, healthchecks, migrations, secrets, hardening, image scanning, and Compose with Postgres. Use when writing, reviewing or debugging any of these, when containerizing or deploying a Python API, or when a container exits, fails health checks or shows CVEs, even if the user never says "Docker".
Creates, modifies and debugs Infrahub transforms that convert data into JSON, text, CSV, or device configs using Python or Jinja2 templates, with YAML-driven tests. TRIGGER when: building config generation, data export, format conversion, Jinja2 templates, artifact pipelines, writing or running tests for a transform, modifying or extending an existing transform or template, debugging why a transform renders the wrong output or an artifact fails to generate. DO NOT TRIGGER when: designing schemas, writing validation checks, creating generators, querying live data.
Type-safe routing guidance for navigation, URL state, data loading, authentication, SSR, and framework adapters. Use when a project uses TanStack Router or when the task needs its setup, implementation, debugging, testing, migration, or integration guidance.
Design, build, evaluate and harden production RAG systems in Python (LangGraph, Qdrant, FastAPI, RAGAS). Use for document Q&A assistants, enterprise knowledge bases, hybrid retrieval, citations/grounding, RAG evaluation, or debugging a RAG app that hallucinates or retrieves badly.
ArcGIS Maps SDK for JavaScript (@arcgis/core, @arcgis/*-components, @arcgis/create) skill for frontend application development, and its public documentation. Use when building, designing, configuring, debugging, upgrading, or explaining an app that uses the SDK - including Core API modules, web components/custom elements, widgets, maps, scenes, link charts, layers, graphics, popups, Arcade, geometry operators, queries/SQL, utility network, CIMSymbols, authentication, routing, editing, guides, tutorials, samples, references, release notes, or app templates.
Teaches Infrahub concepts (schema, objects, branches, proposed changes, checks, transforms, generators, menus) from wherever the learner is, using their own repo files and live instance as lesson material. TRIGGER when: the user wants to learn or understand an Infrahub concept, asks "teach me", "explain how X works in my instance", "I'm new to Infrahub", asks what the equivalent of a NetBox/Nautobot concept is in Infrahub, wants a guided tour, or wants to resume a learning session. DO NOT TRIGGER when: the user wants the work done for them (use the infrahub-managing-* skills), wants live operational answers (use infrahub-analyzing-data), or is debugging a failure (use infrahub-collecting-diagnostics).