domains / families / security / privacy-by-design

privacy-by-design

authentic

Use when building apps that collect user data. Ensures privacy protections are built in from the start—data minimization, consent, encryption.

When to use

• Use when building apps that collect personal data (names, emails, locations, preferences)
• Use when designing database schemas, APIs, or authentication flows
• Use when the user mentions forms, user accounts, analytics, or third-party integrations
• Use when deploying to production—verify privacy controls before launch
• This skill is applicable when building software that collects, stores, or processes personal data. Apply it proactively during design and implementation.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Source