sgds-writing

Applies Singapore Government Design System writing rules to UI copy and documentation.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/HiokKuek/hdb_pricing --skill sgds-writing-hiokkuek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sgds-writing
Source: https://github.com/HiokKuek/hdb_pricing/tree/main/.agents/skills/sgds-writing
Command: npx skills add https://github.com/HiokKuek/hdb_pricing --skill sgds-writing-hiokkuek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Government digital products often ship with inconsistent UI copy: mixed US and UK spelling, title case headings, jargon-heavy sentences, and unclear error messages. This Skill provides a complete set of writing standards so all content accompanying SGDS components follows one consistent, plain-language style. ## Core Features & Use Cases - Style rule enforcement: Covers tone, UK English spelling, sentence case capitalisation, punctuation (including a strict no-em-dash rule), grammar, and plain language principles. - UI copy patterns: Provides ready-made conventions for buttons, error messages, empty states, tooltips, helper text, and loading messages. - Reference lookups: Includes quick-reference files for spelling word lists, grammar rules, punctuation, and word choice for on-demand consultation. - Use Case: When drafting an error message like "You uploaded a file that is too large. Please upload a smaller file.", use this Skill to rewrite it as "The file is too large. Upload a file under 5 MB." ## Quick Start Review this error message and button label against the SGDS writing guide and rewrite them to comply with the style rules.

Frequently Asked Questions about sgds-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write error messages for government digital services?

State what happened and what the user should do next, without blaming the user. For example, write "The file is too large. Upload a file under 5 MB." instead of "You uploaded a file that is too large."

What writing style guide applies to Singapore Government Design System components?

The SGDS writing guide covers tone, UK English spelling, sentence case, punctuation, grammar, and plain language for all UI copy accompanying SGDS components. It includes reference files for spelling, grammar, punctuation, and word choice.

Should UI copy use UK or US spelling in Singapore government products?

Use UK English spelling throughout, such as colour, centre, organise, and licence (noun). Set your editor and CI spell checker to en-GB, and standardise on -ise verb endings for consistency.

Can I use contractions in government website content?

No. Write out full forms in all content, including UI copy, labels, and error messages. This guide deliberately departs from GOV.UK and Shopify Polaris to maintain a formal register and avoid ambiguity like "it's" versus "its".

When should I use must versus should in instructions?

Use "must" only for legal obligations, "need to" for expected administrative steps, "should" for recommendations, and "may" for optional permissions. Using "must" for administrative steps implies a legal consequence that may not exist.

Why is the em dash banned in SGDS content?

The em dash creates visual noise and is often misread or skipped by screen readers. Use a comma pair for parenthetical asides, a colon to introduce lists, or split the content into two sentences instead.