$npx -y skills add human-avatar/skills-for-humanity --skill s4h-aesthetic-pattern-detectionIdentifies 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 f
| 1 | # Aesthetic Pattern Detection |
| 2 | |
| 3 | Surface features differ — colours, words, technologies, industries. Formal patterns |
| 4 | recur across all of them. The same structural moves that make a symphony compelling |
| 5 | make a strategy compelling. The same tension-and-resolution arc that drives a thriller |
| 6 | drives a great pitch. Naming the pattern reveals options that surface-level analysis |
| 7 | cannot, because once the pattern is named, its full playbook becomes available. |
| 8 | |
| 9 | --- |
| 10 | |
| 11 | ## Your Process |
| 12 | |
| 13 | **Step 1: Describe the Thing** |
| 14 | What does it do and how does it feel to engage with it? Focus on behaviour and |
| 15 | effect, not surface features — not "it uses blue and white" but "it creates calm |
| 16 | authority that builds confidence incrementally." Describe the experience of it. |
| 17 | |
| 18 | **Framing check:** Confirm the specific artefact before continuing. State what you've identified — the actual object being analyzed and its medium or domain — in one sentence, then use `AskUserQuestion`: |
| 19 | - **Question:** "I'm reading this as: [your one-sentence framing of the specific artefact and its context]. Is that right?" |
| 20 | - **Header:** "Framing" |
| 21 | - **Options:** |
| 22 | - **Yes — proceed** — framing is correct |
| 23 | - **Adjust** — one element is off; user will correct it before you continue |
| 24 | - **Reframe** — different artefact or context than read; incorporate the correction before proceeding |
| 25 | |
| 26 | **Step 2: Identify Formal Patterns Present** |
| 27 | Work through this list systematically — multiple patterns often operate simultaneously: |
| 28 | - **Repetition/Rhythm** — recurring elements that create expectation, then satisfy |
| 29 | or productively subvert it |
| 30 | - **Symmetry/Asymmetry** — balance creates stability and trust; deliberate |
| 31 | asymmetry creates tension and dynamism |
| 32 | - **Hierarchy** — clear ordering from most to least important, large to small, |
| 33 | general to specific; guides attention |
| 34 | - **Contrast** — sharp differences that create definition, focus attention, and |
| 35 | make meaning by comparison |
| 36 | - **Tension/Resolution** — a problem introduced and resolved, a question posed and |
| 37 | answered; the engine of narrative |
| 38 | - **Figure/Ground** — a subject made vivid and clear by what surrounds and recedes |
| 39 | - **Part/Whole** — components that build into something greater than their sum |
| 40 | |
| 41 | **Step 3: Match to Domain Archetypes** |
| 42 | Which archetypes from design, storytelling, architecture, or music does this |
| 43 | resemble? The hero's journey. The fugue. The golden section. Thesis-antithesis- |
| 44 | synthesis. Call and response. Name the archetype and its source domain. |
| 45 | |
| 46 | **Step 4: Name the Pattern** |
| 47 | **Before narrowing:** Show the complete set of patterns identified in Step 2 to the user first. Use `AskUserQuestion`: |
| 48 | - **Question:** "I've identified [N] patterns at work. Before I select the dominant one, are there any you'd flag as especially significant, or any I've missed?" |
| 49 | - **Header:** "Prioritise" |
| 50 | - **Options:** |
| 51 | - **Proceed with your selection** — the set looks right |
| 52 | - **Flag one** — user will name a specific pattern to treat as dominant |
| 53 | - **Add a missing one** — user will describe a pattern not yet identified |
| 54 | |
| 55 | Give the dominant pattern a precise name. Test: does naming it make the thing more |
| 56 | legible? Does it reveal why certain elements work and why others feel off? A good |
| 57 | pattern name is generative — it produces new options, not just descriptions. |
| 58 | |
| 59 | **Step 5: Apply the Pattern** |
| 60 | What does the pattern imply for what should come next? What is currently in the |
| 61 | artefact that violates the pattern — and is that violation intentional (productive |
| 62 | tension) or accidental (incoherence)? |
| 63 | |
| 64 | --- |
| 65 | |
| 66 | ## Human Check-in |
| 67 | |
| 68 | 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: |
| 69 | |
| 70 | - **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?" |
| 71 | - **Header:** "Scope" |
| 72 | - **Options:** |
| 73 | - **Full analysis** — Complete all steps, reasoning shown throughout |
| 74 | - **Key findings only** — Bottom-line output, skip step-by-step detail |
| 75 | - **Pattern name only** — Identify and name the underlying structure, skip full analysis |
| 76 | - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing |
| 77 | |
| 78 | Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis. |
| 79 | |
| 80 | ## Output Format |
| 81 | |
| 82 | **Formal Patterns Present:** [list each pattern with one sentence on how it manifests] |
| 83 | |
| 84 | **Archetype Match:** [closest domain archetype + which domain it comes from] |
| 85 | |
| 86 | **Pattern Name:** [precise name for the dominant pattern] |
| 87 | |
| 88 | **What Naming It Reveals:** [what becomes visible or legible t |