How work travels

Discovery and Social Model

Runnable work becomes more useful when people can find it, understand it, discuss it, and trace where it came from.

Discovery and social visibility guide for Vibecodr runnable work.

Implementation focus

Use this when shaping tags, topics, profile copy, comments, remix lineage, public visibility, or social reporting expectations around a vibe.

Expected outcomes

Understand where public work can appear.
Use tags and topics intentionally.
Know which social actions are public context versus personal organization.
Recognize how moderation can change reach without changing release identity.

Discovery is product context, not raw indexing

Vibecodr discovery surfaces help people find runnable work through profiles, feeds, search, tags, topics, conversations, comments, remix lineage, and public metadata. They are not raw source indexes and they do not expose private drafts.

Good social context helps a viewer understand what a vibe does, who made it, what it remixes, and where related work lives. That context should be public-safe and useful without revealing owner-only setup.

Use titles and descriptions that describe what the app does.
Use tags for concrete themes or technology people might search.
Use topics for broader public collections and community context.
Use comments and conversations for feedback, questions, and launch notes.

Visibility and moderation affect reach

Search, feeds, and external crawlers follow public visibility and platform safety decisions. Saves and private bookmarks are personal organization, while likes, comments, follows, remix lineage, tags, and topics can become public context around the work.

Blocks, mutes, reports, and moderation actions can change what people see in social surfaces without changing the underlying release model. If a public route or listing looks wrong, check both metadata and visibility state before changing source code.

Public work can appear in feeds, profiles, topics, tags, link previews, and search.
Unlisted work is better for direct sharing than broad discovery.
Private drafts are not discovery entries.
Moderation can reduce or remove visibility when safety rules require it.

Example and read next

Example: a vibe should be easy to find from a topic page. Use clear metadata, relevant tags, social context, and remix lineage while keeping private drafts and owner-only setup out of discovery.

Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.