Explorer Interface Brief

Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an image-model prompt for the interface mock. First step of explorer-pipeline.

1,573 stars 281 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add mohitagw15856/pm-claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mohitagw15856/pm-claude-skills --skill explorer-interface-brief
Manual install
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-claude-skills/plugins/pm-3d-explorer/skills/explorer-interface-brief ~/.claude/skills/explorer-interface-brief

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Explorer Interface Brief

A 3D explorer (a heart, a jet engine, a cell, a volcano) succeeds or fails on its interface: where the model sits, how labels read against it, how a learner moves between free exploration and testing themselves. This skill turns a topic into a design brief a builder can follow and an image-model prompt that produces a convincing mock of the screen before any 3D work starts.

## Required Inputs

Ask for these if not provided:
- **Topic** and the specific object or system to explore
- **Audience**: age or level (for example 14-year-old students, first-year medical students, museum visitors)
- **Learning goal**: what the learner should be able to name, explain or do afterwards
- **Devices**: classroom laptops, phones, a museum touch screen
- **Brand or colour constraints**, if any

## Output Structure

### 1. Design brief
- **Purpose**: one sentence: who explores what, to learn what
- **Audience notes**: reading level, prior knowledge, device and setting
- **Learning outcomes**: three to five, each starting with a verb (name, locate, explain)
- **Layout**: the model stage, a side panel (or bottom sheet on phones) with the selected part's label, description and source, a parts list, and a toolbar (exploded view, quiz mode, reset). Give proportions for desktop and phone.
- **Interactions**: rotate, zoom, select (click, tap and keyboard via the parts list), exploded view, quiz mode, reset. State the response to each.
Read the full skill on GitHub

Details

Skill name
explorer-interface-brief
Path
plugins/pm-3d-explorer/skills/explorer-interface-brief/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Explorer Interface Brief skill do?

Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an image-model prompt for the interface mock. First step of explorer-pipeline.

How do I install the Explorer Interface Brief skill?

Claude Code plugin: /plugin marketplace add mohitagw15856/pm-claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Explorer Interface Brief popular?

It lives in mohitagw15856/pm-claude-skills, which has 1,573 GitHub stars and 281 forks, and is included in 1 curated skill list.

Related skills

Ab Test Planner

1.6k

mohitagw15856/pm-claude-skills

Diseña pruebas A/B estadísticamente rigurosas para características de producto, cambios de UI, flujos de onboarding y experimentos de precios. Úsalo cuando te pidan configurar un experimento, diseñar una prueba A/B, calcular tamaño de muestra o interpretar resultados de pruebas. Produce un plan de prueba completo con hipótesis, definición de variantes, tamaño de muestra, estimación de duración, métricas de seguridad y una guía de interpretación de resultados.

Testing & QAIn 1 list281

Ab Test Planner

1.6k

mohitagw15856/pm-claude-skills

प्रोडक्ट फ़ीचर, UI बदलाव, ऑनबोर्डिंग फ़्लो और प्राइसिंग प्रयोगों के लिए सांख्यिकीय रूप से कठोर A/B टेस्ट डिज़ाइन करें। जब कोई प्रयोग सेट करने, A/B टेस्ट डिज़ाइन करने, सैंपल साइज़ निकालने या टेस्ट के नतीजे समझाने को कहे, तब इसका उपयोग करें। परिकल्पना, वेरिएंट की परिभाषा, सैंपल साइज़, अवधि का अनुमान, गार्डरेल मेट्रिक और नतीजों की व्याख्या की गाइड के साथ एक पूरा टेस्ट प्लान तैयार करता है।

Testing & QAIn 1 list281

Accessible Travel Planner

1.6k

mohitagw15856/pm-claude-skills

Summarise what Accessible Travel Planner does in one line. Use when asked to [trigger phrases the user would say]. Produces [the concrete artifact].

Frontend & DesignIn 1 list281

Landing Page Copy

1.6k

mohitagw15856/pm-claude-skills

Write full landing-page copy that converts — section by section. Use when asked to write a landing page, homepage copy, a product page, or copy for a marketing site. Produces complete copy for every section (hero, problem, solution, social proof, features-as-benefits, objections/FAQ, final CTA) with a clear single conversion goal and one primary call to action.

Frontend & DesignIn 1 list281

Difficult Conversation

1.6k

mohitagw15856/pm-claude-skills

Prepare for and script a hard conversation — conflict, bad news, a boundary, an apology. Use when asked to prepare for a difficult conversation, address a conflict, deliver bad news, confront a colleague, or have a hard talk with a manager/report/peer. Produces a prep brief — the real goal, the other side's likely view, an opening line, the key points, anticipated reactions with responses, and the outcome you want.

Frontend & DesignIn 1 list281

Year in Review

1.6k

mohitagw15856/pm-claude-skills

Run an honest personal year-in-review and set next year's direction — wins, misses, an energy audit, and one theme, not a resolution list that dies in February. Use when asked for a personal year in review, a yearly reflection, to reflect on the past year, or plan next year. Produces the structured retrospective (what worked, what didn't, what you learned), an energy audit of what gave vs. drained you, the honest misses, and a single theme with a few concrete commitments. Personal, not corporate.

Frontend & DesignIn 1 list281

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.