Loading...
Loading...
Found 118 Skills
Expert localization decisions for iOS/tvOS: when runtime language switching is needed vs system handling, pluralization rule complexity by language, RTL layout strategies, and string key architecture. Use when internationalizing apps, handling RTL languages, or debugging localization issues. Trigger keywords: localization, i18n, l10n, NSLocalizedString, Localizable.strings, stringsdict, plurals, RTL, Arabic, Hebrew, SwiftGen, language switching
Reframes messages, requirements, metrics, and decisions for organizational audiences—engineering, product, finance, legal, compliance, sales, operations, actuarial, and executive—by detecting jargon, surfacing implicit assumptions, producing dual-audience briefs, RACI-aligned handoffs, owner-tagged meeting actions, technical-to-business and business-to-technical translation, and escalation summaries. Use when translating for engineering, explaining to finance, cross-department bridging, rewriting for executives, business-friendly versions, technical summaries for leadership, inter-team handoffs, department jargon, or dual-audience briefs—not external customer or brand copy (communication-lead), contract redlines (commercial-counsel), full multi-team program execution (technical-program-manager), human-language i18n/l10n product strings, or strategy-only consulting without audience reframing (business-consultant).
Use this skill to review a Lightning Web Component (.html, .js, .css files) for right-to-left (RTL) internationalization correctness, producing a finding list with code-level fixes covering CSS logical properties, bidirectional text handling, keyboard semantics, and RTL-aware SLDS class usage. TRIGGER when the user says "review this LWC for RTL", "audit i18n compliance", "fix bidirectional text rendering", "replace left/right CSS with logical properties", "check RTL layout issues", "verify SLDS RTL classes", "review my component for Arabic/Hebrew layout", "ensure this LWC works in RTL locales", or "check bidi text handling". DO NOT TRIGGER when the user is building a new LWC (use experience-lwc-generate), refactoring SLDS classes themselves (use design-systems-slds-apply or design-systems-slds2-migrate), or performing accessibility/security review.
Production-readiness pass — audits and implements the full non-happy-path matrix: loading skeletons, empty states, error messages, partial data, i18n, offline, permissions, and first-run guidance. Use when preparing a surface for production or when the user says "it crashes on empty data" / "there's no loading state" / "harden this". Invoke when the user asks for harden on their UI, or mentions 'harden' alongside design / UI / frontend work.
Build static landing pages with Neobrutalism design + Blobity cursor. Design tokens, page structure, components, 3D card tilt, theme toggle, i18n.
Agent Session Visualization / Session Timeline: Execution maps for Cursor, Codex, Claude Code, Workbuddy, kimi-code threads (by ID or name); includes skills/tools/sub-agents, retries/forks/waits, layered internationalization + session health. Triggers (English): agent thread visualizer, agent-thread-visualizer, agent session timeline, session report, session log analyzer, agent flow visualization, execution map, conversation visualizer, subagent timeline, debug agent session, visualize the run, Cursor session, Claude Code session, Workbuddy session, kimi-code session. (Chinese): agent session visualization, session visualization, agent timeline, sub-agent visualization, session report, session analysis, execution map, agent execution flow, debug agent session, Cursor session, Claude Code session, Workbuddy session, kimi-code session. (Japanese): agent session visualization, session visualization, agent timeline, sub-agent visualization, session report, execution map, agent execution flow, Cursor session, Claude Code session, Workbuddy session, kimi-code session.
Dynamic path segments ($paramName), splat routes ($ / _splat), optional params ({-$paramName}), prefix/suffix patterns ({$param}.ext), useParams, params.parse/stringify, pathParamsAllowedCharacters, i18n locale patterns.
Configure your Flutter app to support different languages and regions
Add `flutter_localizations` and `intl` dependencies, enable "generate true" in `pubspec.yaml`, and create an `l10n.yaml` configuration file. Use when initializing localization support for a new Flutter project.
Run the localization workflow: extract strings, validate localization readiness, check for hardcoded text, and generate translation-ready string tables.
Generate a language translation for a mkdocs documentation stack.
Provide additional context for messages based on the codebase and the context of the message to improve the quality of the translations.