메뉴
Apply Pretty Good Type Scale (PGTS) in iOS, iPadOS, and macOS Swift or SwiftUI projects using the generated PGTS.swift export. Use when a coding agent needs to map PGTS roles to Apple text styles, Dynamic Type, custom fonts, or native app typography.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Apply, tune, validate, or port the Pretty Good Type Scale (PGTS) as a coding-agent workflow for design-system typography in web apps, token pipelines, Swift/iOS/macOS projects, and Android Compose projects. Use when a task mentions PGTS, type-scale tokens, generated typography exports, responsive typography, native typography ports, or code changes to a PGTS-based design system.
Apply Pretty Good Type Scale (PGTS) in web projects using the generated CSS. Use when a coding agent needs to integrate PGTS in HTML, CSS, React, Next.js, design-token CSS, responsive typography, print CSS, or browser-based design systems.
Apply Pretty Good Type Scale (PGTS) in Android projects using the generated Jetpack Compose Material 3 typography export. Use when a coding agent needs to map PGTS roles to Compose TextStyle, Material Typography, sp units, Android font scaling, or native Android design-system typography.
SOC 직업 분류 기준
| name | pgts-apple |
| description | Apply Pretty Good Type Scale (PGTS) in iOS, iPadOS, and macOS Swift or SwiftUI projects using the generated PGTS.swift export. Use when a coding agent needs to map PGTS roles to Apple text styles, Dynamic Type, custom fonts, or native app typography. |
Use this skill when the target is an Apple platform project. Use platforms/apple/PGTS.swift as the generated starter export, tokens/pgts.tokens.json as the canonical PGTS source, and tokens/apple-dynamic-type.json as the Apple Dynamic Type adapter source.
Canonical roles: editorial-mega-display, display-large, display, headline-large, headline, title-large, title, body, footnote, caption, legal.
Lean roles for product UI: display, headline-large, title-large, title, body, footnote.
Copy or import the generated Swift file into the host app module. Add a package or module declaration only if the host project requires it.
Use PGTSRole for semantic identity, PGTSContext for mobile, desktop, or print contexts, and PGTS.style(_:) for the numeric values:
let style = PGTS.style(.display)
let font = style.font(for: .mobile, design: .serif)
Use role.dynamicTypeTextStyle as the semantic scaling hint. The generated file provides point-size anchors, Apple text-style mappings, Dynamic Type size names, and preview helpers, but the host app should still rely on Apple runtime scaling for final rendering.
For SwiftUI custom fonts, use Font.custom(name, size: style.pointSize(for: platform), relativeTo: role.dynamicTypeTextStyle) or style.customFont(name:platform:).
For UIKit custom fonts, use UIFontMetrics(forTextStyle: role.uiKitTextStyle).scaledFont(for:) and set adjustsFontForContentSizeCategory = true on the text control.
Use style.scaledPointSize(for:dynamicTypeSize:) and style.scaledLineHeight(for:dynamicTypeSize:) for previews, web visualization, and design-token inspection. Do not replace Apple runtime scaling with these preview values in production app text controls.
For tvOS, treat generated values as projected until exact tvOS 27 SDK probe data replaces the projection source. Standard SwiftUI and UIKit text controls should still use the platform Dynamic Type APIs.
PGTS does not bundle fonts. Apply the host app's custom font separately and test the selected typeface for x-height, ascenders, descenders, optical size, and line-height behavior.
xSmall, large, xxxLarge, accessibility1, and accessibility5.footnote, caption, and legal remain readable.npm run build after token changes and npm run validate before returning work.