How-to Guide Writer (Resources)

To write a developer how-to guide for Medusa ecommerce, use a generation process that researches implementation details within the `packages/` directory and structures concise, task-oriented steps with code examples and testing instructions.

The best way to create technical documentation for specific Medusa developer tasks is to generate focused 4-6 step guides that emphasize actionable content, practical code examples, and clear testing instructions for single problems.

Yes, you can generate how-to guides that comply with Vale linting and cross-project linking conventions by structuring the technical writing output to explicitly adhere to these specific documentation standards during the content generation process.

The how-to guide generation process does research implementation details directly within the `packages/` directory to ensure the technical writing accurately reflects the codebase structure and provides correct developer instructions.

A focused task-oriented developer guide should contain 4-6 steps targeting a single, specific task to ensure the technical writing remains concise and helps developers solve specific problems efficiently without unnecessary overhead.

You can generate concise, task-oriented developer guides for the Medusa platform that provide step-by-step instructions, practical code snippets, and testing procedures for specific implementation tasks like adding custom product attributes.