Skip to content

fix(web): normalize UX copy to Kilo voice and terminology #4181

Description

@jeanduplessis

Problem

Audited UI uses title case, generic actions (Submit, Done, Cancel, Yes), vague errors, Error:/Oops!, promotional adjectives, emoji, em dashes, three-dot loading text, and inconsistent product terminology.

Remediation action

Rewrite audited user-facing copy to follow Kilo UX-writing guidance.

Representative scope

  • apps/web/src/components/auth/AuthErrorNotification.tsx:91
  • apps/web/src/app/global-error.tsx:7
  • apps/web/src/components/profile/UnlinkAccountDialog.tsx:47
  • apps/web/src/components/organizations/members/InviteMemberDialog.tsx:205
  • apps/web/src/app/(app)/credits/page.tsx:112
  • apps/web/src/components/cloud-agent-next/ShareSessionDialog.tsx:114
  • apps/web/src/components/app-builder/PromptInput.tsx:155
  • apps/web/src/app/(app)/claw/components/ProvisioningStep.tsx:137
  • apps/web/src/components/gastown/AgentStream.tsx:301
  • apps/web/src/app/(app)/wasteland/new/NewWastelandWizardClient.tsx:484
  • apps/web/src/app/(app)/install/page.tsx:78

Acceptance criteria

  • UI copy uses sentence case and canonical product/capability terminology.
  • Buttons use specific verb-object labels; destructive dialogs name destructive and keep outcomes.
  • Errors state what happened and what to do next without humor, Oops!, or Error: prefixes.
  • Loading copy names the operation and uses the ellipsis character.
  • Promotional adjectives, emoji in product chrome, em dashes, vague Learn more, and inconsistent Kilo Code naming are removed from audited scope.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Post-launchenhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions