Adds and updates TypeDoc (TSDoc) comments to TypeScript source files in the Medusa codebase. Covers HTTP types, API routes, UI components, data models, service interfaces, JS SDK methods, abstract providers, workflow SDK functions, core-flows workflows and steps, and events. Use when adding TSDoc comments to files in packages/core/types/src/http, packages/medusa/src/api, packages/design-system/ui/src/components, packages/modules/*/src/models, packages/core/types/src, packages/core/js-sdk/src, packages/core/utils/src, packages/core/workflows-sdk/src/utils/composer, packages/core/core-flows/src, or packages/core/utils/src/core-flows/events.ts.
npx skills add https://github.com/medusajs/medusa --skill writing-tsdocs
Adds TypeDoc (TSDoc) comments to Medusa TypeScript source files. Follows TypeDoc conventions and uses custom tags defined in www/utils/packages/typedoc-config/tsdoc.json.
> CRITICAL: Violating these produces incorrect or broken documentation.
exported interfaces, types, functions, classes*.spec.ts, *.test.ts, __tests__/@since version numbers — only use the version passed in the prompttsdoc.json: @expandable, @featureFlag, @since, @apiIgnore, @schema, @tags, @version, @keep, @customNamespace, @namespaceMember> Load the reference file for the file type you're documenting before writing any TSDocs.
| Path pattern | Load |
|------|------|
| packages/core/types/src/http/ | reference/http-types.md |
| packages/medusa/src/api/admin/ or /store/ | reference/api-routes.md |
| packages/design-system/ui/src/components/ | reference/ui-components.md |
| packages/modules/*/src/models/ | reference/data-models.md |
| packages/core/types/src/ (non-http) | reference/service-interfaces.md |
| packages/core/js-sdk/src/ | reference/service-interfaces.md |
| packages/core/utils/src/ (abstract providers) | reference/service-interfaces.md |
| packages/core/workflows-sdk/src/utils/composer/ | reference/service-interfaces.md |
| packages/core/core-flows/src/ (workflows) | reference/workflows-steps.md |
| packages/core/core-flows/src/ (steps) | reference/workflows-steps.md |
| packages/core/utils/src/core-flows/events.ts | reference/events.md |
/**
* Brief description.
*/
export interface Foo {
/**
* The foo's ID.
*/
id: string
}
| File type | What to document | Key Medusa tags |
|-----------|-----------------|----------|
| HTTP types | Every exported interface/type + all properties | @expandable on nested objects |
| API routes | Exported handlers only (minimal) | @featureFlag, @since |
| UI components | Component + all props | Plain descriptions |
| Data models | Model + each property | @since on new items |
| Service interfaces | Every method in full | @param, @returns, @example |
| JS SDK | Every public method | @param, @returns, @example, @tags |
| Providers | Class + every abstract method | @param, @returns, @example |
| Workflow SDK | Every exported function | @param, @returns, @example |
| core-flows workflows | Workflow export + hooks | @summary, @featureFlag, @since |
| core-flows steps | Step export + input type | @featureFlag, @since, @example |
| Events | Every event constant | @eventPayload, @featureFlag, @since |
www/utils/packages/typedoc-config/tsdoc.json)| Tag | Kind | Use when |
|-----|------|----------|
| @featureFlag <name> | block | Export requires a feature flag to be enabled |
| @expandable | modifier | Nested object expandable in API queries |
| @since <version> | block | Export was added in this version (prompt-provided only) |
| @apiIgnore | modifier | Exclude from API docs output |
| @tags <name> | block | SDK categorization |
| @schema | block | Custom schema documentation |
| @keep | modifier | Preserve during doc generation |
| @customNamespace | block | Assign to custom doc namespace |
Standard TypeDoc/JSDoc tags (@param, @returns, @example, @deprecated, @remarks, etc.) are always allowed.
private items@since without a version being provided in the prompt@param/@returns to non-method exports (interfaces, types)id field without specifying what resource it belongs toreference/http-types.md - HTTP type interfaces: properties, @expandable
reference/api-routes.md - API routes: @featureFlag, @since, minimal docs
reference/ui-components.md - UI components: component + inline prop pattern
reference/data-models.md - DML models: @since, property descriptions
reference/service-interfaces.md - Methods, SDK, providers, workflow SDK: full JSDoc
reference/workflows-steps.md - core-flows workflows and steps: @summary, hooks, @example
reference/events.md - Event constants: @eventPayload, @featureFlag, @since
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take medusajs/writing-tsdocs from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.