Claude Design pack — Assets¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Pack id AIF-UX-ASSETS · reads with the master brief · 11 screens.
1. Alignment¶
This pack covers the Assets work area of the Factory Studio. Design the screens below as high-level pages, flows and states; do not design element-level components beyond the design-system catalog. Every simulated action is fixture behaviour and says so.
2. Design prompt¶
Produce an interactive prototype of the Assets work area: the screens, their states from the state families, the flows that pass through them with their adverse branches, in light and dark, LTR (en, ru) and RTL (he), keyboard-first, WCAG 2.2 AA.
3. Sources¶
- Screens: screens catalog · states: states catalog · permissions: permissions catalog
- Prototype references:
ConnectSoft AI Software Factory.dc.htmldestinationsagentmesh,skills,agentmesh,runs,templates,marketplace,packversions,packcomposer;ConnectSoft Design System.dc.html,ConnectSoft Component Catalog.dc.html,ConnectSoft Developer Handoff.dc.htmlinC:/Git/ConnectSoft/ConnectSoft.DesignPrototypes/. - Alignment decisions: prototype alignment.
4. Personas, routes and layout¶
| Persona | Role | Enters this area for |
|---|---|---|
| Lena | AssetMaintainer | Take an agent, skill or template from Draft to Published with evidence; Act on learning proposals |
| Eli | PlatformAdmin | Publish policies, profiles and templates that tenants may only tighten; Certify publishers and connectors |
| Screen | Route | Layout |
|---|---|---|
asset-catalog — Asset catalog |
/assets |
read-only list or detail; no action rail |
release-detail — Asset release |
/assets/{assetId}/releases/{version} |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
agent-card — Agent card |
/assets/agents/{agentId} |
read-only list or detail; no action rail |
tool-descriptor — Tool descriptor |
/assets/tools/{toolId} |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
mcp-servers — MCP servers |
/assets/mcp |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
model-profiles — Model profiles and deployments |
/assets/models |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
workflow-definitions — Workflow definitions |
/assets/workflows |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
template-catalog — Template catalog |
/assets/templates |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
marketplace-browse — Marketplace |
/marketplace |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
marketplace-installations — Installations and entitlements |
/marketplace/installations |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
publisher-console — Publisher console |
/marketplace/publisher |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
5. Interaction¶
Flows passing through this area: publish-asset, manage-editions-and-billing. A command returns the server's outcome (202, 403, 409, 412, 422) rendered in words; the BFF never retries; a 412 re-renders the newer proposal.
6. Mock data¶
Use the shared fixtures of the fixtures page only; label every number as fixture data; never real customer data.
7. State and permission matrix¶
| Screen | State families | Roles |
|---|---|---|
asset-catalog |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | Requester, Reviewer, AssetMaintainer, PlatformAdmin, Observer |
release-detail |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Approval (Pending, Approved, Rejected, Expired, Superseded) | AssetMaintainer, Reviewer, PlatformAdmin, Observer |
agent-card |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | Requester, AssetMaintainer, Observer |
tool-descriptor |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | AssetMaintainer, PlatformAdmin, Observer |
mcp-servers |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Deployment availability (Registered, Evaluating, Approved, Active, Degraded, Retired) | PlatformAdmin, AssetMaintainer, Observer |
model-profiles |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Deployment availability (Registered, Evaluating, Approved, Active, Degraded, Retired) | PlatformAdmin, AssetMaintainer, Observer |
workflow-definitions |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | AssetMaintainer, PlatformAdmin, Observer |
template-catalog |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | AssetMaintainer, PlatformAdmin, Observer |
marketplace-browse |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Approval (Pending, Approved, Rejected, Expired, Superseded) | Requester, AssetMaintainer, WorkspaceAdmin, Observer |
marketplace-installations |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Usage (Estimated, Reserved, Observed, Reconciled, Uncertain) | WorkspaceAdmin, AssetMaintainer, Observer |
publisher-console |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Approval (Pending, Approved, Rejected, Expired, Superseded) | AssetMaintainer, PlatformAdmin |
| Global states on every screen: loading skeleton; empty with the permitted next action; validation error; dependency degraded with freshness; permission denied with explanation; stale version conflict with the newer version rendered; success with scope and version. |
8. Accessibility criteria¶
Keyboard-only operation; visible focus; landmarks; live regions for realtime updates; 24×24 targets; contrast 4.5:1 text and 3:1 UI in both schemes; RTL mirrored for he with identifiers LTR; reduced motion honoured; status by text and icon, never colour alone (see localization and accessibility).
9. Expansion instructions¶
Screens marked missing in the prototype are new designs; generic placeholders become dedicated views; keep the design-system tokens and the seven-status palette; do not invent destinations outside the screens catalog. Future-phase screens stay designed with a Proposed badge.