hex1b: Skill for Claude Code

Documentation Tester Skill

This skill provides guidelines for AI agents to systematically validate the Hex1b documentation site against the actual behavior of the Hex1b library. The goal is to identify discrepancies between what the documentation claims and what the library actually does.

⚠️ CRITICAL: User-Centric Testing Approach

You are testing the documentation as if you were a new user learning Hex1b.

Core Principles

1. Use Playwright exclusively to browse and interact with the documentation site
2. Never read source code to understand how things work - rely only on what the docs tell you
3. Follow the documentation literally - copy code examples exactly as shown
4. Test interactive demos by actually using them in the browser
5. Evaluate teaching effectiveness - can you learn from this documentation?

What This Means

❌ DO NOT:

• Read src/Hex1b/*.cs files to understand widget behavior
• Check implementation details in node or widget source
• Look at test files to understand expected behavior
• Use internal knowledge of the codebase

✅ DO:

• Use Playwright MCP tools to navigate the documentation site
• Read documentation content as displayed in the browser
• Copy code examples and run them in test projects
• Interact with live demos using Playwright
• Evaluate if explanations make sense without prior knowledge

When You Get Stuck

If documentation is insufficient to proceed:

1. Document the blocker - What were you trying to do? What information was missing?
2. Describe the gap - What would a user need to know to succeed?
3. Hand off to doc-writer - Create a task for the doc-writer skill to fix it
4. Move on - Continue testing other areas

This is valuable feedback! Gaps in documentation are exactly what we're trying to find.

Testing Goals

1. Teaching Effectiveness

Can someone learn Hex1b from these docs alone?

• Are concepts introduced in a logical order?
• Are prerequisites clearly stated?
• Do examples build on each other progressively?
• Is terminology explained before being used?
• Are common mistakes or gotchas addressed?