tesseron-explorer

Map Tesseron TypeScript codebases into architecture summaries with file references.

20|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Eigenwise/tesseron --skill tesseron-explorer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tesseron-explorer
Source: https://github.com/Eigenwise/tesseron/tree/main/plugin/skills/tesseron-explorer
Command: npx skills add https://github.com/Eigenwise/tesseron --skill tesseron-explorer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps existing Tesseron TypeScript codebases — catalogs apps, actions, resources, context-method usage, transports, React hooks, and session-lifecycle wiring; traces how agent invocations flow through handlers into app state; returns a compact architecture summary with file:line references. Use PROACTIVELY when the user asks to "explore", "map", "understand", "analyze", "trace", or explain how this works in a project that imports from @tesseron/core, @tesseron/web, @tesseron/server, @tesseron/react, or @tesseron/mcp, or before extending a non-trivial Tesseron codebase. The caller should pass the scope (project root, package, or specific feature) in the invocation prompt.

Core Features & Use Cases

Map an existing Tesseron TypeScript application — its app manifests, actions, resources, context-method usage, transports, React hooks, and session lifecycle — and return a compact summary the caller can act on without re-reading the files themselves.

  • Identify apps via tesseron.app registrations and session lifecycle via tesseron.connect and transports.
  • Catalog actions, resources, and context-method usage to trace data-flow from gateway to state mutations.

Quick Start

Run the explorer with a scope (project, package, or feature) to generate a concise architecture map of a Tesseron codebase.

Frequently Asked Questions about tesseron-explorer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map the architecture of a Tesseron TypeScript codebase?

Mapping a Tesseron TypeScript codebase involves scanning for tesseron.app registrations, context-method usage, and transports to produce a concise architecture summary with file:line references.

How does data flow through Tesseron apps and session lifecycle?

Data flows through Tesseron apps by tracing agent invocations from gateways through handlers into app state, utilizing tesseron.connect and transports to manage the session lifecycle.

Can I analyze a specific feature instead of the whole project in Tesseron?

Yes, you can analyze a specific feature. The exploration scope can target a project root, a package, or a specific feature, allowing you to map only the relevant actions, resources, and context-method usage.

What's the best way to trace React hooks and context methods in a Tesseron project?

The best way to trace React hooks and context methods is to use an explorer that scans imports from @tesseron/react and @tesseron/core, cataloging their usage to map data-flow into state mutations.

When do I need to explore Tesseron codebase architecture before extending it?

You need to explore Tesseron codebase architecture proactively before extending a non-trivial codebase, ensuring you understand the existing app manifests, actions, and transports to avoid breaking session lifecycle wiring.

Does the architecture explorer require a SKILL.md file to identify the codebase?

Yes, the architecture explorer identifies the Tesseron skill unit by detecting the presence of a SKILL.md file containing the name and description at the root of the target directory.