Style Guide Writing Skill
Purpose
Route writing/terminology implementation tasks to the minimum required
style-guide Knowledge Contracts.
Routing
Load only the contracts relevant to the task. All paths relative to
knowledge/style-guide/.
- UI interaction verbs, clicks, taps, buttons, navigation -> ui-action-verbs.md, pointer-and-click-terminology.md, touch-gesture-verbs.md, general-button-labels.md, navigation-controls.md
- UI components: dialogs/sheets, inputs, progress, chrome -> presentation-surfaces.md, input-controls.md, status-and-progress-indicators.md, app-chrome-and-window-terminology.md
- App state, connectivity, instructional voice -> app-state-and-error-terminology.md, connectivity-and-media-terminology.md, instructional-voice-and-phrasing.md
- Capitalization, punctuation, abbreviations -> capitalization-style-rules.md, capitalization-of-apple-proper-nouns.md, punctuation-and-typography-in-text.md, abbreviations-and-acronyms.md
- Units, numeric edge cases, locale formatting -> units-of-measure.md, numeric-terminology-supplement.md, international-formatting.md, international-style.md
- Inclusive writing -> writing-inclusively.md
- Code font / placeholder-name conventions -> technical-notation.md
- Copyright/trademark text -> copyright-and-trademarks.md
- Sign-in, sign-out, login wording -> sign-in-and-authentication-terminology.md
- Passkey, password, PIN, biometric wording -> authentication-credentials-and-biometrics.md
Never load more than the contracts relevant to the specific question.
Stop Conditions
Stop and report if the requested topic has no matching Knowledge Contract
in knowledge/style-guide/ — do not guess or fall back to general knowledge.
This domain owns how user-facing text is worded, never what it must
communicate. If the task turns on the latter — an error message that
must explain why an action failed, an alert whose contents are in
question, onboarding text that must convey something specific — stop and
report that human-interface-guidelines-patterns owns it, naming the
topic. Rewording text that is wrong about its own content produces
correct wording and an unfixed screen.
1---2name: style-guide3description: Route writing and terminology implementation tasks to the minimum required style-guide Knowledge Contracts — capitalization, punctuation, button labels, inclusive writing, date and number formatting, code font and placeholder-name conventions. Use when writing or reviewing app UI text, labels, buttons, errors, onboarding copy, or the wording of sign-in and credential screens (not their implementation). Triggers on writing, terminology, capitalization, punctuation, button label wording, inclusive writing, date and number formatting, code font conventions, placeholder-name text, sign-in wording, credentials wording, style guide, UI copy.4---56# Style Guide Writing Skill78## Purpose910Route writing/terminology implementation tasks to the minimum required11style-guide Knowledge Contracts.1213## Routing1415Load only the contracts relevant to the task. All paths relative to16knowledge/style-guide/.1718- UI interaction verbs, clicks, taps, buttons, navigation -> ui-action-verbs.md, pointer-and-click-terminology.md, touch-gesture-verbs.md, general-button-labels.md, navigation-controls.md19- UI components: dialogs/sheets, inputs, progress, chrome -> presentation-surfaces.md, input-controls.md, status-and-progress-indicators.md, app-chrome-and-window-terminology.md20- App state, connectivity, instructional voice -> app-state-and-error-terminology.md, connectivity-and-media-terminology.md, instructional-voice-and-phrasing.md21- Capitalization, punctuation, abbreviations -> capitalization-style-rules.md, capitalization-of-apple-proper-nouns.md, punctuation-and-typography-in-text.md, abbreviations-and-acronyms.md22- Units, numeric edge cases, locale formatting -> units-of-measure.md, numeric-terminology-supplement.md, international-formatting.md, international-style.md23- Inclusive writing -> writing-inclusively.md24- Code font / placeholder-name conventions -> technical-notation.md25- Copyright/trademark text -> copyright-and-trademarks.md26- Sign-in, sign-out, login wording -> sign-in-and-authentication-terminology.md27- Passkey, password, PIN, biometric wording -> authentication-credentials-and-biometrics.md2829Never load more than the contracts relevant to the specific question.3031## Stop Conditions3233Stop and report if the requested topic has no matching Knowledge Contract34in knowledge/style-guide/ — do not guess or fall back to general knowledge.3536This domain owns how user-facing text is *worded*, never what it must37*communicate*. If the task turns on the latter — an error message that38must explain why an action failed, an alert whose contents are in39question, onboarding text that must convey something specific — stop and40report that `human-interface-guidelines-patterns` owns it, naming the41topic. Rewording text that is wrong about its own content produces42correct wording and an unfixed screen.
caglarbaranbora