view-map-audit

Cross-reference viewCatalog.js with Vue pages to detect missing, obsolete, or duplicate entries.

Updated Jun 1, 2024
One-click install
npx skills add https://github.com/gustavop-dev/projectapp --skill view-map-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: view-map-audit
Source: https://github.com/gustavop-dev/projectapp/tree/main/.agents/skills/view-map-audit
Command: npx skills add https://github.com/gustavop-dev/projectapp --skill view-map-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and project managers verify that the project's view catalog accurately reflects the actual Vue pages in the codebase, preventing outdated or missing entries.

Core Features & Use Cases

  • Consistency Verification: Checks that each real Vue page has a corresponding catalog entry.
  • Integrity Reporting: Reports missing, obsolete, or duplicated entries based on the current folder structure.
  • Use Case: When updating or refactoring the frontend, ensure all pages are correctly documented in the catalog and no orphan pages are left undocumented.

Quick Start

Run the audit command to compare viewCatalog.js with the Vue pages under frontend/pages/, focused on the panel section.

Frequently Asked Questions about view-map-audit

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

FAQPage Schema
How do I verify my Vue frontend view catalog matches actual pages?

To verify your Vue view catalog, cross-reference the `viewCatalog.js` file with your frontend directory structure to detect missing entries, obsolete references, and duplicates, ensuring source code and configuration consistency.

What is a view catalog audit in frontend development?

A view catalog audit validates that all real Vue pages are properly documented in the configuration data. It cross-references the folder structure against the catalog to report missing, obsolete, or duplicated entries for project maintenance.

How do I find missing or obsolete Vue pages in my codebase?

Find missing or obsolete Vue pages by cross-referencing your `viewCatalog.js` with the frontend pages directory. The audit respects test and exclude rules to accurately report discrepancies like undocumented orphan pages and duplicates.

When do I need to check frontend view catalog consistency?

You need to check frontend view catalog consistency when updating or refactoring your Vue application. This ensures all pages are correctly documented in the catalog and prevents leaving undocumented orphan pages in the codebase.

Does the view catalog audit support excluding specific Vue directories?

Yes, the view catalog audit supports excluding specific directories. It cross-references the `viewCatalog.js` with the Vue pages directory while respecting predefined test and exclude rules to avoid false positives during consistency verification.