Loading...
Loading...
Found 2,493 Skills
When the user wants to create a press coverage page, "As Seen In" section, or media mentions aggregation. Also use when the user mentions "press coverage," "media mentions," "as seen in," "as featured in," "in the news," "press mentions," "media coverage page," or "trusted by publications."
Consult this skill when designing storage and documentation systems. Use when organizing knowledge storage, managing configuration lifecycle, creating structured documentation, establishing naming conventions. Do not use when simple storage without lifecycle or structure needs.
[Pragmatic DDD Architecture] Guide for creating DDD Repositories (Interfaces and Infrastructure). Use when creating repository contracts or implementing them using Drizzle ORM, Zod, and Postgres. Enforces completely typed transactions with Drizzle Transaction types (no 'unknown'), Result returns for Railway-oriented programming via neverthrow, and mapping pg node errors to domain errors. Fits our docker-compose / drizzle-kit standard testing workflow.
[Pragmatic DDD Architecture] Guide for creating strictly typed Domain validation and infrastructure errors. Use when handling or creating new errors to ensure they conform to the Railway-oriented programming model (neverthrow Result), TypeScript error branding, and constructor parameter constraints. Covers co-location rules vs. shared domain error usage.
[Pragmatic DDD Architecture] Guide for creating Next.js Server Actions exactly tied to zod, neverthrow, and the domain architecture. Use when creating or editing any file in presentation/actions/. Covers "use server" placement, unknown parameters validated with `zod`, discriminated union response types, auth-first pattern, Value Object validation with TypeScript narrowing, use-case error mapping via `assertNever`, serviceContainer invocation, and revalidation strategy.
[Pragmatic DDD Architecture] Guide for Server and Client components in Next.js App Router. Use when creating any .tsx file under presentation/components/, pages, or layouts — also when deciding whether to add "use client" to an existing component, passing data from a Server Component to a Client Component, composing Server content inside a Client slot, handling the VO serialization boundary, creating Compound Components, separating logic for Mobile/Desktop screens, or styling with `cva` and `cn`. Covers: Server vs Client decision, async Server Component patterns, creating getSession callbacks for Use Cases, Client Component restrictions, toBranded() boundary pattern, children slot composition, and props interface rules. Depends on 'use-cases' and 'server-actions'.
Use when deploying object storage (S3-compatible) to Zeabur. Use when user needs MinIO, RustFS, or S3-compatible storage. Use when user says "object storage", "file storage", "S3", "MinIO", "RustFS", "upload files", "store files", "blob storage", or "OSS". Also use when integrating object storage with an existing service.
Use when the user asks to design RAG pipelines, optimize retrieval strategies, choose embedding models, implement vector search, or build knowledge retrieval systems.
Initiating-coverage report framework — five-step workflow to generate an institutional-grade coverage initiation report: ① company overview ② industry positioning ③ financial modelling ④ valuation analysis ⑤ investment conclusion. Covers business description, competitive advantages, financial health, valuation multiples, price target, and risk factors. Triggers: "首次覆盖", "初始覆盖", "覆盖报告", "研报框架", "投资报告", "建立覆盖", "首次評級", "初始覆蓋", "覆蓋報告", "建立覆蓋", "initiate coverage", "coverage initiation", "first coverage", "equity research report", "investment report", "initiating coverage", "research initiation", "NVDA initiate coverage".
Cloud object storage integration with AWS S3, Azure Blob Storage, and Google Cloud Storage. Covers presigned URLs, multipart uploads, bucket policies, lifecycle rules, and CDN integration. USE WHEN: user mentions "S3", "blob storage", "cloud storage", "object storage", "presigned URL", "file upload to cloud", "GCS", "Azure Blob", "bucket" DO NOT USE FOR: local file uploads - use `file-upload`; database BLOB columns; local filesystem operations
Read-only Storage Analysis Assistant for macOS / Windows (auto-detects system). Scans the entire disk usage to identify space hogs, categorizes each item into three levels: 🟢 Auto-cleanable / 🟡 Manual judgment required / 🔴 Clean with caution, and provides actionable disposal plans. Generates an interactive HTML report with beautiful formatting, collapsible sections, and one-click copy commands. Also supports starting a local service to delete files directly via the web (move to trash / delete immediately). The entire scanning process is read-only. Must be used in the following scenarios: When users mention "storage analysis", "disk full", "C drive/hard disk full", "insufficient space", "clean up space", "disk cleanup", "space occupied", "what's taking up space", "help me check storage", "check computer storage/space", "storage space", "computer space insufficient", "memory full/insufficient" (in Chinese colloquial, "memory" often refers to storage), "storage analysis", "disk cleanup", "clear cache", "disk cleanup"; or when users complain about insufficient computer space, want to know what's taking up hard disk space, or need cleanup suggestions. Note: If users explicitly refer to RAM (e.g., "which process is using memory", "high memory usage", want to see Activity Monitor), that's RAM, not storage, and does not belong to this skill.
Scout, pilot, or review Mirage virtual-filesystem tool use for Workbench agents while preserving source-of-truth and public-safety boundaries.