ワンクリックでManusで任意のスキルを実行

privacy-alignment-check

スター4

フォーク1

更新日2026年7月23日 20:22

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

aura-historia

aura-historia/webapp

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Privacy Alignment Check

Use this skill whenever work affects user data or behavior described by the privacy policy.

Required Reading

Read:

docs/privacy-policy-alignment.md
src/assets/content/AGENTS.md when privacy/legal markdown may change
the applicable DOX chain for touched code paths

Data Categories to Check

Look for changes involving:

Account/profile data: email, name, user ID, language, currency, roles, subscriptions.
Auth/session data: AWS Amplify/Cognito, route guards, server auth, logout/login behavior.
Cookies/storage: user-preferences, i18next, localStorage, sessionStorage, consent flags.
Watchlists, saved searches/search filters, notifications, matching, product interactions.
Newsletter/marketing and double-opt-in evidence.
Partner/shop/admin data: contact/address/domain metadata, applications, access tokens, OAuth clients.
Payment/subscription/Stripe metadata.
Tracking/analytics, external embeds, processors, logs, or error reporting.

Review Procedure

Identify exactly what personal data is collected, displayed, stored, sent, logged, or deleted.
Identify purpose, storage location, processor/API, persistence/retention implications, and whether the user expects it.
Confirm current privacy policy text covers the behavior in de, en, es, fr, and it.
Confirm optional analytics/tracking/non-essential storage remains consent-gated.
Confirm authenticated/user-specific data is not exposed in cacheable public responses, URLs, logs, or analytics events.
Confirm secrets and tokens are masked except for deliberate one-time plaintext display.
If policy/UI text changes are needed, update every locale and related i18n metadata.
If a new processor, data category, purpose, retention behavior, or transfer is introduced, flag for legal/product review.

Output Expected

When reporting, summarize:

Data touched.
Policy sections/locales checked or updated.
Consent/security/cache considerations.
Remaining legal/product review questions, if any.

このリポジトリの他の Skills

同じリポジトリ

add-feature

aura-historia/webapp

Add or extend Aura Historia features using the project's feature-sliced React/TanStack architecture, i18n, design, privacy, testing, and hydration checks.

2026-07-234

product-copywriter

aura-historia/webapp

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.

2026-07-234

react-hook-form-writer

aura-historia/webapp

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.

2026-04-204

writing-react-effects

aura-historia/webapp

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.

2026-04-204

Privacy Alignment Check

Use this skill whenever work affects user data or behavior described by the privacy policy.

Required Reading

Read:

docs/privacy-policy-alignment.md

src/assets/content/AGENTS.md when privacy/legal markdown may change

the applicable DOX chain for touched code paths

Data Categories to Check

Look for changes involving:

Account/profile data: email, name, user ID, language, currency, roles, subscriptions.

Auth/session data: AWS Amplify/Cognito, route guards, server auth, logout/login behavior.

Cookies/storage: user-preferences, i18next, localStorage, sessionStorage, consent flags.

Watchlists, saved searches/search filters, notifications, matching, product interactions.

Newsletter/marketing and double-opt-in evidence.

Partner/shop/admin data: contact/address/domain metadata, applications, access tokens, OAuth clients.

Payment/subscription/Stripe metadata.

Tracking/analytics, external embeds, processors, logs, or error reporting.

Review Procedure

Identify exactly what personal data is collected, displayed, stored, sent, logged, or deleted.

Identify purpose, storage location, processor/API, persistence/retention implications, and whether the user expects it.

Confirm current privacy policy text covers the behavior in de, en, es, fr, and it.

Confirm optional analytics/tracking/non-essential storage remains consent-gated.

Confirm authenticated/user-specific data is not exposed in cacheable public responses, URLs, logs, or analytics events.

Confirm secrets and tokens are masked except for deliberate one-time plaintext display.

If policy/UI text changes are needed, update every locale and related i18n metadata.

If a new processor, data category, purpose, retention behavior, or transfer is introduced, flag for legal/product review.

Output Expected

When reporting, summarize:

Data touched.

Policy sections/locales checked or updated.

Consent/security/cache considerations.

Remaining legal/product review questions, if any.

name	privacy-alignment-check
description	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.