AddThisFeature

Public Profile Pages

Give users a page worth sharing.

moderate Social & Sharing

What it adds

A public, shareable profile page per user, with control over what's visible.

What your agent is told to do

4
  1. 1

    Give each user a public URL with a slug they choose, not a database ID.

  2. 2

    Let the user decide what appears — default to private and let them opt in.

  3. 3

    Make the page work signed-out, and give it proper SEO and share metadata.

  4. 4

    Show the owner a preview of how others see it.

Edge cases it handles

4
  • Slugs must be validated and reserved — nobody gets /admin, /settings, or /api.
  • Changing a slug must not silently break existing links; redirect the old one.
  • The page must never leak private fields (email, billing, internal notes) — build it from an explicit allow-list, not by hiding fields.
  • A deactivated or banned user's profile must stop rendering.

Definition of done

7
  • Each profile has a user-chosen, validated, reserved-word-safe slug.
  • The page is built from an explicit allow-list of public fields.
  • It renders correctly signed-out with proper share metadata.
  • Old slugs redirect after a change.
  • The owner can preview and control what's public.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.