analyze-project-structure

Analyzes project structure, detects patterns, and generates implementation recommendations for new features.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill analyze-project-structure-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-project-structure
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/analysis/analyze-project-structure
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill analyze-project-structure-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before adding a new feature or service, developers need to understand an existing codebase's structure, conventions, and patterns. This Skill performs a read-only analysis of a project and produces actionable documentation so new code follows established patterns instead of guessing. ## Core Features & Use Cases - Service and Module Inventory: Scans source directories to catalog every module with its language, tests, README, entry point, and dependencies. - Pattern Detection: Identifies language distribution (TypeScript vs JavaScript), test frameworks (Jest, Vitest, Mocha, Bun), documentation style, and configuration approaches. - Recommendation Generation: Produces a project-analysis.md and recommended-approach.md with service type suggestion, file structure, implementation steps, and agent assignment. - Use Case: Before adding a new payment integration to an existing TypeScript monorepo, run this analysis to discover how existing API services are organized, which test framework is used, and receive a recommended file structure and implementation plan. ## Quick Start Analyze this project structure and recommend how to implement a new notification service feature.

Frequently Asked Questions about analyze-project-structure

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

FAQPage Schema
How do I analyze a project structure before adding a new feature?▼

Run the analysis with a feature description and optional project path. It scans source directories, inventories all modules with their languages and tests, detects patterns, and generates a project-analysis.md plus a recommended-approach.md with implementation steps.

What does the project structure analysis detect?▼

It detects language distribution across .ts, .js, .jsx, and .tsx files, the test framework in use (Jest, Vitest, Mocha, or Bun test), documentation style, configuration file formats, environment variable usage, and each module's entry point and dependencies.

Does the project analysis modify any files in my codebase?▼

No, the analysis is strictly read-only. It only scans and reads project files, then writes two new output documents: project-analysis.md and recommended-approach.md. No existing source files are changed.

What happens if my project has no clear structure or no modules?▼

The analysis falls back to file-extension-based detection for non-standard structures. If no modules are found, it proceeds with minimal analysis and notes that no existing modules exist, still producing recommendations for the new feature.

How does the skill recommend a service type for my feature?▼

It matches your feature requirements against detected patterns: external API needs map to API Integration, database needs to Data Service, agent tooling to Plugin/Extension, and general features default to Utility Module, each with a suggested agent assignment.