メニュー
Use when improving visual design, interface quality, dashboards, SaaS positioning, landing page copy, UX text, documentation, explanations, or other human-facing writing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | product-design-writing |
| description | Use when improving visual design, interface quality, dashboards, SaaS positioning, landing page copy, UX text, documentation, explanations, or other human-facing writing. |
Load only the matching sub-skill:
| Trigger | Read |
|---|---|
| distinctive frontend UI, production-grade visual design, components/pages/apps | product-design-writing/subskills/frontend-design/SKILL.md |
| dashboards, admin panels, SaaS apps, tools, settings, data interfaces | product-design-writing/subskills/interface-design/SKILL.md |
| SaaS positioning, landing page messaging, pricing, SEO, conversion copy | product-design-writing/subskills/saas-marketing-playbook/SKILL.md |
| documentation pass, stale docs, README refresh, examples/changelog after code changes | documentation-pass/SKILL.md |
| drafting or revising prose, docs, commit messages, error messages, explanations, UI text, emails, articles, summaries, or public writing | product-design-writing/subskills/writing-clearly-and-concisely/SKILL.md |
Use when managing per-project backlog folders, feature queues, async agent work items, lifecycle status updates, PR/done/blocked transitions, or status reviews inside an Obsidian vault.
Use when prototyping, authoring agent skills, or asking the agent to zoom out and map unfamiliar code before acting.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Use when reviewing architecture boundaries, hexagonal architecture, clean architecture layers, dependency direction, trust boundaries, uploads, parsers, redirects, or web security risks.
Use when configuring or running hexcheck in a Go repo for hexagonal architecture boundaries, adapter business-logic warnings, and mock discipline.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
