studio-3d-hero

Category: Data & AI | Uploader: Mijiang111 | Downloads: 0 | Version: v1.0（Latest）

Use when a Studio deck should explain one system, architecture, chip, engine, platform, device, or core object through a dominant pseudo-3D HTML/CSS hero model page. Focus on left narrative, right single model, strong spatial depth, and restrained executive presentation without dashboard clutter.

Changelog: Source: GitHub https://github.com/Mijiang111/claw-design

Directory Structure

Current level: tree/main/server/skills/studio-3d-hero/

📁 references/
- 📄 composition-families.md 1.6 KB
- 📄 material-and-annotation-language.md 708 B
- 📄 object-grammar-chip-platform.md 3.0 KB
- 📄 prompt-examples.md 1.2 KB
📄 SKILL.md 2.5 KB

SKILL.md

---
name: studio-3d-hero
description: Use when a Studio deck should explain one system, architecture, chip, engine, platform, device, or core object through a dominant pseudo-3D HTML/CSS hero model page. Focus on left narrative, right single model, strong spatial depth, and restrained executive presentation without dashboard clutter.
---

# Studio 3D Hero

Use this skill when a page should explain one complex object or system, not a chart or dashboard.

3D is opt-in only. Do not use this skill just because the brief mentions systems, platforms, chips, or architecture in general. Only use it when the brief explicitly asks for a 3D, cutaway, exploded, or hero-model style concept page.

## Trigger cues

- The subject is a chip, platform, interconnect fabric, system architecture, device, or layered technical object.
- The page needs to answer "what this thing is" or "how this architecture is built".
- The page should elevate one concept object instead of many equal-weight cards.

## Core rules

- Use at most one 3D hero page in a deck unless the brief explicitly asks for more.
- Keep one dominant hero object, usually on the right, with short narrative on the left.
- The object is the explanation, not decoration.
- Do not turn the page into a dashboard, icon collage, or card grid.
- Do not place long copy below the model.
- One page should still make one point: one object explanation, one main claim, and at most a few terse labels or support bullets.

## Pseudo-3D rules

- Use HTML/CSS only.
- Create depth with perspective, layered planes, thickness, seams, highlights, shadows, and restrained labels.
- Prefer one coherent fabricated object with internal hierarchy over many disconnected parts.

## Repair rules

- Preserve the hero object and its composition family first.
- Compress left narrative, labels, and footer before touching the object.
- Only simplify outer annotations or ornament if fit still fails.
- Only as a last resort may the page fall back to a simpler structure diagram.
- Do not convert an ordinary page into a 3D hero page during repair unless the page already clearly contains 3D hero cues.

## References

- For chip, platform, or interconnect object language, read `references/object-grammar-chip-platform.md`.
- For composition families such as cutaway, exploded stack, or layered slab, read `references/composition-families.md`.
- For material tone and labeling language, read `references/material-and-annotation-language.md`.
- For short example patterns, read `references/prompt-examples.md`.

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

studio-3d-hero

Directory Structure

SKILL.md

Report

Notice