adaptic
About
Adpatic is a master skill that orchestrates a 5-step synoptic cycle—including meditation, observation, and integration—to produce a unified, panoramic synthesis across three or more domains. Use it when domain interactions are more critical than individual depth, sequential analysis feels inadequate, or before making major architectural decisions affecting multiple stakeholders. It generates coherent, holistic understanding rather than a sequential compromise.
Quick Install
Claude Code
Recommendednpx 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/adapticCopy and paste this command in Claude Code to install this skill
Documentation
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 Repository
Related Skills
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
polymarket
MetaThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
creating-opencode-plugins
MetaThis skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
sglang
MetaSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
