Question
What should Skill Manager's default opening surface be for the human fleet operator?
Reference pass
Before building the prototype variants, run the reference-driven design workflow rather than inventing a direction from the current screen:
- Use
npx -y mobbin-axi for real product UI references. Pull web screens and sections with specific queries, use --download, view the actual images, and cite every reference used with its returned Mobbin URL. Do not infer a design from result titles alone.
- Review 21st.dev, Land-book, and Magic UI as explicit sources for component, landing-page, and motion inspiration.
- Use the existing Outline reference shelf as additional input: AuxUI Resources, OpenCode Resources, Skills, and Customizations. Relevant candidates include Awwwards, TypeUI, FOREVER, TheGallery, and Hallmark.
- Distill the references into one committed direction and concrete tokens or a small moodboard artifact. Borrow interaction and layout patterns, not brand identity or copied screens.
Image-quality floor
- Diagnostic vision probes must be at least 32x32 pixels, or 1,024 total pixels. Tiny 8x8 probes are invalid for providers with minimum-image-size checks.
- Reference and prototype images must be at least 1,024 pixels wide, with 1,440 pixels or more preferred for UI detail review.
- Preserve downloaded reference files at their source resolution. Do not upscale a lower-resolution Mobbin download and describe it as high fidelity.
- Measure the actual dimensions of every downloaded reference. In the sampled Mobbin AXI call, the MCP short URL and cached
--download file were identical 768x521 or 768x523 WebP files, and the wrapper performed no resizing. Do not assume this is Mobbin's maximum quality: if the Mobbin website or an underlying asset exposes a higher-resolution version, prefer it and record the dimensions; otherwise use the MCP image for composition and interaction patterns and supplement typography/detail review with higher-resolution captures from the reference site or the prototype itself.
- Prototype review captures should target at least a 1,280px viewport width, preferably 1,440px or more.
Prototype
Create a throwaway UI prototype that lets the user compare three shells using the same representative tasks and data:
- Attention-first: open on health, uncertainty, drift, pending reviews, and next safe actions.
- Browse/catalog-first: open on the complete skill inventory and fleet overview.
- Skill-workspace-first: open on a selected skill and its provenance, evidence, variants, and operations.
Use the approved reference direction and the current dark Genome language as inputs, but make the differences in hierarchy, navigation, density, and action discoverability obvious. Exercise at least drift diagnosis, explain, origin assignment, adaptation review, and verified apply. The prototype must be clearly throwaway, easy to run, and linked from this issue when complete.
Resolve the ticket through live human reaction: choose the default shell, record the rationale, and identify any elements borrowed from the other two shells and from the reference pass. Do not implement production UI here.
Question
What should Skill Manager's default opening surface be for the human fleet operator?
Reference pass
Before building the prototype variants, run the reference-driven design workflow rather than inventing a direction from the current screen:
npx -y mobbin-axifor real product UI references. Pull web screens and sections with specific queries, use--download, view the actual images, and cite every reference used with its returned Mobbin URL. Do not infer a design from result titles alone.Image-quality floor
--downloadfile were identical 768x521 or 768x523 WebP files, and the wrapper performed no resizing. Do not assume this is Mobbin's maximum quality: if the Mobbin website or an underlying asset exposes a higher-resolution version, prefer it and record the dimensions; otherwise use the MCP image for composition and interaction patterns and supplement typography/detail review with higher-resolution captures from the reference site or the prototype itself.Prototype
Create a throwaway UI prototype that lets the user compare three shells using the same representative tasks and data:
Use the approved reference direction and the current dark Genome language as inputs, but make the differences in hierarchy, navigation, density, and action discoverability obvious. Exercise at least drift diagnosis, explain, origin assignment, adaptation review, and verified apply. The prototype must be clearly throwaway, easy to run, and linked from this issue when complete.
Resolve the ticket through live human reaction: choose the default shell, record the rationale, and identify any elements borrowed from the other two shells and from the reference pass. Do not implement production UI here.