OpenParable
Skip to content

Development skills

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

element-backwards-compat

Backwards compatibility rules when changing element controllers in `apps/prairielearn/elements/`.

489 repo stars390 repo forks
Development

groups-and-teams

Dealing with groups and teams in PrairieLearn, and confusion about table/column/variable names.

489 repo stars390 repo forks
Development

property-dots

Guide for writing functions that accept property name-value pairs via `...`. Use when adding a function whose `...` collects property values.

489 repo stars49 repo forks
Development

better-result-adopt

Migrate codebase from try/catch or Promise-based error handling to better-result. Use when adopting Result types, converting thrown exceptions to typed errors, or refactoring existing error handling to railway-oriented programming.

488 repo stars83 repo forks
Development

cds-code

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?"

488 repo stars100 repo forks
Development

cds-design-to-code

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.

488 repo stars100 repo forks
Development

cds-migrator-transform

Use when a CDS change in **cds-web**, **cds-common**, **cds-mobile**, **web-visualization**, or **mobile-visualization** needs a **jscodeshift** migration in `packages/migrator` to update callers or mitigate breaking API or import moves (add or change a transform, tests, or preset entry).

488 repo stars100 repo forks
Development

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.

488 repo stars100 repo forks
Development

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.

488 repo stars100 repo forks
Development