Loading...
Loading...
Found 762 Skills
Self-hosted web dashboard for managing Hermes AI agent stacks with terminals, file explorer, multi-agent gateway, and RBAC
End-to-end RevenueCat integration — sets up the dashboard side via the RevenueCat MCP (project, app, public API key) and installs/configures the Purchases SDK in the app. Use when the user asks to add RevenueCat, integrate Purchases, install the RevenueCat SDK, set up a RevenueCat API key, configure Purchases on launch, or set up a brand new RevenueCat integration on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.
SaaS application template using the Partnership model. AI proposes complete vision based on proven SaaS patterns (auth, dashboard, core features, settings), then you provide context. Perfect for web applications requiring user accounts and core functionality.
freeCodeCamp's "Command-line Chic" UI design system and aesthetic guidelines. Apply these rules whenever building, styling, or reviewing any UI that should look and feel like a freeCodeCamp product — web apps, dashboards, landing pages, admin tools, component libraries, or themes. Use this skill when the user mentions freeCodeCamp styling, fCC design, "Command-line Chic", dark theme development for fCC, or asks for a UI that follows freeCodeCamp's visual identity. Also use when working on any freeCodeCamp repository, contributing to freeCodeCamp projects, or building tools and dashboards for freeCodeCamp staff, even if the user doesn't explicitly mention the design system.
Create dynamic, queryable dashboard views of the Obsidian vault using Obsidian Bases — a native Obsidian feature that turns vault frontmatter into interactive tables, card galleries, and lists. Use this skill when the user says "create a dashboard", "vault dashboard", "show all X as a table", "dynamic view", "query my vault", "build a content index", "show me all concepts/entities/projects", or wants a structured, auto-updating view of their wiki content. Requires Obsidian 1.8+ (Bases is a core plugin, no external install needed).
Operate Teable bases — tables, fields, views, records, SQL queries, automations, apps, and web scraping. Trigger when user mentions Cuppy, Teable, teable CLI, or Teable-style IDs (bseXXX, tblXXX, fldXXX, recXXX, viwXXX), or wants to manage tables/fields/records, build dashboards/apps, generate charts, create automations, import/export data, trigger AI fill, or scrape websites (LinkedIn, Amazon, YouTube, etc.) — even if they don't explicitly say "Teable" but are clearly working with a Teable base.
Design the structural anatomy of screens at wireframe fidelity — what goes where and why, before anyone argues about how it looks. Part of the Intent design strategy system. Produces lo-fi idea boards for divergent exploration, complete interactive grayscale wireframes with real labels and real hierarchy, and click-through prototypes that materialize flow logic from /journey. Trigger on: wireframe, wireframes, wireframing, thumbnails, "sketch the screen", "lay out this page", "what goes where on this screen", screen layout, page structure, lo-fi, mid-fi, click-through prototype, wireflow, "wireframe the dashboard", or any request to design the structure of a screen before its visual design. The flow through screens belongs to /journey; the information structure belongs to /organize; the words belong to /articulate — this skill owns the screen itself.
Comprehensive design elevation system that automatically transforms functional visual outputs into polished, professional designs. Use when creating ANY visual output including presentations (pptx), spreadsheets (xlsx), dashboards, reports, HTML artifacts, PDFs, web pages, or data visualizations. Applies systematic design thinking grounded in Tailwind CSS as the canonical design token system. Structures decisions through functional patterns (what users interact with) and perceptual patterns (how the design feels), following Alla Kholmatova's design systems framework. Triggers on ALL requests for visual content creation, ensuring outputs look hand-crafted rather than template-based.
This skill should be used when the user asks about Stripe Connect configuration, charge patterns, dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (e.g. POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants/sellers/vendors, mentions connected account dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.
Plan complex Blazor UI features by decomposing them into focused components. USE FOR: building a complex Blazor page with multiple sections, planning component decomposition, designing a multi-section dashboard or layout, breaking down a large UI feature into composable components, pages with sidebars and content panels, any page with 3+ distinct visual sections or multiple interacting sub-features, identifying parent-child relationships and data flow. DO NOT USE FOR: creating new Blazor projects or apps from scratch (use create-blazor-project), implementing a single individual component (use author-component), writing component code with parameters and EventCallback (use author-component), or simple single-component pages.
Generates Google Cloud Monitoring Server-Driven UI (SDUI) Widget and XyChart Protocol Buffer textprotos from resolved PromQL queries. Use when: - Generating valid google.monitoring.dashboard.v1.Widget textprotos, containing PrometheusQuery datasets, for use with the Cloud Monitoring Dashboards API, gcloud CLI, or declarative dashboard definitions. - Synthesizing Server-Driven UI (SDUI) widget titles, axis labels, and plot types for Prometheus queries. Don't use for: - Metric discovery or PromQL query generation. For those tasks, use the cloud-monitoring-metric-selection or cloud-monitoring-promql-query skills.
.NET Aspire for cloud-native orchestration. Covers AppHost configuration, service defaults, resource configuration, service discovery, and the Aspire dashboard. Load this skill when setting up local development orchestration, service discovery, or Aspire-managed infrastructure, or when the user mentions "Aspire", "AppHost", "service defaults", "service discovery", "orchestration", "Aspire dashboard", "AddProject", "WithReference", or "cloud-native .NET".