القائمة
Instructions to fetch assigned Linear issues in the current cycle and potentially kick off a development session.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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?"
Turn Figma designs into CDS React (cds-web) or React Native (cds-mobile) code. Use when the user shares a Figma design URL (e.g. `figma.com/design/...?node-id=...`) or asks to "implement this design" or "build this from Figma" in a frontend project that is using Coinbase Design System (CDS). Do not use for general CDS UI work with no Figma reference (use `cds-code`), or for design critique without an implementation request.
Reviews already-written Coinbase Design System (CDS) UI for accessibility: verifying documented accessibility props (e.g. accessibilityLabel, accessibilityState), confirming the chosen CDS primitives cover the right assistive technology behavior, and checking usage against official CDS documentation—not generic web ARIA tutorials. Use this skill to review CDS UI for screen reader, keyboard, and labeled control requirements after the code has been written.
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.
Back-port a specific commit from master to a release branch via cherry-pick. Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default. Returns to the original branch when done (success or failure). If there are merge conflicts, diagnoses the root cause without attempting an autonomous resolution. Use when asked to "backport", "cherry-pick to release", or "port a fix to a release branch".
| name | ktlo |
| description | Instructions to fetch assigned Linear issues in the current cycle and potentially kick off a development session. |
| model | claude-sonnet-4-6 |
| disable-model-invocation | true |
Use the Linear MCP server to get my assigned issues in the active cycle. Follow these steps exactly:
get_user with query "me" to retrieve my user info and the list of teams I belong to.list_cycles with type: "current" and that team's teamId to get the active cycle ID(s). Skip teams with no active cycle.list_issues with assignee: "me", the explicit cycle id (NOT the string "current"), and the corresponding team ID. Do NOT pass "current" as the cycle value — it must be the actual cycle ID returned in step 2.Present them to me as a list of options. It is possible that I have no issues assigned to me in the active cycle.
Also remind me to check the Jira Bug Sprint board for any bugs that may be assigned to me as they are still not tracked in Linear.
If I have any issues assigned to me in the active cycle, ask for the issue id/name/etc. that I may want to work on. If provided, fetch the rest of the issue's details and think about the best way to implement the feature/bug/etc. If there is not enough context on the issue, ask me clarifying questions.
You must always execute on designated issue in PLAN MODE. Never start coding a solution to the issue without consent from me on a well thought out plan.