Profile Workspace Default Template and First-Run Content

Where you see this in the app

This page documents the default shape a newly provisioned profile workspace starts with before the creator begins customizing it.

Users usually experience this indirectly the first time the app bootstraps a profile workspace for them.

Default profile workspace template

A new profile workspace is not meant to begin from a totally empty void.

The app uses a default profile-workspace template and default runtime assumptions so the first-run workspace already has a sensible professional starting point.

From an end-user perspective, this means a fresh profile workspace can start closer to a prepared professional workspace than to a blank scratchpad.

Starter body and files

The first-run content can include a starter profile-workspace body and suggested files.

Typical examples include guidance like:

• profile.md
• services.md
• pricing.md
• AGENTS.md

Users should treat these as starter structure hints, not as locked required files.

Runtime defaults on first run

The default template also influences first-run runtime expectations.

That can affect how the new profile workspace behaves before the user manually changes later workspace defaults or swaps templates.

This is why first-run behavior may already feel opinionated even before the creator opens template selection themselves.

How this differs from later template changes

First-run seeding is automatic setup behavior.

Later template changes are an explicit creator action through workspace template controls.

Users should distinguish:

• automatic initial seeding,
• deliberate later replacement.

Related docs

• Profile workspace bootstrap and featured post reuse
• Workspace templates, pools, and replace behavior
• Workspace defaults, env vars, and runtime commands