القائمة
Write or revise Aura Historia user-facing copy for collectors, dealers, auction staff, partners, and estate sellers with polished antiques/art-market tone and full i18n coverage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Add or extend Aura Historia features using the project's feature-sliced React/TanStack architecture, i18n, design, privacy, testing, and hydration checks.
Review Aura Historia code changes that touch user data, cookies/storage, auth, consent, analytics, payments, partner/admin data, OAuth, or tokens for privacy-policy alignment.
Write and refactor React forms using react-hook-form with Zod validation. Use when creating new form components, converting existing forms to react-hook-form, or implementing form validation patterns.
Writes React components without unnecessary useEffect. Use when creating/reviewing React components, refactoring effects, or when code uses useEffect to transform data or handle events.
استنادا إلى تصنيف SOC المهني
| name | product-copywriter |
| description | Write or revise Aura Historia user-facing copy for collectors, dealers, auction staff, partners, and estate sellers with polished antiques/art-market tone and full i18n coverage. |
Use this skill when adding or changing user-facing text, landing-page copy, SEO metadata, empty/loading/error states, partner-program copy, legal-adjacent explanations, or product messaging.
Read:
docs/product-context.mddocs/design-guidelines.md for UI tone/fitdocs/privacy-policy-alignment.md if the copy explains data, consent, tracking, accounts, payments, tokens, OAuth, or privacysrc/i18n/AGENTS.mdWrite polished, confident, precise, restrained copy for discerning antiques/art users.
Prefer:
Avoid:
src/i18n/locales/de/translation.json, en, es, fr, and it.<Trans> markers exactly.Sie unless the local context already uses another tone.meta.* keys when page-facing content changes.Before finishing: