Storybook stories 规范
SkillSkillsMP
io.github.storybookjs/storybook/stories
在创建、编辑或删除组件、story、样式、CSS、主题、颜色或设计 token 之前——凡影响 UI 观感的一切——必须最先调用，无一例外。也用于启动或预览 Storybook 验证 UI、展示/浏览/列举组件、story 或 UI 状态的请求，以及文档、props 或用法查询。
source
“Api Integration” 共 907 个结果
io.github.storybookjs/storybook/stories
在创建、编辑或删除组件、story、样式、CSS、主题、颜色或设计 token 之前——凡影响 UI 观感的一切——必须最先调用，无一例外。也用于启动或预览 Storybook 验证 UI、展示/浏览/列举组件、story 或 UI 状态的请求，以及文档、props 或用法查询。
io.github.storybookjs/storybook/stories
在创建、编辑或删除组件、story、样式、CSS、主题、颜色或设计 token 之前——凡影响 UI 观感的一切——必须最先调用，无一例外。也用于启动或预览 Storybook 验证 UI、展示/浏览/列举组件、story 或 UI 状态的请求，以及文档、props 或用法查询。
io.github.mem0ai/mem0/mem0-integrate
以目标驱动、TDD 的流程将 Mem0 集成到现有仓库。自动检测仓库语言,并让用户在 Mem0 Platform(托管)与 Mem0 开源(自托管)之间选择。先写失败测试再做实现。产出本地功能分支和供配套验证技能使用的 .mem0-integration/ 产物。触发条件:用户说 "integrate mem0"、"add mem0 to this repo"、"wire mem0 into <repo>",或询问如何在现有项目中加入记忆。不触发:一般 SDK 使用(用 skill:mem0)、CLI 使用(用 mem0-cli)、Vercel AI SDK(用 skill:mem0-vercel-ai-sdk)。成功后调用 skill:mem0-test-integration 在同一工作区验证(松耦合)。
io.github.mem0ai/mem0/mem0-cli
Mem0 CLI——mem0 记忆操作的命令行界面。触发条件:用户提到 "mem0 cli"、"mem0 command line"、"@mem0/cli"、"mem0-cli"、"pip install mem0-cli"、"npm install -g @mem0/cli",或在终端/shell 中运行 mem0 命令(mem0 add、mem0 search、mem0 list、mem0 get、mem0 init、mem0 config、mem0 import)。查询包含 --user-id、--output、--json、--agent 等 CLI 参数,或描述 bash/zsh/终端使用时也触发。不触发:Python/TS 代码中的 SDK 集成(用 mem0 技能),或 Vercel AI SDK provider(用 mem0-vercel-ai-sdk)。
io.github.mem0ai/mem0/mem0-oss-to-platform
制定并执行将项目从 mem0 开源/自托管 SDK(本地 Memory 类)迁移到 mem0 Platform 托管 SDK(MemoryClient 类)的方案。当开发者想把 mem0 从 OSS/自托管迁移到托管 API 时使用,例如"把 mem0 设置迁移到平台""从自托管 mem0 切换到 MemoryClient""改用 mem0 API key 而非本地 Qdrant""把 mem0 迁到云端/托管服务""用平台配置替换本地向量库+嵌入器配置"。适用于 Python(from mem0 import Memory → from mem0 import MemoryClient)和 TypeScript/JavaScript(import { Memory } from "mem0ai/oss" → import MemoryClient from "mem0ai")。即使用户没说"迁移"二字,但明显希望现有 mem0 集成改为访问托管平台时也应触发。先产出可审阅的迁移计划,经开发者确认后执行。
io.github.browser-use/browser-use/open-source
基于 browser-use 开源库编写 Python 代码的文档参考。凡涉及 Agent、Browser、Tools 配置、导入 browser_use 的代码、@sandbox 部署、支持的 LLM 模型、Actor API、自定义 tools、lifecycle hooks、MCP 服务器搭建、Laminar 或 OpenLIT 监控/可观测性，以及 browser-use 安装、prompt 策略、敏感数据处理时都适用。不适用于 Cloud API/SDK 用法与定价——用 cloud skill；也不适用于通过 CLI 命令直接驱动浏览器——用 browser-use skill。
io.github.thedaviddias/Front-End-Checklist/contract-testing
为前后端 API 边界搭建集成测试、评估两个服务能否独立安全部署，或用契约测试替换缓慢的端到端测试时使用。
io.github.asgeirtj/system_prompts_leaks/requirements-clarification
Clarify a material user-owned product decision before substantive implementation commitments. Use only when request and named/governing evidence still leave a choice that would materially change scope, platform support, user-facing surface, data/API contract, domain values, project placement, or cross-system architecture; also use when a truncated request omits such a choice. On the initial turn, inspect only named or governing requirements evidence, then ask directly without loading: prefer structured input; ask one blocking outcome question or at most three coupled questions; wait. After the answer, load the body before write or delegation. Do not use for implement/build/fix/debug/refactor work when expected behavior is settled, plan/design deliverables owned by Plan, complexity/greenfield/integration alone, agent-owned technical choices, locally discoverable facts, reversible defaults, permission to begin, or stop/no-tool turns. Never re-ask supplied facts or turn clarification into refusal.
io.github.The-Vibe-Company/quivr/mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
io.github.coreyhaines31/marketingskills/sms
当用户想规划、搭建或优化短信/MMS 营销时使用，包括欢迎流程、购物车挽回、购后触达、流失挽回、促销群发或验证码类事务短信。用户提到 SMS marketing、text message campaigns、SMS sequence、SMS automation、abandoned cart text、post-purchase SMS、Klaviyo SMS、Postscript、Attentive、Twilio、A2P 10DLC、TCPA、SMS compliance、short code、toll-free SMS、MMS campaign、“要不要做短信”或“SMS vs email”等场景时也适用。邮件序列见 emails，短信文案框架见 copywriting，采集手机号的弹窗见 popups。
io.github.affaan-m/ECC/change-impact
Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths, data and schema, API contracts, tests, documentation, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.
io.github.affaan-m/ECC/change-impact
Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths, data and schema, API contracts, tests, documentation, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.
io.github.K-Dense-AI/scientific-agent-skills/pylabrobot
开发和审查 PyLabRobot 实验室自动化资源、液体处理方案、离线仿真与受支持设备集成。用于 PyLabRobot 协议或 API 相关问题；物理执行必须置于显式的操作员安全门之后。
io.github.K-Dense-AI/scientific-agent-skills/rowan
Rowan 是带 Python API 的云原生分子建模与药物化学工作流平台。适用于 pKa 与大分子 pKa 预测、构象与互变异构体系综、对接与类似物对接、蛋白-配体共折叠、MSA 生成、分子动力学、通透性、描述符工作流，以及相关的小分子或蛋白建模任务。适合程序化批量筛选、多步化学流水线，以及原本需要自建 HPC/GPU 基础设施的工作流。
io.github.K-Dense-AI/scientific-agent-skills/pyzotero
使用 pyzotero Python 客户端操作 Zotero 参考文献库。通过 Zotero Web API v3 检索、创建、更新和删除条目、合集、标签与附件。适用于以编程方式操作 Zotero 文库、管理文献引用、导出引文、检索文库内容、上传 PDF 附件，或构建与 Zotero 集成的科研自动化工作流。
io.github.K-Dense-AI/scientific-agent-skills/adaptyv
如何使用 Adaptyv Bio Foundry API 与 Python SDK 进行蛋白实验设计、提交与结果获取。只要用户提到 Adaptyv、Foundry API、蛋白结合实验、蛋白筛选实验、BLI/SPR 实验、热稳定性实验，或想提交蛋白序列进行实验表征，就使用本技能。当代码导入 `adaptyv`、`adaptyv_sdk`、`FoundryClient`，或引用 `foundry-api-public.adaptyvbio.com` 时也应触发。
io.github.K-Dense-AI/scientific-agent-skills/zarr-python
用于云存储的分块 N 维数组（Zarr-Python 3）。压缩数组、并行 I/O、经 fsspec 访问 S3/GCS、兼容 NumPy/Dask/Xarray，适用于大规模科学计算流水线。
io.github.coollabsio/coolify/tailwindcss-development
用户消息以任何形式包含 'tailwind' 时始终调用。还适用于:构建响应式栅格布局(多列卡片栅格、商品栅格)、flex/grid 页面结构(带侧边栏的仪表盘、固定顶栏、移动端可折叠导航)、UI 组件样式(卡片、表格、导航栏、价格区、表单、输入框、徽章)、添加暗色模式变体、修复间距或排版,以及 Tailwind v3/v4 工作。核心场景:在 HTML 模板(Blade、JSX、Vue)中编写或修正 Tailwind 工具类。跳过:后端 PHP 逻辑、数据库查询、API 路由、无 HTML/CSS 部分的 JavaScript、CSS 文件审计、构建工具配置和原生 CSS。
io.github.airbytehq/airbyte/source-snowflake-e2e-tests
Run the Airbyte protocol sweep for airbyte/source-snowflake:<tag> against the shared Snowflake integration account inside a per-run PROVEFIX_<run_id> schema (B3 remote-backend mode of db-harness-lib); prove-fix comparisons, cursor canary, orphan sweep.
io.github.affaan-m/ECC/gateguard
面向 API、智能体与 LLM 端点的访问控制与授权模式。
io.github.affaan-m/ECC/ml-adoption-playbook
End-to-end methodology for AI agents and software engineers to add machine learning algorithms to existing non-ML codebases. Covers problem framing, data readiness, architectural decoupling, and baseline model integration. Use when adding a machine learning capability to a codebase that has none, from problem framing through a baseline model.
io.github.affaan-m/ECC/contract-first
Coordinate frontend/backend or service-to-service work through one authoritative machine-checkable contract (OpenAPI, AsyncAPI, Protocol Buffers, or JSON Schema), with generated consumer types and contract-verified integration. Use when parallel consumer and provider work must evolve an API or event schema without field drift, mock/production shape mismatch, or one side silently redefining the interface.
io.github.affaan-m/ECC/intent-driven-development
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
io.github.affaan-m/ECC/springboot-verification
Run the full Spring Boot verification loop — Maven or Gradle build, SpotBugs, PMD, and Checkstyle static analysis, unit and Testcontainers integration tests with JaCoCo coverage, OWASP dependency and secret scans, and diff review — producing a pass/fail readiness report. Use when preparing a Spring Boot pull request, validating coverage thresholds, or running pre-deploy verification.