domains / families / documents / tutorial-engineer

tutorial-engineer

combined

Creates step-by-step tutorials and educational content from code. Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples.

When to use

• Working on tutorial engineer tasks or workflows
• Needing guidance, best practices, or checklists for tutorial engineer
• Transforming code, features, or libraries into learnable content
• Creating onboarding materials for new team members
• Writing documentation that teaches, not just references
• Building educational content for blogs, courses, or workshops

When not to use

• The task is unrelated to tutorial engineer
• You need a different domain or tool outside this scope
• Writing API reference documentation (use `api-reference-writer` instead)
• Creating marketing or promotional content
• Clarify goals, constraints, and required inputs.
• Apply relevant best practices and validate outcomes.
• Provide actionable steps and verification.
• Identify what readers will be able to do after the tutorial

Skill page

Conflict

The sickn33 copy is a more developed, parameterized version of the rmyndharis copy, but it is truncated and contains corrupted placeholders (e.g., '± Rule', 'x faster', 'x% retention') that make it unusable as a standalone procedure. The rmyndharis copy is complete and clean but lacks the specific pedagogical constraints (Bloom's taxonomy, cognitive load rules, I-We-You pattern) found in the sickn33 copy. Combining them yields a complete, actionable skill that retains the structural integrity of the first and the specific instructional heuristics of the second.