Summarise the Lampa repository structure: top-level folders, likely entrypoints, build/doc scripts, and plugin list.

List all JavaScript/TypeScript modules in a given subfolder of the Lampa repo.

Find files in the repo by name pattern or extension.

Search the repo source code for a text string or regex pattern. Returns file paths, line numbers, and short previews.

Read a specific line range from a file in the repo.

List all NPM scripts defined in package.json.

Locate Lampa settings registrations, storage reads/writes, and default configs. Optionally filter by keyword.

Locate external API calls, fetch wrappers, and provider integrations in the Lampa source.

Find Lampa UI component files (templates, components, views) by name.

Find translation key definitions and usages across all supported languages.

Find CSS/SCSS style files related to a module or feature name.

Map imports/requires for a file. Returns direct imports, inferred reverse dependencies, and change blast radius.

Infer all files relevant to a named Lampa feature: player, catalog, search, settings, cards, parser, bookmarks, iptv, etc.

Generate a step-by-step implementation plan for a requested Lampa feature or change. Must be called before draft_patch.

Analyse the potential impact of modifying a specific file or module.

Given a feature request, suggest the minimal set of files to edit and the best insertion points.

Scan a file or folder for coupling risks: shared state, global events, settings persistence, reused components.

Draft a code patch for a Lampa change. Requires a prior plan_feature_change call. Returns annotated diff-style suggestions.

Find the best Lampa.Listener or Lampa.Event hook point for a given trigger or lifecycle event.

Generate the boilerplate to add a new setting to Lampa's settings panel.

Generate a complete Lampa plugin scaffold (folder structure + main.js boilerplate) for a new plugin.

Run a set of code-quality grep checks across the repo: undefined references, console.log leftovers, TODO markers, missing translations.

Find test/spec files related to a module or feature.

Return the correct build/dev/test command for the Lampa project based on package.json scripts.

Look up a topic in the generated docs (build/doc/index.html) or README.

Comprehensive single-call analysis of a Lampa plugin folder: all files, Lampa API usage, event hooks (follow/send), settings registrations, CSS, and entry-point preview. Replaces 6–10 individual tool calls.

List all online streaming content providers bundled with Lampa (plugins/online/.js and plugins/online_prestige/balansers/.js). Shows base URL, public methods, and Lampa APIs each provider uses.

Compare all Lampa language files against the English reference. Shows coverage percentage and lists missing/extra keys per language. Helps identify untranslated strings before shipping.

Trace a Lampa event through the entire codebase. Shows every file that emits it (Lampa.Listener.send) and every file that listens to it (Lampa.Listener.follow). Essential for understanding the event bus.

Extract the complete Lampa.* global API surface from the source code. Lists every module (Lampa.Storage, Lampa.Player, etc.) with its sub-methods and file usage count. The definitive reference for plugin development.

List all Lampa UI templates in src/templates/. Optionally read a specific template's source to understand its HTML structure and data bindings.

Generate a ready-to-use Lampa plugin boilerplate based on real patterns from existing plugins. Select the features you need and get working code instantly.

Deep-analyse a Lampa component's lifecycle: lifecycle methods (create/render/destroy), event hooks, Lampa APIs used, storage reads/writes, template usages, and settings interactions — all in one call.

Read the complete contents of any file in the Lampa repo. Files larger than max_lines are truncated — use read_file_segment to read specific sections of large files.

Extract all Lampa.Storage keys used across the codebase. Builds a complete map of the user-persistence model: key names, default values, which files read and write each key.

Build a complete map of the Lampa.Listener event bus. Lists every event name, how many files listen to it, and how many files emit it — across the entire codebase.

Extract all hardcoded URLs, API base URLs, and proxy patterns from the Lampa source. Reveals every external service the app communicates with.

Validate a Lampa plugin against established conventions: IIFE wrapping, strict mode, appready bootstrap, no localhost URLs, proper event cleanup, and more. Returns a scored report with fix guidance.

Extract the actual HTML markup from Lampa template files (src/templates/*.js). Shows template structure, CSS classes, data-binding placeholders, and data attributes. Useful for understanding UI structure without running the app.

Read a Lampa core module from src/core/. Core modules implement the fundamental Lampa APIs (storage, lang, player, api, component, etc.). Lists all available modules when no name is given.

Get a detailed explanation and real extracted code examples for any core Lampa development pattern. Combines a written guide with live source examples — the fastest way to understand how Lampa works.