integrate-gestalt
정보
이 스킬은 `expand-awareness`에서 얻은 여러 분야의 원시 관점들을 종합하여 하나의 창발적 통찰로 만듭니다. 각 분야 간의 긴장과 공명을 매핑하여 부분들의 합보다 큰 일관된 전체를 형성합니다. 통일된 결론을 표현하기 위해 `expand-awareness` 이후, `express-insight` 이전에 사용하세요.
빠른 설치
Claude Code
추천npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/integrate-gestaltClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Integrate Gestalt
Form whole from panoramic perception of expand-awareness. Not by averaging, not by compromise, not by picking best domain. By spotting emergent pattern no single view could make.
When Use
expand-awarenesshas surfaced raw perception from many domains; observations need to become one insight- Many domain views present, no single one covers all evidence
- Problem analyzed from several angles; separate analyses need to become more than list
- Question "what does all this mean together?" has no obvious answer
- Synthesis keeps collapsing to "pick best domain" instead of making something new
- Before
express-insight, which needs formed gestalt as input
Inputs
- Required: Multi-domain observations from
expand-awareness(or equivalent panoramic perception) - Optional: Original question or problem that triggered multi-domain scan
- Optional: Known constraints gestalt must satisfy
- Optional: Prior failed integration tries (what collapsed into single-domain answers)
Steps
Step 1: Map Tensions
For each pair of domains from panoramic perception, characterize how they relate. Three relationships: tension (disagree), resonance (reinforce from different angles), orthogonality (address unrelated aspects).
Use tension-resonance map:
Tension-Resonance Map
+-------------------+-------------------+-------------------------------+
| Domain Pair | Relationship | Detail |
+-------------------+-------------------+-------------------------------+
| A vs B | tension / | |
| | resonance / | |
| | orthogonal | |
| Evidence: | | What specifically disagrees, |
| | | reinforces, or is unrelated? |
| Implication: | | What does this relationship |
| | | suggest for the whole? |
+-------------------+-------------------+-------------------------------+
| A vs C | ... | ... |
+-------------------+-------------------+-------------------------------+
| B vs C | ... | ... |
+-------------------+-------------------+-------------------------------+
Fill one row per domain pair. For N domains: N(N-1)/2 pairs. Over ten rows? Group related domains first, map between groups.
Prioritize tensions — carry most integrative info. Resonances confirm. Orthogonalities can sit aside. Tensions demand resolution. Gestalt lives in how they resolve.
Got: Completed map. Every domain pair has characterized relationship with specific evidence. At least one real tension found. No tensions? Domains maybe not different enough for emergence.
If fail: All pairs show resonance? Domains agree at surface only. Dig deeper: where do they agree for different reasons? Agreement-for-different-reasons is hidden tension. Nothing characterizable? Panoramic perception from expand-awareness too shallow — go back, deepen domain observations before integrating.
Step 2: Find Figure
Gestalt psych: figure emerges from ground. Ground = tension-resonance map from Step 1. Figure = dominant pattern unifying most domains with fewest contradictions.
- Scan map for clusters: which groups of domains resonate? Clusters suggest candidate figures
- For each candidate, ask: "What single perspective makes sense of most observations?"
- Figure not compromise (weaken each domain until agree). Not selection (pick strongest). New frame recontextualizing domain observations
- Test: state candidate in one sentence. Feels like it belongs to one input domain? Then not yet gestalt — domain answer in disguise
- Look at tensions: true figure often lives in space between disagreeing domains, not in either domain's position
Signs figure emerging:
- Multiple tensions resolve at once under same reframe
- Contradictory observations become complementary aspects of same phenomenon
- Figure explains why each domain saw what it saw, including why they disagreed
Got: One or two candidate figures as single sentences. Each recontextualizes domain observations rather than selecting among them. Candidate accounts for major tensions in map.
If fail: No figure emerges? Integration premature. Two paths: (a) return to expand-awareness, add missing domain — figure maybe cannot form because key perspective absent; (b) sit with tensions, do not force resolution — some gestalts need incubation. Note state, return later.
Step 3: Test Whole
Candidate gestalt from Step 2 must survive three tests before accepted.
Test A — Tension accounting: Walk every tension from Step 1. Does gestalt resolve it, reframe it, or explicitly accept as irreducible trade-off? Unaddressed tensions = premature gestalt.
Test B — Single-domain origin: Could this insight come from within single domain? If domain specialist nods and says "yes, already knew that," gestalt collapsed to domain answer. True gestalt surprises every domain — each recognizes own contribution but not whole.
Test C — Coherence under rotation: Mentally approach gestalt from each domain in turn. Hold shape? Or look different depending on view? Robust gestalt = same insight from any angle. Fragile one changes meaning under rotation.
Scoring:
- All three pass: go Step 4
- Test A fails: gestalt incomplete — back to Step 2 with unresolved tensions as extra constraints
- Test B fails: gestalt not emergent — back to Step 2, explicitly exclude single-domain framings
- Test C fails: gestalt not coherent — maybe two separate insights pretending to be one. Split, test each half independent
Got: Candidate passes all three tests, or failure mode identified and guides return to Step 2.
If fail: Candidate fails repeatedly after many iterations? Maybe domains do not form natural gestalt for this problem. Not every multi-domain observation makes emergence — sometimes honest answer is structured list of domain perspectives with tensions mapped. Deliver tension-resonance map as output instead of forcing false unity.
Step 4: Name Insight
Articulate gestalt in single sentence that domain specialist would not write from within own domain alone. This sentence is deliverable.
- Write sentence. Should be:
- Specific enough to be actionable or falsifiable
- General enough to encompass all contributing domains
- Surprising to at least two input domains
- Free of jargon from any single domain (or jargon deliberately recontextualized)
- Test sentence against three criteria from Step 3 one final time
- Optional: add one-paragraph expansion tracing how gestalt emerged from domain contributions — this is provenance, not insight itself
- Record which domains contributed, which tensions were key, what figure-ground relationship was — metadata supports future integration tries
Named insight + provenance = input to express-insight for communication.
Got: Single sentence capturing gestalt + brief provenance paragraph. Sentence passes "no single domain" test. Reading it, practitioner of any contributing domain recognizes field's contribution but could not have arrived at statement alone.
If fail: Sentence keeps collapsing to domain language? Try negation test: state what gestalt is NOT. "This not security recommendation, not performance optimization, not architectural pattern — it is [the gestalt]." Negations clear domain frames, open space for emergent formulation.
Checks
- Tension-resonance map completed for all domain pairs with specific evidence
- At least one real tension (not just difference of emphasis) identified
- Candidate gestalt articulated as reframe, not compromise or selection
- Test A passed: all major tensions resolved, reframed, or acknowledged
- Test B passed: no single domain could produce this insight alone
- Test C passed: gestalt holds shape under each domain's view
- Final insight in single sentence with provenance
Pitfalls
- Averaging: Weakening each domain's position until surface agreement. Makes mush, not gestalt. Integration feels bland = averaging
- King-making: Pick strongest domain's answer, dress in multi-domain language. Test B catches — one specialist nods unsurprised = king-making
- Premature closure: Accepting first candidate without testing against tensions. First figure often most obvious, not most integrative
- Forced unity: Insisting gestalt must exist when domains truly orthogonal. Orthogonal domains make structured lists, not gestalts — valid outcome
- Jargon blending: Mixing technical terms from multiple domains into sentence that sounds integrative but means nothing. Every term in final sentence should be meaningful independent
See Also
expand-awareness— makes raw panoramic perception this skill integrates; always before integrate-gestaltexpress-insight— communicates formed gestalt to audience; always after integrate-gestaltbuild-coherence— selects among competing options via structured evaluation; integrate-gestalt makes new whole instead of choosingbrahma-bhaga— creates from void; integrate-gestalt creates from abundance (many filled views)meditate— clears prior context for clean perception; useful before expand-awareness, which precedes this skillcoordinate-reasoning— manages info flow in multi-path evaluation; complements when gestalt coordinates many reasoning threads
GitHub 저장소
연관 스킬
evaluating-llms-harness
테스팅이 Claude Skill은 MMLU, GSM8K를 포함한 60개 이상의 표준화된 학술 과제에서 LLM 성능을 벤치마크하기 위해 lm-evaluation-harness를 실행합니다. 개발자들이 모델 품질을 비교하고, 학습 진행 상황을 추적하거나 학술 결과를 보고할 수 있도록 설계되었습니다. 이 도구는 HuggingFace와 vLLM 모델을 포함한 다양한 백엔드를 지원합니다.
cloudflare-cron-triggers
테스팅이 스킬은 cron 표현식을 사용하여 Worker를 스케줄링하기 위한 Cloudflare Cron Triggers 구현에 관한 포괄적인 지식을 제공합니다. 주기적 작업, 유지보수 작업, 자동화된 워크플로우 설정 방법을 다루며, 잘못된 cron 표현식이나 시간대 문제 같은 일반적인 이슈들을 해결하는 방법을 포함합니다. 개발자들은 이를 통해 스케줄된 핸들러 구성, cron 트리거 테스트, Workflows 및 Green Compute와의 연동 작업을 수행할 수 있습니다.
webapp-testing
테스팅이 Claude Skill은 Python 스크립트를 통해 로컬 웹 애플리케이션을 테스트하기 위한 Playwright 기반 툴킷을 제공합니다. 프론트엔드 검증, UI 디버깅, 스크린샷 캡처, 로그 확인 기능을 지원하며 서버 라이프사이클을 관리합니다. 브라우저 자동화 작업에 사용하되 컨텍스트 오염을 방지하기 위해 소스 코드를 읽지 않고 스크립트를 직접 실행하세요.
finishing-a-development-branch
테스팅이 스킬은 테스트 통과를 확인한 후 체계적인 통합 옵션을 제시하여 개발자가 완성된 작업을 마무리하도록 돕습니다. 구현이 완료된 후 머지, PR 생성, 브랜치 정리와 같은 워크플로우를 안내합니다. 코드가 준비되고 테스트가 완료되었을 때 개발 프로세스를 체계적으로 마무리하기 위해 사용하세요.
