specpin

Review and improve target-language translations in i18n message catalogs (JSON/TS/YAML key-value locale files). Use this skill whenever the user asks to check, review, proofread, or fix a translation file; says a translation "sounds unnatural" / "chưa tự nhiên" / "awkward"; asks to review or fix a vi.ts / ja.ts / locale / messages / i18n / l10n catalog or the translated prose of a localized docs site (e.g. Astro Starlight vi/ ja/ Markdown mirrors); or wants a source-vs-target naturalness audit. Flags literal/wrong-nuance wording, wrong software-domain terms, dropped words, and spelling/style inconsistencies while preserving untranslated project jargon. Not for authoring brand-new keys/pages, translating from scratch, or editing i18n loader/runtime code.

Author and pin living business specs (rules, descriptions, acceptance criteria) onto the elements of a running web UI, and drive the specpin sidecar CLI. Use when the user wants to document UI elements with versioned specs, write or edit .specs/*.spec.json files, run "specpin serve"/"specpin validate", or mentions specpin, spec.json, or pinning specs to a page. The host coding agent is the author: it reads the UI source, writes schema-valid JSON, registers it in the manifest, and validates. No application code is generated.

Create high-quality visual designs — websites, app screens, dashboards, slides, marketing materials, social media graphics — using the Pencil CLI tool. Use this skill whenever the user wants to create, generate, or visualize any kind of UI design, mockup, wireframe, layout, webpage, app screen, presentation slide, poster, banner, or marketing asset. Also use it when the user says things like "design me a...", "make a visual for...", "create a mockup of...", "what would X look like?", or wants to turn an idea into a visual. Even if the user doesn't mention "Pencil" or "design tool" explicitly — if they want something visual created, this is the skill to use.