发现 Skills

Guidelines and best practices for writing unit tests in the G2 visualization library, covering directory structure, testing patterns, and implementation guidelines. Use when need to generate test.

Use when the user wants to write a culture-and-arts news piece — exhibition coverage, performance reviews, artist interviews, cultural policy analysis, art-market reporting, or cultural heritage reporting — from supplied material. Activates a culture-beat-specific workflow on top of the general news-reporter workflow: cultural-appropriation audit, indigenous-knowledge protection, source credibility tagging (institutional PR vs. independent critic), aesthetic-judgment marking, and translation/cross-cultural framing discipline. Also triggers on prompts like “draft an exhibition review”, “write up this gallery opening”, “turn into an album review”, “compile exhibition news”, “write a review”, “help me do an artist interview”, “cover this museum exhibition”, “draft a cultural commentary”. Defers general news craft to med-news-reporter; do NOT use for art-marketing copy (use mkt-*) or artist/gallery press releases (use pr-press-release).

Automate Abyssale tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Aryn tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Blocknative tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate headless CMS operations in Contentful — list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration.

Automate Here tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate LaunchDarkly tasks via Rube MCP (Composio): feature flags, environments, segments, and rollout management. Always search tools first for current schemas.

Automate Magnetic tasks via Rube MCP (Composio). Always search tools first for current schemas.

Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.

Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.

Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync. Use when: adding authentication, Clerk auth, user authentication, sign in, sign up.

Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions.

Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.

DNAnexus cloud genomics platform. Build apps/applets, manage data (upload/download), dxpy Python SDK, run workflows, FASTQ/BAM/VCF, for genomics pipeline development and execution.

CLI/Python toolkit for rapid bioinformatics queries. Preferred for quick BLAST searches. Access to 20+ databases: gene info (Ensembl/UniProt), AlphaFold, ARCHS4, Enrichr, OpenTargets, COSMIC, genome downloads. For advanced BLAST/batch processing, use biopython. For multi-database integration, use bioservices.

Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards.

Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.

Use when the user wants to manage project settings, create characters, update worldbuilding entries, view or edit the outline, or check foreshadowing status. Triggers include "new", "character", "worldbuilding", "outline", "foreshadowing", "project".

Screenpipe brand style guide. Reference this when designing UI components, writing copy, or making visual decisions.

UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.

Decide where to place TiDB tests and how to write them (basic structure, naming, testdata usage). Use when asked about test locations, writing conventions, shard_count limits, casetest categorization, or when reviewing test changes in code review.

Analyze Cargo.toml dependencies and attempt to remove unused features to reduce compile times and binary size

Create a simple PR from staged changes with an auto-generated commit message