// Tests whether a solution is more complex than it needs to be — distinguishing necessary complexity from accidental complexity that accreted over time. TRIGGERS: 'elegance test', 'is this too complex', 'over-engineered', 'is there a simpler way', 'does this feel right'.
Master orchestration skill. Takes any situation in plain English, identifies the underlying goal, designs a multi-skill reasoning workflow, and executes it sequentially — feeding each skill's output into the next. Use when you say 'help me think through this', 'I need to figure out what to do', 'where do I start', or any time you want structured thinking applied end-to-end rather than routed to a single tool.
Tests whether the parts of something form a unified whole — finding the jarring inconsistencies that accumulate when different contributors work without a shared vision. TRIGGERS: 'coherence check', 'does this feel unified', 'something feels off', 'inconsistent', 'check the whole', 'does this hang together'.
Identifies the underlying formal pattern at work — because most successful designs, arguments, and solutions share deep structural patterns, and naming the pattern unlocks the playbook. TRIGGERS: 'what pattern is this', 'pattern recognition', 'why does this work', 'identify the form', 'what structure is at play', 'what archetype is this'.
Finds the simpler version while preserving what matters — not arbitrary reduction, but finding the core and discarding what is not it. TRIGGERS: 'find the simple version', 'simplify this', 'what's the essence', 'less but better', 'strip it back', 'what could we remove'.
Entry point for the aesthetic toolkit. Routes to the right aesthetic skill based on your situation. Use when you say 'aesthetic', 'check the design', 'does this feel right', 'is this elegant', 'is this too complex', 'what pattern is this', 'find the simpler version', or want an aesthetic lens applied without knowing which specific tool fits.
Finds where an analogy breaks down before it's relied upon. Analogies fail silently — the damage happens when decisions are made on a mapping that doesn't hold in the relevant dimension. Triggers: 'stress-test this analogy', 'where does this comparison break', 'does this really apply', 'test the metaphor', 'where is the analogy wrong'.
| name | s4h-aesthetic-elegance-testing |
| description | Tests whether a solution is more complex than it needs to be — distinguishing necessary complexity from accidental complexity that accreted over time. TRIGGERS: 'elegance test', 'is this too complex', 'over-engineered', 'is there a simpler way', 'does this feel right'. |
Complexity is the default outcome of design by committee, incremental revision, and deference to edge cases. Each addition is locally defensible. The cumulative result is a system no one would have designed on purpose. Elegance is not simplicity for its own sake — it is the property of a solution where every element earns its place and nothing obscures the core. This skill tests for that property.
Step 1: State the Solution Describe the design, plan, system, or solution in enough detail to evaluate its parts. If it's a process, name the steps. If it's a system, name the components. If it's a strategy, name the moves.
Framing check: Confirm the specific solution before continuing. State what you've identified — the actual artifact being tested and its apparent purpose — in one sentence, then use AskUserQuestion:
Step 2: Define the Irreducible Core What is the minimum that does the job? State in one sentence what the solution must accomplish to succeed. Every element that doesn't directly serve this core is a candidate for removal. If you can't state the core in one sentence, the solution may not have one — which is itself a finding.
Step 3: Element Audit For each component, mechanism, layer, or step: is it necessary for the core job, or did it accrete over time to handle edge cases, satisfy stakeholder requests, hedge against unlikely scenarios, or address problems that may not exist? Label each clearly: necessary or accreted.
Step 4: Concept Count How many distinct concepts must a new person learn to understand and use this solution fully? Elegant solutions have fewer. Count them explicitly. Compare against the irreducible minimum — the number of concepts required if every accreted element were removed. The gap is the complexity overhead.
Step 5: Thirty-Second Explanation Test Can you explain the solution in 30 seconds to someone intelligent but unfamiliar with it? Attempt the explanation. If it requires more than 30 seconds, complexity may be genuine — or it may be a sign the design hasn't been thought through clearly enough to be simple. Both are worth knowing.
Step 6: Sources of Unnecessary Complexity For each accreted element: what introduced it, and what would removing it cost? Some removals are free — the element was pure noise. Some involve real trade-offs — the element serves a secondary purpose worth naming. Distinguish them explicitly.
Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:
Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.
Core Job: [one sentence — what the solution must accomplish to succeed]
Element Audit
| Element | Necessary or Accreted | Rationale |
|---|---|---|
| [component/mechanism/step] | [necessary / accreted] | [why it does or doesn't serve the core] |
Concept Count: [n currently required] vs [n at irreducible minimum] — overhead: [gap]
30-Second Explanation Test: [pass / fail — include the actual attempt]
Sources of Unnecessary Complexity
| Accreted Element | How It Was Introduced | Cost of Removal |
|---|---|---|
| [element] | [origin] | [what is lost if removed] |
Recommended Simplifications: [specific removals or reductions, with trade-offs named]
The question is not "can we defend every element" but "does every element earn its place." Elements that can be defended are not the same as elements that are necessary — hold the higher bar. Elegance is achieved not when there is nothing left to add, but when there is nothing left to remove.
After delivering this output, use AskUserQuestion to offer the next move:
/s4h-aesthetic-simplicity-analysis — Simplify what elegance testing flagged as complex/s4h-writing-prose-elevation — Elevate prose flagged as inelegant/s4h-aesthetic-coherence-check — Verify that elegance is coherent with the whole