web

Discover, validate, and map frontend pages, routes, and documentation.

5|1|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/MyElectricalData/myelectricaldata_new --skill web-myelectricaldata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web
Source: https://github.com/MyElectricalData/myelectricaldata_new/tree/main/.claude/skills/web
Command: npx skills add https://github.com/MyElectricalData/myelectricaldata_new --skill web-myelectricaldata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically manage frontend web pages by automatically discovering, mapping, and validating page files, routes, and documentation across the repository.

Core Features & Use Cases

  • Auto-detects pages, API frontends, and router mappings to ensure consistency between code, routes, and docs.
  • Validates frontmatter, navigation menus, and execution modes (server/client/both) for each page.
  • Provides a structured quick-start workflow to target a page for checks, updates, or design validation.

Quick Start

Use the web skill to inspect a target page (e.g., dashboard), verify its frontmatter, ensure corresponding routes exist, and confirm navigation and design conformance.

Frequently Asked Questions about web

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

FAQPage Schema
How do I validate frontend page routes and frontmatter across a large codebase?

To validate frontend page routes and frontmatter, this skill auto-discovers page files and router mappings, enforcing frontmatter integrity and route consistency across the repository to ensure code and documentation alignment.

What is the best way to automate discovery and documentation alignment for multi-tab pages?

Automating discovery and documentation alignment for multi-tab pages involves targeting specific page files to verify navigation menus, nested documentation, and execution modes to ensure standardized design conformance.

Can I check navigation menu structure and execution modes for server and client rendering?

Yes, you can check navigation menu structure and execution modes by validating each page's frontmatter to confirm whether it operates in server, client, or both execution modes within the project.

How do I start inspecting a target frontend page like a dashboard?

To start inspecting a target frontend page, follow the structured quick-start workflow to target the page, verify its frontmatter, ensure corresponding routes exist, and confirm navigation conformance.

Does this work for single-page targets or is it only for multi-page applications?

It works for both single-page targets and multi-tab pages, handling the discovery, validation, and documentation alignment of any frontend web page across the entire project repository.