microcopy

Follow the required error structure: state what happened, optionally why, and what the user can do next. Always offer actionable options like Retry, View details, Go to Settings, or Contact support, and never blame the user or show only an error code.

Provide the raw Chinese string and the Skill produces localized, product-native English rather than literal translation. It keeps visual length similar to the source, preserves placeholders like {name} or %s exactly, and prioritizes verb-plus-object phrasing for tight spaces like buttons and toasts.

Use the fixed terminology table: Workspace, Agent, Group, Context, Memory, Integration, Skill, Agent Profile, Topic, Page, Community, Resource, Library, and Provider. One concept maps to exactly one term across the entire product, with no synonym mixing.

Default to roughly 80 percent information and 20 percent warmth, rising to 70/30 only at key moments like first-time creation, empty states, failures, and long waits. Warmth is capped at half a sentence to one sentence and must be followed by a clear next action.

It is designed for user-facing product copy such as buttons, toasts, modals, and onboarding, not for long-form marketing content, documentation, or legal text. Serious scenarios like billing, security, and data loss prioritize neutral clarity over warmth.