What problem does it solve? Explaining a new framework, runtime, or architecture to Chinese-speaking developers often degenerates into API listings or translated docs that never convey why the design exists. This Skill structures a Chinese-language article that derives each abstraction from a concrete pain point, so readers understand the technology by watching it grow out of necessity. ## Core Features & Use Cases - Requirement-ladder method: Builds a seed example with no framework, then grows requirements one rung at a time, gating every abstraction behind a demonstrated pain point. - Paired implementations: Shows vanilla code and framework code side by side, isolating the single line where they diverge and honestly accounting for added complexity. - Chinese style rules: Enforces natural Chinese prose with English technical terms, question-form headings, arrow-chain summaries, and a bolded thesis statement. - Source verification gate: Requires every technical claim to be checked against the actual source code of the version being explained before delivery. - Use Case: Write a Chinese article explaining a dependency-injection framework by starting from a 15-line greeter program, then introducing Context, Plugin, and lifecycle management only as each limitation appears. ## Quick Start Write a Chinese tech breakdown article that derives the target framework step by step from a minimal seed example, following the requirement-ladder and pain-point gating method.
