TRIZ 76 Standard Solutions — guides users through solving technical and organizational problems using Substance-Field Analysis (Su-Field) and the 76 Standard Solutions organized in 5 classes. Use this skill when the user mentions '76 standard solutions', 'standard solutions', 'substance-field', 'su-field', 'SFM', or wants to model a problem using substances and fields, identify harmful or insufficient interactions, or apply TRIZ solution standards.
TRIZ Ideality — optimize technical systems by reducing harm, enhancing usefulness, managing resources, and adding new functions. Use this skill when the user wants to increase system ideality, reduce complexity, improve performance without adding resources, define the ideal system, or mentions 'ideality', 'ideal system', 'ideal final result', 'IFR', or wants to move a system toward its ideal state. Does NOT handle resource analysis in isolation — use triz_resource_analysis for that.
TRIZ Root Conflict Analysis (RCA+) — a domain-independent technique for defining, structuring, and visually representing problems by discovering contradictions. Extends classical Root Cause Analysis by identifying causes that produce both positive and negative effects simultaneously. Applicable to engineering, product, process, service, and business/management problems. Use this skill when the user mentions 'root conflict analysis', 'RCA+', 'Grundkonfliktanalyse', or wants to decompose a complex problem into its underlying contradictions rather than just finding root causes.
TRIZ Problem Operator (Problem-Oriented Nine Screen Approach) — solves problems by analyzing them across a problem timeline (before / during / after the problem) at Super-System, System, and Sub-System levels. The problem is treated as unavoidable; Past explores how to prevent it, Present explores how to address it, Future focuses on how to still reach the overall goal (Plan B / Oberziel) after the problem has occurred. Use this skill when the user describes a specific problem occurring in a system and wants to find solutions. Triggers on 'problem operator', '9 boxes problem', 'problem-oriented', or when the user mentions both a concrete problem and a system. Does NOT handle system evolution — use system-operator for that.
TRIZ System Operator (also known as Multi-Screen Diagram, MSD, 9 Boxes, 9 Screens, 9 Windows, Multi-Screen Thinking) — analyzes technical or business systems across past, present, and future at Super-System, System, and Sub-System levels. Use this skill when the user mentions 'system operator', 'multi-screen', 'MSD', '9 boxes', '9 screens', '9 windows', 'multi-screen diagram', 'multi-screen thinking', or wants to explore how a system evolves over time. Default to technical systems; switch to business if context suggests. Does NOT handle problem-solving — use problem-operator for that.
TRIZ Function-Oriented Search (FOS), Method-Oriented Search (MOS), and Scientific Effects exploration — helps users find inventive solutions by searching for scientific effects, natural analogies, and functionally similar solutions from other domains. Use this skill when the user mentions 'function-oriented search', 'FOS', 'MOS', 'scientific effects', 'AskNature', 'Oxford Creativity', or wants to find how other systems or nature solve a similar function.
TRIZ Contradiction Solver and 40 Inventive Principles — resolves engineering and physical contradictions using the Altshuller Matrix, Matrix 2003, and the 40 Inventive Principles. Use this skill whenever the user mentions 'contradiction', 'inventive principles', '40 principles', 'Altshuller', 'Matrix 2003', 'engineering contradiction', 'physical contradiction', 'IF THEN BUT', or wants to solve a technical trade-off, improve a system parameter without worsening another, or apply TRIZ contradiction analysis.
TRIZ Function Analysis for technical systems — identifies tools, actions, objects, and functions, clarifies component relationships, and reveals the system's main function. Use this skill when the user wants to perform a function analysis, identify functions in a technical system, map tools-actions-objects, create a function model, or analyze component interactions. Also trigger on mentions of 'function analysis', 'function model', 'tool-action-object', or 'function carrier'.