Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.
91
87%
Does it follow best practices?
Impact
96%
1.11xAverage score across 5 eval scenarios
Passed
No known issues
An engineering team is building a Node.js web application and needs to add Redis as a caching layer to reduce database load. The team's developers are experienced with Node.js and already have a working Express application — they just need to know the steps to connect it to a Redis instance and start using it for caching responses. They don't need a conceptual primer on what Redis is or why caching matters; they need a practical, no-frills document they can follow to get it wired up and working.
The team's developers work across different environments and setups, so the documentation needs to be practical for real-world conditions rather than assuming a single fixed configuration.
Produce a single Markdown file named guide.md that an experienced Node.js developer can follow to connect their existing Express application to Redis for caching. The document should be actionable without re-explaining Node.js or Express fundamentals. Include code snippets where appropriate.
The document should cover:
Name the output file guide.md.