tech-writing

To write a clear README, draft and structure your technical content using a reader-first approach that enforces evidence-first reasoning, consistent terminology, and accessible presentation throughout the document.

The best way to structure API documentation is by applying a structured drafting and reviewing workflow that enforces YAML frontmatter usage and evidence-first reasoning to ensure clarity and consistent terminology.

Rewrite technical content to improve clarity by applying structured heuristics and a review checklist that enforce concise, evidence-backed, and action-oriented prose for your readers.

Yes, you can use this workflow for drafting tutorials and onboarding guides, as it applies to documentation, design docs, release notes, specs, comments, CLI help, and support content.

Yes, it supports Chinese technical prose by loading and applying specific language style guidelines from internal references to guide your content toward evidence-first reasoning when needed.

Your documentation lacks consistent terminology because it needs a structured review process that enforces reader-first drafting, evidence-first reasoning, and clear accessible presentation guidelines.