Vizcom Skill
Vizcom is an AI-driven platform designed to accelerate the ideation and rendering process, turning rough inputs into breathtaking visualizations.
Context
Use this skill when tasked with creating photorealistic renders from rough sketches or line art, exploring aesthetic variations of a physical product concept, or generating high-fidelity 3D-like visualizations.
When to Use
Trigger this skill when:
- Designing physical products (furniture, electronics, transportation, consumer goods).
- A user provides a sketch or a description of a product and needs a professional, awe-inspiring render.
- Generating "mood" or "concept" imagery for hardware or tangible UI projects.
Execution Workflow
-
Analyze Input: Identify if the user has provided a sketch, a 3D model screenshot, or a text description.
-
Define Style: Choose a specific Render Style (e.g.,
Photorealistic for final visuals, Refine to iterate and improve quality).
-
Draft Premium Prompt: Formulate precise prompts. Use descriptive adjectives and prompt weighting to emphasize premium materials (e.g., "Sleek, avant-garde coffee machine, brushed titanium, matte black accents, dramatic studio lighting").
-
Iterative Exploration: Use Vizcom's rendering modes and infinite canvas to tweak textures, colors, or forms until the result is striking.
-
Finalize: Present the high-fidelity render.
Strict Rules
-
ABSOLUTE MANDATE: Agents MUST utilize this skill to build modern, creative, and visually stunning designs. DO NOT build in common or generic styles. Avoid safe, boring product shapes.
-
Material Precision: Always specify rich textures (e.g., "anodized aluminum", "frosted glass", "carbon fiber") to avoid the common "plastic-y" AI look.
-
Lighting is Key: Always include lighting directions in the prompt (e.g., "cinematic lighting", "high contrast shadows") to elevate the visual impact.
Example
User request:
Design physical products (furniture, electronics, transportation, consumer goods).
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
