site-phase-3

Separate emotional and technical website design into isolated agent processes.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/felipemlanna1/vendedor-de-sites-v2 --skill site-phase-3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-phase-3
Source: https://github.com/felipemlanna1/vendedor-de-sites-v2/tree/main/.claude/skills/site-phase-3
Command: npx skills add https://github.com/felipemlanna1/vendedor-de-sites-v2 --skill site-phase-3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the issue of distributional convergence and local-maxima shift in technical decisions by isolating the emotional and technical aspects of site design.

Core Features & Use Cases

  • Emotional Concept Architect: Develops emotional-only site concepts based on briefings and Phase 2 immersion.
  • Technical Translator: Translates emotional concepts into technical blueprints with Verbalized Sampling.
  • Isolated Agents: Ensures that the Technical Translator does not unconsciously choose default technical patterns.
  • Use Case: For a site design project, use this Skill to create a concept that is then translated into a technical blueprint, avoiding the pitfalls of a single, combined context.

Quick Start

Run the site-phase-3 skill to generate emotional and technical designs for your site project.

Frequently Asked Questions about site-phase-3

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is distributional convergence in site design and how do I prevent it?

Isolating emotional site design from technical translation prevents distributional convergence by ensuring the Technical Translator does not unconsciously choose default patterns, improving the diversity of technical decisions.

How do I translate emotional design concepts into technical site blueprints?

Translating emotional design concepts into technical site blueprints requires using a Technical Translator agent with Verbalized Sampling, converting isolated emotional concepts into structured technical architecture without falling into default pattern traps.

Why does my website architecture end up looking like generic templates?

Website architecture often looks generic due to distributional convergence, where technical decisions unconsciously align with default patterns. Combining emotional and technical design in a single context causes this local-maxima shift toward repetitive structures.

Can I separate emotional site design from technical architecture decisions?

Separating emotional site design from technical architecture decisions is achievable by using isolated agents like the Emotional Concept Architect and Technical Translator, preventing unconscious pattern defaults during the design process.

What are the limitations of combining emotional and technical site design in one process?

Combining emotional and technical site design in a single process risks distributional convergence, where technical decisions shift toward local maxima. This combined context limits the diversity of technical outcomes and creates generic site architecture.