UI field guide

This section documents the current CFarm interface contract. It is organized by destination and visible interaction state rather than by source file.

Production screenshots were captured at 1440 x 900 for desktop and 390 x 844 for mobile on 29 July 2026. The remaining imagery was exported from the LumenClip Paper design file on 1 August 2026 from boards traced against the shipped UI. Screenshots are reference imagery, and the written behavior takes precedence where they disagree.

Current workspace layout contract

• /app is one authenticated, tabbed workspace. Its visible destination is addressed by the view query parameter rather than by a route per destination.
• The six workspace destinations are Home, Compose, Schedule, Analytics, Collections, and Templates. Their query values are home, compose, schedule, analytics, collections, and templates.
• Template deep links keep the Templates destination selected and add template=<id> or run=<id> to the workspace query.
• Collection detail at /app/collections/[id], post analytics at /app/analytics/posts/[id], the testing facility at /app/testing, X/Threads post studio at /app/x-automations, UGC run status at /app/ugc/[id], and analytics previews at /analytics-preview/[platform] are separately routed surfaces.
• Public, authentication, documentation, shared slideshow, legal, and system pages also use their own routes outside the authenticated workspace.
• In-app page and section headings stand alone. The interface does not add explanatory subtitles beneath them.

Route reference

• Browser routes

Page map

Workspace shell

• Application shell
• Navigation
• UI primitives
• Media viewers

Home

• Home
• Published posts

Templates

• Templates overview
• Template hooks
• Hook analytics
• Template schedule
• Template settings
• Template social settings
• Template editors
• Text posting templates
• Composition and publish gates
• UGC video templates (WIP)

Compose, Schedule, Analytics

• Compose
• Schedule
• Analytics
• Post analytics
• Analytics preview

Collections and Testing

• Collections
• Collection detail
• Testing facility
• Output trace

Workspace settings

• Notifications
• AI models

Public and system

• Landing
• Authentication
• Shared slideshow
• Documentation shell
• Legal and system

Reading MCP coverage

Yes means the underlying data operation is registered. Partial means some underlying operations exist but a UI-only step remains. No means there is no matching registered operation.

Opening a destination, expanding a card, and opening or closing a dialog are UI navigation and are not expected to have MCP tools.