components.write-docs
Goal: Create or update documentation for a CDS component on the docsite (apps/docs/).
If no component name is provided, ask the user which component they want to document.
Step 1: Check for Existing Documentation
First, check if documentation already exists for this component:
apps/docs/docs/components/*/[ComponentName]/
- If docs exist: Review the existing documentation and identify what needs to be added, updated, or improved. Consider the user's additional context if provided.
- If docs don't exist: Follow the full workflow below to create new documentation.
For updates, focus on the specific areas that need improvement rather than rewriting everything.
Reference Components
More from coinbase/cds
cds-code
|
10cds-docs
|
6feature-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.
3ktlo
Instructions to fetch assigned Linear issues in the current cycle and potentially kick off a development session.
2dev.cds-mobile
USE THIS when asked to work on a new or existing (MOBILE) CDS React component in packages/mobile
2git.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.
2