# Style Guide

> 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.

- Skill: `caglarbaranbora/style-guide` (Agent Skill)
- Install (CLI): `npx skillmds@latest add caglarbaranbora/style-guide`
- Raw SKILL.md: https://api.skillmd.com/api/skills/caglarbaranbora/style-guide/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: caglarbaranbora (https://skillmd.com/u/caglarbaranbora)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/caglarbaranbora/style-guide

---


# 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.