cross-domain-synthesislisted

Cross-domain synthesis skill. Combines knowledge from completely different fields to generate novel, practical insights — not analogies for their own sake, but structural borrowings where the mechanism in domain A directly solves the problem in domain B. Activates when the user wants unconventional approaches, is stuck in their domain's standard thinking, or explicitly wants to borrow from another field. Finds the structural isomorphism — not just a surface metaphor. Use when user says: cross-domain, think outside my field, what would X think, borrow from another discipline, combine these fields, unconventional approach, think like a biologist / game designer / architect, apply X to Y, what does another field say about this, novel approach, think differently, synthesize across domains, first principles from another field. Do NOT activate for: domain-specific questions where conventional expertise is what the user actually needs, requests that are already cross-domain framed. First response: "Cross-Domain Synt
Sandeeprdy1729/claude-design-skill · ★ 2 · Web & Frontend · score 71

Install: claude install-skill Sandeeprdy1729/claude-design-skill

# Cross-Domain Synthesis "Think outside the box" is the most useless advice in problem-solving. It says where not to look, not where to look. Cross-domain synthesis is specific: find the field that has already solved your problem under a different name, extract the mechanism (not the metaphor), and apply it directly. Evolutionary biology solved distributed consensus before computer science named it. Game design solved engagement loops before B2B SaaS needed them. Urban planning solved pedestrian throughput before stadium architects did. The skill is knowing which domain to borrow from and how to transplant the mechanism without losing its function in translation. --- ## SLASH COMMANDS | Command | Action | | --- | --- | | `/synthesize <problem>` | Find the domains that have solved this problem and extract mechanisms | | `/map <domain>` | Map a specific domain's core mechanisms to the user's problem space | | `/bridge <domain-a> <domain-b>` | Find structural isomorphisms between two domains | | `/mechanism <name>` | Extract a specific mechanism from its source domain for application | | `/rotate <problem>` | Reframe the problem using 5 different domain lenses | | `/apply <mechanism> <context>` | Apply a specific borrowed mechanism to the current context | | `/tension` | Find where the borrowed mechanism breaks down in the new domain | | `/combine <domain-a> <domain-b> <problem>` | Force-combine two domains' approaches to a single problem | | `/invert` | Ask what the oppos