Launch a standard social experience

Choose this path when you want a standard social surface live quickly — a community feed, chat, stories — using social.plus UIKit’s prebuilt screens, themed to your brand.

What to ask

Use social.plus UIKit to launch a standard community feed in this app.
Recommend the lowest customization level that fits our design system,
and don't hand-roll standard surfaces from SDK primitives.

What your agent will ask you

The usual product questions — platform, screen or route, region, identity — plus one that’s specific to UIKit:

How much to customize. The agent recommends the lightest level that fits your design system: theming and dynamic UI, component styling, localization, behavior overrides, or fork-and-extend as a last resort. You confirm the choice; it’s recorded with the rest of the plan.

Staying on the UIKit path

The skill keeps the agent honest about the boundary. Once UIKit is the chosen route, UIKit’s installation, provider, behavior, and customization guidance is the implementation source — the agent shouldn’t quietly rebuild a standard feed from raw SDK calls. Mixing in direct SDK code is reserved for behavior that’s genuinely differentiated for your app.

What “done” looks like

Vise validates everything your app owns — SDK setup and region, authentication, configuration, and your project’s own build, lint, and test checks. What it can’t see inside prebuilt UIKit internals it won’t claim to have verified. A themed UIKit screen still deserves product QA and a real launch before you ship it.

Choose an integration path

Compare UIKit with a custom SDK experience.

Build a custom social experience

Need a differentiated experience? Build directly on the SDK.

Choose how to build your social experience Build a custom social experience

⌘I

​What to ask

​What your agent will ask you

​Staying on the UIKit path

​What “done” looks like

​Related