Loading...
Loading...
Found 1,359 Skills
Use ShadTextarea for multi-line text input; placeholder. ShadTextareaFormField for forms with validation. Use when adding multi-line text fields or bio/description inputs in a Flutter shadcn_ui app.
Build forms with ShadForm, validation, and form field values; use ShadInputFormField, ShadCheckboxFormField, ShadSelectFormField, ShadDatePickerFormField, etc. Use when building validated forms, getting form values, or using dot notation for nested fields in a Flutter shadcn_ui app.
SSH into host `h100_sglang`, enter Docker container `sglang_bbuf`, work in `/sgl-workspace/sglang`, and use the ready H100 remote environment for SGLang development and validation. Use when a task needs remote CUDA work, GPU-backed smoke tests, diffusion checks, or a safe remote copy instead of local-only execution.
Full browser UAT for web apps — Playwright testing with console/network error capture, accessibility checks, i18n validation, and bug triage. Use when running screen-by-screen UAT or testing specific features in any web or hybrid app (React, Vue, Angular, Ionic, Next.js, etc).
Keep status and error colours minimal and consistent — too many semantic colours confuse users. Each colour must mean exactly one thing. Errors should be recoverable, large failures must be prevented, and the UI should always give the user a path forward. Use when designing status indicators, error states, form validation, alerts, or any feedback system.
Scans code for error handling and resilience issues — swallowed exceptions, missing try/catch on external calls, unhandled promise rejections, missing transactions, validation gaps, retry/timeout omissions, and logging blind spots. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "error handling check", "exception audit", "resilience check", "try/catch review", "error handling audit".
Comprehensive guide to Steedos field types and configurations. Fields are defined as .field.yml files in objects/{name}/fields/. Covers text fields, numeric fields (number, currency, percent, autonumber), date/time, boolean/select, relationship fields (lookup, master-detail), computed fields (formula, summary), file/media, and special types. Includes field properties, amis UI customization, visible_on formulas, validation, defaults, and dependencies.
Use when working with CUE kind definitions, schemas, or versioning in grafana-app-sdk projects (app platform apps). This skill should be used when the user asks to "define a kind", "add a CUE kind", "write a kind schema", "create a CUE schema", "model a resource", "add a new resource type", "edit kinds/", "what is a kind in grafana-app-sdk", "add a version to a kind", or asks about CUE kind structure, versioning, schema fields, validation constraints, or the codegen configuration section. Provides guidance on authoring CUE kind definitions for grafana-app-sdk projects.
ProductBurst platform help — product launch and discovery platform for startups with daily and weekly rankings. Covers product submission (launch in under 5 minutes, no gatekeepers), daily/weekly leaderboard rankings (not single-day like Product Hunt), community upvoting, Top of Day/Week badges (shareable SVGs), featured homepage placement (one-time fee), do-follow backlinks (DR46), comment threads, idea validation without a full build, and marketplace. Use when your product isn't getting noticed on launch day, your ProductBurst listing isn't ranking, you need visibility without Product Hunt's gatekeeping, or you want a do-follow backlink from a DR46 directory. Do NOT use for general launch strategy across multiple directories (use /sales-launch-directory), email marketing (use /sales-email-marketing), or audience growth (use /sales-audience-growth).
Check whether a design is complete enough to move into implementation planning. Use when a design appears mostly done and needs a final readiness review for missing branches, weak assumptions, unresolved risks, failure handling, validation gaps, or non-functional omissions. Trigger before invoking writing-plans or when the user asks whether the current design is ready to implement. Do not use as a general design-document audit for external docs or as a replacement for initial design work.
Refine an existing design tree until key branches become implementation-ready. Use when the high-level structure already exists but important branches remain vague, shallow, or unresolved. Trigger when the user needs deeper decomposition, edge-case coverage, failure-path clarification, interface detail, or validation criteria for a partially designed system. Do not use to create the initial design skeleton from scratch or to compare options for a single explicit decision node.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes