adaptic
정보
애드패틱은 명상, 관찰, 통합을 포함한 5단계 개요 주기를 조율하여 세 가지 이상의 영역에 걸친 통합적이고 파노라마적인 종합을 만들어내는 마스터 스킬입니다. 개별 심도보다 영역 간 상호작용이 더 중요할 때, 순차적 분석이 부족하게 느껴질 때, 또는 여러 이해관계자에게 영향을 미치는 주요 아키텍처 결정을 내리기 전에 사용하세요. 이는 순차적 타협이 아닌 일관되고 전체론적인 이해를 생성합니다.
빠른 설치
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/adapticClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Adaptic
5-step synoptic cycle → panoramic synthesis across domains. Sequential = compromise ("little of each"). Synoptic = integration → unified understanding holds all domains at once → emergent whole.
Use When
- Problem spans 3+ domains, interactions > depth in any one
- Polymath sequential tried → synthesis feels like compromise
- Existing approaches = "little of each" not unified vision
- Before major architectural decisions, multi-stakeholder
- Domain experts disagree → resolution lives between
Use NOT When
- Single-domain → use domain agent direct
- Well-understood trade-offs → polymath sequential enough
- Self-care/wellness → tending team
- Speed > depth → full cycle needs sustained attention
In
- Required: Problem requiring multi-domain synthesis
- Optional: Explicit domain list (default: auto-detect)
- Optional: Depth —
light,standard,deep(default:standard) - Optional: Expression form —
narrative,diagram,table,recommendation(default:auto)
Config
settings:
depth: standard # light (skip meditate), standard, deep (extended perceive)
domains: auto # auto-detect or explicit list
expression_form: auto # narrative, diagram, table, recommendation
Do
Step 1: Clear — Empty Workspace
Run meditate → clear prior ctx, assumptions, single-domain bias.
- Full meditate proc: prepare, anchor, observe distractions, close
- Domain bias = tendency to frame via recently-active domain
- Clear premature solutions arrived pre-full-picture
depth: light→ brief ctx-clearing pause
→ Workspace empty. No domain priority. No solution pre-selected. Neutral receptive → hold multiple perspectives.
If err: Domain keeps asserting → name bias: "I frame this as primarily [domain]." Naming loosens. Clearing fails → genuinely single-domain → reconsider.
Step 2: Open — Panoramic Mode
Run expand-awareness → narrow → wide-field perception.
- Inventory all domains → no pre-filter/rank
- Per domain: core concerns, constraints, values — no eval
- Soften focus: hold all simultaneously vs cycling
- Resist "start solving" → opening field only
- Domains in inputs → starting set, open to more
→ Panoramic field open. All domains simultaneous. Full landscape sensed. Spacious not overwhelming.
If err: List incomplete → "What missing would change picture?" Simultaneous → sequential scan → slow down. >7 domains → cluster related.
Step 3: Perceive — Cross-Domain Patterns
While maintaining panoramic, run observe + awareness → notice patterns, tensions, resonances across domains.
- Hold Step 2 field open → no narrow
observe→ what present: patterns across domains? tensions? resonances?awareness→ what not seen: ignored domains? blind spots? surface assumptions?- Record cross-domain no interpret:
- Tensions: domains pull opposite
- Resonances: domains reinforce/echo
- Gaps: no domain addresses, whole reveals
- Surprises: domain unexpected contribution
depth: deep→ cycle multiple times → subtler patterns
Critical: perceive across all simultaneously, not each in turn. Sequential loses cross-domain patterns = entire point.
→ Rich cross-domain obs — tensions, resonances, gaps, surprises. Span boundaries not live within. Noticed something invisible from any single domain.
If err: All within single ("in domain A, I notice X") → field collapsed → Step 2. No cross-domain → problem not synoptic → genuinely decomposable. Overwhelming → prioritize tensions (integration happens there).
Step 4: Integrate — Emergent Whole
Run integrate-gestalt → synthesize cross-domain obs → unified understanding.
- Map Step 3 tensions → don't resolve prematurely → hold as creative constraints
- Find figure: unified understanding when all held together? Not compromise/avg → new pattern includes+transcends individual
- Test whole: honors each domain's core concerns? Resolves tensions or papers over?
- Name insight one clear statement → unstatable simply = incomplete
- Verify emergent: reachable sequentially? Yes → synoptic added no value → sequential suffices
→ Single integrated understanding holding all simultaneously. Feels like discovery not construction — emerged from whole. Each domain honored, tensions resolved not compromised.
If err: "Little of each" not unified → gestalt not formed → Step 3, find avoided tensions — integration happens through tension. No gestalt → decompose: 2-3 strongest-tension domains first, then expand.
Step 5: Express — Communicate
Run express-insight → communicate synthesis.
- Assess audience: what domains familiar? framing makes accessible?
- Expression form (or input):
- Narrative: audience needs parts→whole journey
- Diagram: structural relationships
- Table: systematic comparison
- Recommendation: actionable decision
- Express w/ transparency: which domains contributed, where tensions resolved, emergent insight beyond any single
- Invite challenge: which aspects strongest, which most speculative
→ Clear expression accessible to audience. Shows work → audience sees domain contributions → whole. Form matches audience needs.
If err: Feels like list not integrated → insight lost → Step 4 one-statement summary, build outward from center. Wrong framing → "Who needs this and what decision does it inform?"
Check
- Step 1 (Clear) ran → ctx + domain bias released
- Step 2 (Open) produced panoramic 3+ domains
- Step 3 (Perceive) cross-domain patterns (not within-domain)
- Step 4 (Integrate) single emergent transcends individual
- Step 5 (Express) form appropriate to audience
- Output unreachable by sequential single-domain
- Each domain's core concerns honored
- Tensions resolved through integration, not compromise
Traps
- Sequential masquerading as simultaneous: Cycling domains + stapling results ≠ synoptic. Test: cross-domain interactions produced new, or just concatenation?
- Premature integration: Jump synthesis pre-panoramic field open. Steps 2+3 build foundation → rushing = shallow.
- Compromise instead of emergence: Avg ("50% security, 50% usability") = compromise. True integration finds frame where both fully met, or honestly names irreducible trade-off.
- Overuse single-domain: Not every problem panoramic. Single domain → synoptic adds overhead no value. "Use NOT When" exists.
- Losing insight in expression: Step 4 gestalt → Step 5 fragments back to domain list. Keep integrated insight center; domain details supporting evidence.
- Domain inflation: Artificially expand count → justify synoptic. 3 genuinely relevant > 7 where 4 peripheral.
→
meditate— Step 1; clears ctx + neutral stateexpand-awareness— Step 2; narrow → panoramicobserve— Step 3; what present across fieldawareness— Step 3; what not seen, blind spotsintegrate-gestalt— Step 4; emergent whole from cross-domainexpress-insight— Step 5; communicate integrated understanding
GitHub 저장소
연관 스킬
content-collections
메타이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
polymarket
메타이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
creating-opencode-plugins
메타이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
sglang
메타SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
