From e292e487f414cc640221507ce8958f29bf867898 Mon Sep 17 00:00:00 2001 From: Duggan Burke Date: Wed, 8 Jul 2026 20:26:42 -0700 Subject: [PATCH 1/2] docs: narrow cds-code skill trigger Co-authored-by: Codex --- skills/cds-code/SKILL.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/skills/cds-code/SKILL.md b/skills/cds-code/SKILL.md index 0c8e617761..24bf4ce3d5 100644 --- a/skills/cds-code/SKILL.md +++ b/skills/cds-code/SKILL.md @@ -1,11 +1,13 @@ --- name: cds-code description: | - Provides a structured workflow for writing high quality Coinbase Design System (CDS) code. - Use this skill every time you are asked to create or update a user interface using React or React Native. - Additinoally, this skill may be used to conduct a code review on existing code for CDS adherence. - Trigger examples: "build this screen", "update this component", "perform a CDS audit on our changes", - "check our codebase for CDS adherence", "does this feature use CDS well?" + Provides a structured workflow for writing and reviewing high quality Coinbase Design System (CDS) presentation code. + Use this skill when a request changes rendered React or React Native UI presentation or CDS usage. + Examples include CDS component choices, JSX layout or structure, spacing, color, typography, icons, illustrations, images, loading states, empty states, error states, interactive control accessibility labels, or user-facing copy. + Use this skill for explicit CDS audits, reviews, or adherence checks. + Do not use this skill for logic-only changes, hooks, tests, Relay or data fetching, analytics, navigation wiring, feature flags, generated artifacts, performance-only refactors, or edits in component files that do not alter rendered presentation or CDS usage. + Trigger examples: "build this screen", "fix spacing on this component", "replace this UI with CDS components", + "perform a CDS audit on our changes", "check our codebase for CDS adherence", "does this feature use CDS well?" license: Apache-2.0 metadata: version: '2.1.0' @@ -17,11 +19,13 @@ metadata: Before responding, determine what the user needs: -**Coding** — the user wants to create or update UI → follow the Coding Workflow. +**Coding** — the user wants to create or update rendered UI presentation or CDS usage → follow the Coding Workflow. **Review** — the user explicitly asks to audit, review, or check existing code for CDS adherence → read `guidelines/code-review.md` and follow it instead. -**Default to coding.** Only treat a request as a review if the user's intent is explicit. Writing code is the primary use case for this skill. +**Out of scope** — the user wants logic-only changes, hooks, tests, Relay or data fetching, analytics, navigation wiring, feature flags, generated artifacts, performance-only refactors, or edits in component files that do not alter rendered presentation or CDS usage → do not follow this skill's coding or review workflows. + +If the request is ambiguous, inspect the requested change first. Only enter the Coding Workflow when the change affects rendered UI presentation or CDS usage. Do not treat "component" or "frontend repo" as sufficient signal by itself. ## Initialization @@ -41,7 +45,7 @@ If the script cannot be run, much of the information it provides can be determin ## Coding Workflow -For all frontend coding tasks, follow these steps in order. +For coding tasks that change rendered UI presentation or CDS usage, follow these steps in order. **YOU MUST** perform steps 1 and 2 before writing any code! From dc5a5b75ab3d95dc16d6946fc4a69974197bcf22 Mon Sep 17 00:00:00 2001 From: Duggan Burke Date: Wed, 8 Jul 2026 20:31:08 -0700 Subject: [PATCH 2/2] docs: clarify cds-code default workflow Co-authored-by: Codex --- skills/cds-code/SKILL.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/skills/cds-code/SKILL.md b/skills/cds-code/SKILL.md index 24bf4ce3d5..0f9cce64e8 100644 --- a/skills/cds-code/SKILL.md +++ b/skills/cds-code/SKILL.md @@ -25,6 +25,8 @@ Before responding, determine what the user needs: **Out of scope** — the user wants logic-only changes, hooks, tests, Relay or data fetching, analytics, navigation wiring, feature flags, generated artifacts, performance-only refactors, or edits in component files that do not alter rendered presentation or CDS usage → do not follow this skill's coding or review workflows. +**Default in-scope work to coding.** For requests that affect rendered UI presentation or CDS usage, only treat the request as a review if the user's audit/review intent is explicit. Writing code is the primary use case for this skill. + If the request is ambiguous, inspect the requested change first. Only enter the Coding Workflow when the change affects rendered UI presentation or CDS usage. Do not treat "component" or "frontend repo" as sufficient signal by itself. ## Initialization