Skill | Added | Review |
|---|---|---|
git.repo-manager Instructions to manage a local cache of GitHub repositories. This would typically done in cases where the user want to perform research/analysis on a repository. Invoke whenever you need to clone a repo that isn't present locally, bring an existing clone up to date, or remove a repo from the cache. This skill handles only the mechanical filesystem/git operations — not research, analysis, or anything about the repo's contents. | 16 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
research.deprecation-usage Audits how often deprecated CDS exports are actively used in customer codebases using Sourcegraph MCP search tools. Use this skill whenever asked to assess removal readiness for deprecated CDS APIs, investigate the blast radius of removing a deprecated component or hook, check Sourcegraph for customer usage of deprecated exports, or help the team decide which deprecated APIs are safe to remove in the next major version. Always invoke when asked to "audit deprecated APIs", "check Sourcegraph for deprecated usage", "find usages of deprecated exports", "analyze deprecation impact", or any similar request involving CDS deprecations and customer adoption. | 18 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: f79a780 | |
figma.connect-best-practices Guidelines for writing Figma Code Connect property mappings. Use this skill when working on Figma Code Connect files, which typically end in .figma.tsx. | 18 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
cds-code Produces high quality Coinbase Design System (CDS) code for React and React Native projects. Always use this skill every time you are asked to create or update UI or write React or React Native code. | 75 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
cds-docs Retrieve Coinbase Design System (CDS) documentation: setup, installation, theming, tokens, and per-component APIs/examples. Use this skill whenever the task involves CDS components, design-system rules, theming, or choosing between web and mobile CDS packages, even if the user only says "use CDS" or names a component. Always start from the docs route index, then fetch only the pages you need to reason and implement correctly. Prefer the CDS MCP server (`list-cds-routes`, `get-cds-doc`); if MCP is unavailable, use curl against https://cds.coinbase.com/llms/.... | 90 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: f79a780 | |
cds-design-to-code Turns frontend designs from Figma into CDS-first React or React Native code. Use this skill whenever the user shares a Figma URL such as `figma.com/design/...?...node-id=...` while working in a frontend application context. | 86 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: f79a780 | |
ktlo Instructions to fetch assigned Linear issues in the current cycle and potentially kick off a development session. | 66 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
figma.audit-connect Examines a Figma Code Connect mapping file and provides a report on the mapping's accuracy and completeness | 17 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: f79a780 | |
git.detect-breaking-changes Analyzes the previous N commits for breaking changes across the CDS public API surface. Use this skill when you need to check if any recent changes will cause breaking changes in the CDS public API surface. | 16 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
dev.cds-web USE THIS when asked to work on a new or existing (WEB) CDS React component in packages/web | 18 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
components.write-docs Guidelines for creating or updating documentation for a CDS component on the docsite (apps/docs/). Use this skill after creating or making updates to a CDS React component to write high quality documentaiton in the CDS docsite. | 16 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: f79a780 | |
components.best-practices Use this skill whenever working on CDS React components in any package. | 17 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
skill-creator Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | 84 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: f79a780 | |
components.styles Guidelines writing styles API (styles, classNames, and static classNames) for a CDS component. Use this skill when adding customization options to a React component via `styles` or `classNames` props or when needing to update the docsite with component styles documentation. | 17 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
eslint-plugin-custom-rule USE THIS when asked to create a new eslint plugin rule for the eslint-plugin-cds package | 76 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
feature-planner A guided workflow for non-technical contributors (designers, PMs) to describe a feature idea and produce a detailed technical implementation plan for an engineer. Invoke manually with /feature-planner. | 74 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: f79a780 | |
dev.cds-mobile USE THIS when asked to work on a new or existing (MOBILE) CDS React component in packages/mobile | 18 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 | |
deprecate-cds-api Deprecates a CDS component, hook, or other exported symbol with consistent JSDoc, version tags, and docsite metadata across every public export path (web, mobile, common, visualization), not only the original package. Use whenever the user asks to deprecate a CDS component or API, mark something as deprecated, add @deprecated / @deprecationExpectedRemoval, or update deprecation warnings in apps/docs metadata under components or hooks (webMetadata.json / mobileMetadata.json / metadata.json). Also use when replacing a component or hook and sunsetting the old one. Always finish by running `yarn nx run <project>:lint` on modified packages so `internal/deprecated-jsdoc-has-removal-version` passes. | 16 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: f79a780 |