Skip to documentation
Design Studio AI
DocumentationCommunity
FEATURE GUIDES

Community

Publish, discover, download and remix shared designs.

Community is a free place to discover, download and remix designs. Your private projects remain private until you explicitly publish a reviewed version.

Find something worth making your own

Search titles, descriptions, tags and creator names. Combine category, format, time and creator filters with Trending, Newest, Most used, Most downloaded or Relevance. Most used and Most downloaded count eligible unique people, not raw transfers. Search and filters stay in the URL.

Cmd+K or Ctrl+K searches your projects on Home and community designs on Community. The visible Search control works without a keyboard. Save designs to a private collection when signed in.

Publish with confidence

  1. Save the project and choose Publish to Community.
  2. Create your public creator profile, choose a title, description, tags, cover and download formats.
  3. Review the public projection and source disclosures. Hidden content, notes and unrelated media are removed; painting is shared as a composite.
  4. Confirm that you can share the included material under CC-BY-4.0 and explicitly approve public publication.
  5. Follow the durable job until it succeeds. Its operation ID lets an uncertain request be retried without publishing twice.

Private edits do not change the published version. Publish an update deliberately. Unlisting stops new public requests; files already downloaded and completed private remixes remain available. The existing Share link is managed separately.

Under Download formats, All selects or clears every available optional format; the Studio project package is always included. PNG sequence and spritesheet show a Frame archive FPS setting. Its recommended default keeps the full animation and original dimensions within the render budget; video downloads stay at 30 fps. Review this frame rate before confirming. Unsupported frame budgets are rejected during preflight, before a publication build starts.

After confirmation, the dialog shows build progress. Congratulations appears only when all selected files are ready and the design is live, with a link to view it. A failed build shows its error and lets you return to the details to correct it.

Draft your public profile with AI

Choose Generate with AI to suggest a public display name, handle and bio. The first configured text provider is selected automatically; you can choose another connection and add optional writing instructions. Only the entered profile fields and instructions are sent, using your saved provider model. Provider usage may incur charges. Your account email and private projects are not added as context.

Review the suggestion, choose Use suggestion, edit if needed, then Save public profile. Generating does not save or publish. If you edit the form while generation is running, review those changes before applying a new suggestion. Handles are checked for availability when generated and again when saved. You can always fill in the form manually; connect a text provider in Settings to enable AI drafting.

Draft listing details with AI

Generate with AI is also available alongside Title, Description and Tags in the Publish dialog. It selects your first configured text provider and saved model, or you can choose another connection. Add optional writing instructions to set the language or tone. The provider receives your entered fields and a bounded summary of visible text and structure from the saved design. Notes, hidden content, account identity and media URLs are excluded. This drafts from text and structure, without inspecting the cover image; provider usage may incur charges.

Review the separate suggestion, then choose Use suggestion to fill the editable fields. Nothing is saved or published. Applying a suggestion clears the previous publication review and consent, so run preflight again. Manual edits or a changed saved revision block stale suggestions. You can retry generation, load the current saved revision, connect a provider in Settings, or continue manually.

Agents use community_generate_metadata, studio_community_generate_metadata, or dsa community generate-metadata --file request.json. Supply the owned projectId and observed expectedProjectRevision, plus optional provider, title, description, tags and prompt. Review the returned suggestion before a separate preflight and explicit publication.

Download, import and remix

Guests can download already-built files. A portable design ZIP contains the canonical document, included assets, license and attribution. Import creates a new private project with its own asset copies. Packages allow up to 20 MiB compressed, 64 MiB expanded and 1,000 entries. External media dependencies must be imported before publication; packages never fetch source media during import.

Signed-in Remix also creates an independent private project with attribution. Publishing that remix is a separate confirmation. Imported attribution is marked unverified; an archive cannot grant creator milestones.

Recognition that reflects usefulness

Your Impact view shows server-confirmed downloads and remixes, plus contribution milestones. Self-actions and repeated actions from the same account do not inflate qualifying counts. Curated collections give useful work another way to be discovered. Reporting a design sends the selected version and your reason to authorized moderators.

Agent workflow

Discover /api/schema → community, community_capabilities over MCP, or studio_community_capabilities in a supported Community browser tab. MCP and WebMCP expose the same named operations as dsa community --help. Community WebMCP tools are scoped to Community pages.

dsa community search --q "portfolio" --kind web --sort relevance
dsa community get LISTING_ID
dsa community preflight --file preflight.json
# Show the projection, disclosures and license to the author first.
dsa community publish --file confirmed-publication.json
dsa community job OPERATION_ID
dsa community download LISTING_ID VERSION FILE_ID --out design.zip
dsa community import --file design.zip --operation-id UNIQUE_ID

JSON mutation files use the canonical schema and observed revisions. Never invent a digest, substitute a newer revision, or treat preflight as consent. MCP and WebMCP base64 package import is limited to 12 MiB; use CLI or the browser file picker for larger packages. MCP binary results above 12 MiB also use CLI downloads.

Hosting and moderation

Enable COMMUNITY_ENABLED=true after applying migrations. Moderation uses COMMUNITY_ADMIN_IDS for existing account IDs. Optional COMMUNITY_ADMIN_EMAILS pregrants are claimed only after GitHub verifies those email identities. Password registration alone does not claim a pregrant. Keep those settings private and separate from observability admins. Moderator actions require a session or API key; OAuth never grants moderation.