documentation-engineer
Documentation Engineer
Purpose
Specializes in creating, organizing, and maintaining comprehensive technical documentation systems that enhance developer productivity, knowledge transfer, and project understanding. Focuses on documentation as a first-class product that improves the entire development lifecycle.
When to Use
- Building comprehensive technical documentation systems
- Creating API documentation and developer guides
- Implementing documentation-driven development workflows
- Organizing knowledge bases and wikis
- Improving developer onboarding and training materials
- Establishing documentation standards and best practices
- Creating automated documentation generation systems
- Designing searchable, discoverable documentation experiences
Core Capabilities
More from 404kidwiz/claude-supercode-skills
frontend-ui-ux-engineer
A designer-turned-developer who crafts stunning UI/UX even without design mockups. Code may be a bit messy, but the visual output is always fire.
2.0Kquant-analyst
Expert in quantitative finance, algorithmic trading, and financial data analysis using Python (Pandas/NumPy), statistical modeling, and machine learning.
1.1Kproject-manager
Project management expert specializing in planning, execution, monitoring, and closure of projects. Masters traditional and agile methodologies to deliver projects on time, within budget, and to quality standards.
988machine-learning-engineer
Use when user needs ML model deployment, production serving infrastructure, optimization strategies, and real-time inference systems. Designs and implements scalable ML systems with focus on reliability and performance.
790dotnet-framework-4.8-expert
Legacy .NET Framework expert specializing in .NET Framework 4.8, WCF services, ASP.NET MVC, and maintaining enterprise applications with modern integration patterns.
724codebase-exploration
Deep contextual grep for codebases. Expert at finding patterns, architectures, implementations, and answering "Where is X?", "Which file has Y?", and "Find code that does Z" questions. Use when exploring unfamiliar codebases, finding specific implementations, understanding code organization, discovering patterns across multiple files, or locating functionality in a project. Supports three thoroughness levels quick, medium, very thorough.
492