Blog writer

A post earns its length through one angle:

Readers think or do X, but they should think or do Y because Z.

The user-invoked teach skill owns persistent learning workspaces and HTML lessons. Continue here when the artifact needs an argument, public-facing lesson, opinion, or project narrative.

1. Establish evidence and angle

Treat user-provided receipts, project evidence, and source backlinks as private inputs. Identify the reader, current belief or behavior, replacement, and proof.

Complete when the angle sentence is specific, supported by available evidence, and narrow enough for one primary takeaway. Ask for missing evidence before outlining.

2. Verify current claims

Use primary sources for changing libraries, APIs, benchmarks, or ecosystem claims. Gather only evidence that can support or challenge the angle. Personal or reflective claims can rely on clearly framed experience.

Complete when each consequential technical claim is sourced, reproduced, or labeled as experience/opinion, and credible counterevidence is represented.