conduct
Conduct the method of a session's epistemic work before object-level cognition begins. When a work prospect needs multiple cognitive moves whose order, independence, reconciliation, termination, and routing are non-trivial, design a conduct topology over the protocol graph and hand off a method plan with in-session checkpoints; single-move work relays to that one protocol instead of conducting. Type: (MethodUnderdetermined, AI, CONDUCT, WorkProspect × ProtocolGraph) → ConductedMethod. Alias: Hyphegesis(ὑφήγησις).
What this skill does
# Hyphegesis Protocol
Conduct how a session's epistemic work will be carried out — the order, independence, reconciliation, termination, and routing of its cognitive moves — when that method is underdetermined before object-level cognition begins. The morphism is **design THEN hand off**: Hyphegesis designs a conduct topology over the protocol graph and emits a method plan with in-session checkpoints, then stops; the substrate executes the moves. Type: `(MethodUnderdetermined, AI, CONDUCT, WorkProspect × ProtocolGraph) → ConductedMethod`.
## Definition
**Hyphegesis** (ὑφήγησις: a leading-the-way, guiding from just ahead): A dialogical act of conducting a session's epistemic work — deciding how its multiple cognitive moves relate in order, independence, reconciliation, termination, and routing — when the method is underdetermined while the goal is clear. The protocol's lexical verb is `/conduct`. It activates only when the work needs two or more moves whose conduct is non-trivial (single-move work relays to that one protocol), designs the conduct topology impact-first (locking stable axes, deferring volatile ones to in-session checkpoints), surfaces substrate feasibility as a handoff annotation, assembles a cross-cutting trace contract (its disclosure overlay over the five axes — residuals, degradations, coverage caps, never silent), and hands off a method plan that the substrate — not Hyphegesis — executes.
```
── FLOW ──
Hyphegesis(WP) → MethodBrief(WP) → guard[relay-test, anti-self-application] →
[single-move ∨ trivial-conduct: relay-route(extension) → deactivate] |
[multi-move ∧ non-trivial:
Qc(brief, warrant) → continue →
MoveId(WP × PG) → Sc(MoveSet) → MS →
CT_default_relay → loop( AxisGate(impact-first axis·region) → VM → update(CT) → auto-advance ) until Sufficient → CT →
SubstrateHandoff(CT) → SH → RecordDegradation(degradations) → AssembleTraceContract(residuals, degradations, coverage) → TC → converge(conduct trace incl. trace contract) → ConductedMethod ]
── MORPHISM ──
WorkProspect × ProtocolGraph
→ brief(method, conduction_warrant) -- infer the work prospect's method-brief; judge whether conduction is warranted
→ guard(relay_test, anti_self_application) -- single-move work relays to that one protocol; Hyphegesis does not conduct Hyphegesis
→ identify(moves) -- candidate cognitive moves over the protocol graph
→ select(moves) -- user confirms the move set via Cognitive Partnership Move (Constitution)
→ design(conduct_topology) -- impact/leverage-first: lock stable axes, defer volatile to in-session checkpoints; edge-local over move-regions
→ annotate(substrate_feasibility) -- per resolved topology, surface substrate realizability as a handoff annotation
→ contract(trace_disclosure) -- assemble the cross-cutting disclosure overlay: residuals + degradations + coverage caps; surfaced, never silent (not a sixth axis — assembled, not gated)
→ handoff(conducted_method) -- emit the method plan + in-session checkpoints, then stop (substrate executes)
→ ConductedMethod
requires: method_underdetermined(WP) -- runtime checkpoint (Phase 0)
deficit: MethodUnderdetermined -- activation precondition (Layer 1/2)
preserves: WP -- work prospect read-only
invariant: Conduction over Substrate
── TYPES ──
WP = WorkProspect: the work or goal facing object-level cognition, with its method (conduct plan) not yet determined
PG = ProtocolGraph: available protocols and move-neighbors (the dependency graph plus ad-hoc moves)
Move = CognitiveMove: a single cognitive step (protocol invocation | analysis pass | delegation) — the unit Hyphegesis arranges, always object-level (never another conduction)
MS = MoveSet: (WP × PG) → {Move₁ … Moveₙ}, n ≥ 2 -- n < 2 → guard relay, deactivation
MethodBrief = AI-inferred summary of WP: { work_intent, expected_handoff, span } -- span = invocation → next planned /compact or /clear (the design-time horizon; the user types the command)
Warrant = ConductionWarrant ∈ {warranted, relay} -- warranted = (moves ≥ 2 ∧ conduct non-trivial: ≥ 2 conduct-plans with differential futures); relay = single-move ∨ trivial (conduction entropy → 0)
MoveRegion = a contiguous sub-graph of moves sharing one conduct treatment (e.g. an authoring region vs a verification region); the single region "whole" when order is not a dependency DAG
axis ∈ {order, independence, reconciliation, termination, routing} -- FINITE seed; surfaced impact/leverage-first (most-constrained axis·region first), NOT a fixed sequence
Gen(order) ∈ {single_move (relay-only: trips the guard; never selected in Phase 2), sequential_chain, parallel_fan, dependency_dag}
Gen(independence) ∈ {isolated, shared} -- isolation before synthesis-contamination
Gen(reconciliation) ∈ {aggregate, dialectic, adversarial_refute, synthesis} -- the only composable axis (⨾/∥)
Gen(termination) ∈ {single_pass, bounded_rounds, until_dry_ceiling, until_goal_met}
Gen(routing) ∈ {return_to_user, chain_to_next, handoff_to_protocol, deepen_on_finding}
ResolvedValue⟨a⟩ = per-axis resolved value, axis-typed (composition is NOT axis-uniform):
ResolvedValue⟨reconciliation⟩ = Gen(reconciliation) ⊕ Compose(RVᵣ, RVᵣ, op) -- the sole composable axis (the reconciliation-stage algebra)
ResolvedValue⟨order⟩ = Gen(order); ResolvedValue⟨independence⟩ = Gen(independence); ResolvedValue⟨termination⟩ = Gen(termination); ResolvedValue⟨routing⟩ = Gen(routing) -- SCALAR axes: Gen only (⨾/∥ have no meaning on an order shape, an isolation flag, a termination bound, or a routing flag)
op ∈ {⨾ sequential, ∥ parallel} -- reconciliation-stage operators; extensible at operator level
CT = ConductTopology = Map(axis → Map(MoveRegion → ResolvedValue⟨axis⟩)) -- EDGE-LOCAL: when Gen(order) = dependency_dag, independence/reconciliation/routing/termination resolve per move-region (non-uniform); order defines the regions (global); uniform axes carry the single region "whole"
CT_default = ⟨order: sequential_chain, independence: isolated, reconciliation: synthesis, termination: bounded_rounds, routing: return_to_user⟩ over the single region "whole" -- the assembled tuple of per-axis Gen defaults; relay fast-path. NORMALIZATION: the flat tuple is shorthand for Map(axis → {whole → value}) — every flat axis value normalizes to the nested single-region form, so CT is uniformly Map(axis → Map(MoveRegion → ResolvedValue⟨axis⟩))
AxisGate = { axis, region, options, default, basis } -- one surfaced per elicitation cycle, impact/leverage-first; reconciliation gate additionally offers ⨾/∥ composites
Checkpoint = an in-session conductor re-entry point (plan | exec | verify, or a finer sub-topology point) where Constitution may re-fire -- in-session ONLY; /compact and /clear are the span wall, never checkpoints
CheckpointSet = ordered Set(Checkpoint) -- Hyphegesis conducts to the LAST checkpoint, then downstream-delegates (multi-consumer-like)
SH = SubstrateHandoff: CT → FeasibilityAnnotation -- substrate realizability surfaced as a handoff annotation (matter; composed in TOOL GROUNDING, not in phase prose)
VM = ConductMove ∈ {Select(value), Compose(via op), Reorient(axis), Sufficient} -- per-cycle user move in the axis gate; Compose offered on the reconciliation axis only
Sufficient = a MOVE in the axis gate (NOT a separate gate) → converge elicitation (user Constitution declaration)
ResidualAxis = { axis, region, status: ResidualDisposition, reason } -- unresolved axis·region carries Gen default + a surfaced disposition; silent default-binding forbidden
ResidualDisposition ∈ {Declared, Deferred, Dismissed}
Degradation = { region: MoveRegion, kind ∈ {independence_relaxed, substrate_infeRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.