analyze frontend structure

This skill is used to scan any frontend project directory, automatically analyze routing structure and module division, and generate a universal module-page...

Security Scan

The skill's requirements and instructions are consistent with its stated purpose (scanning a frontend project directory and generating a module-page mapping), but the SKILL.md is high-level and leaves implementation details unspecified.

Purpose & Capability

Name/description match what the skill asks for: scanning a user-provided project directory, parsing routing/config files, and producing mapping outputs. There are no unrelated required binaries, env vars, or config paths.

Instruction Scope

SKILL.md instructs the agent to traverse and analyze a supplied directory and parse framework routing files. This is within scope, but the instructions are high-level (no concrete safe parsing rules or limits). The agent is given broad discretion about how to scan and infer modules, which could lead to unintended file reads if not constrained to the provided path.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes installation risk because nothing is written to disk by an installer.

Credentials

No environment variables, credentials, or external config paths are requested. The declared inputs (directory path, optional framework/output type) are proportional to the stated functionality.

Persistence & Privilege

Skill is not always-enabled and does not request persistent privileges or modify other skills' configurations. Autonomous invocation is allowed by platform default but not requested beyond normal behavior.

Assessment

This skill appears coherent with its description: it expects a project directory and will analyze files there. Before running it, provide only a project directory (not your entire home or system paths), or run it against a read-only copy of the repository. Ask the skill author or registry for an implementation (scripts or code) or sample output so you can verify exactly which files will be read and whether any network access is performed. If you have sensitive files in the repository, remove or move them before analysis. If you require higher assurance, request an explicit guarantee that the agent will not access paths outside the supplied directory or transmit analyzed data externally.

Features

1. Universal Routing Analysis: Automatically identifies and parses routing configuration files of different frontend frameworks, extracting routing paths, component associations, and other information.
2. Intelligent Module Recognition: Analyzes directory structure and component dependencies to identify project module divisions, regardless of framework.
3. Standardized Mapping Generation: Generates clear mapping relationships between modules and pages, including parent-child relationships, hierarchical structures, etc.
4. Intelligent Navigation Support: The generated mapping document can be directly used in intelligent navigation systems, supporting quick positioning and navigation.

Technical Implementation

Core Functions

1. Directory Scanning: Traverses the specified directory, identifies key files and directory structures, and adapts to different project organization methods.
2. Route Parsing: Parses common routing configurations such as Vue Router, React Router, Angular Router, etc.
3. Module Recognition: Intelligently identifies modules based on directory structure, naming conventions, and component reference relationships.
4. Mapping Generation: Generates standardized module-page mapping documents, supporting multiple output formats.

Supported Frameworks

• Vue 2/3
• React
• Angular
• Svelte
• Solid

Usage

When user needs to analyze a frontend project structure, invoke this skill directly:

1. User provides the frontend project directory path
2. Skill automatically scans and analyzes
3. Generates module-page mapping document

Input Requirements

• User needs to provide the directory path of the frontend project to be analyzed
• Optional: specify framework type (vue, react, angular, svelte, solid), default is auto-detection
• Optional: specify output format (json, markdown, html)
• Optional: specify output file path

Output

Generates a mapping document containing:

• Project Info: project name, framework type, analysis date
• Module List: module name, route path, component file, nested sub-modules
• Component List: component name, file path, which modules use it