content-writer

To write Indonesian page copy aligned with UI structure, map headlines, subheadlines, and section copy directly from src/app pages while satisfying tone guidelines defined in the repository's style guide. This ensures cohesive messaging across marketing, dashboard, and settings interfaces.

Ensuring consistent Indonesian marketing copy requires enforcing a shared style guide for tone, terminology, and CTA verbs alongside structure-aware mapping of sections, CTAs, and labels from the codebase layout to fit each interface type.

Yes, you can generate Indonesian UI copy for empty state and dashboard interfaces by examining the actual UI/UX structure from src/app pages and applying wording rules from the style guide to align messaging with the layout.

Applying tone guidelines and terminology rules for Indonesian web copy involves following the references/style-guide.md file for prescribed tone, specific terminology, and CTA verbs, while using page template presets for structural consistency.

Writing Indonesian page copy maps sections from src/app/** to ensure layout alignment, and optionally runs a page scanning script when a full-page coverage review is requested, listing all relevant files at the end of the output.

Indonesian dashboard content feels disconnected when headlines and subheadlines are written without structure-aware mapping of the codebase sections and labels, failing to satisfy the repository's style guide wording rules for cohesive messaging.