---
name: apply-design-typography-standards
description: Apply the bundled Chinese-English typography and design standard for copy audits, spacing, punctuation, or design QA; skip ordinary rewriting.
---

# Apply Design and Typography Standards

Apply the requested product style while preserving meaning, official names and technical notation. Use the relevant [standard](references/standards.md), not invented dimensions or thresholds; authoring/rendering belongs to the actual output-format skill; new visual direction belongs to [frontend-design](../frontend-design/SKILL.md) or [claude-design](../claude-design/SKILL.md).

Choose the requested action: review only, correct copy, design critique or delivery QA. A correction request authorizes the edits; findings-only stays read-only. Infer medium, language, audience and official spellings, asking only about choices that materially change the result.

Read the necessary reference sections: 2–7 and 15–16 for design, 8–14 and 16 for copy, applicable parts of 9–13 for mixed language, 2 and 16 for conflicts, 17 for QA and 18 for uncovered topics. Reuse loaded material; narrow edits need no full standard.

Prefer official spellings, then language grammar, meaning/readability, product consistency and specific exceptions. Preserve URLs, code, variables, formulas, links, placeholders and intentional terminology. This skill includes no linter; only report automated checks actually run.

For design, inspect affected alignment, grouping, hierarchy, contrast, states, feedback, recovery, color and typography. For academic or professional copy polishing, read and use [academic-humanizer](../academic-humanizer/SKILL.md). This skill checks applicable spacing, punctuation, official names and rendering; it does not impose another prose style. Use [format and fidelity guidance](../refine-text/references/document-writing.md) only as needed and reuse unaffected checks. Routine text or backup hash checks are forbidden.

Classify explicit violations as errors, likely usability/readability issues as warnings and optional/disputed changes as suggestions. Resolve reference conflicts transparently rather than silently imposing preferences.

Return corrected content first or specific findings with location, consequence and correction. Use a table only for useful comparison. State material unresolved product-style questions and the actual scope/results of QA; do not infer pixels or rules absent from the standard.