innozverse-repo-structure

Name: innozverse-repo-structure
Availability: InStock
Author: lastcow

Map the innozverse monorepo structure across apps, packages, and docs.

Updated Dec 21, 2025

Search Tags:#structure #monorepo #packages #conventions #repo #apps

Ready to run

npx skills add https://github.com/lastcow/innozverse --skill innozverse-repo-structure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: innozverse-repo-structure
Source: https://github.com/lastcow/innozverse/tree/main/.claude/skills/repo-structure
Command: npx skills add https://github.com/lastcow/innozverse --skill innozverse-repo-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides on top-level structure, app and package directories, and naming conventions to reduce confusion in a large monorepo.

Core Features & Use Cases

Top-level layout: Overview of apps/, packages/, docs/, and .claude/ directories.
App vs Package boundaries: Clear rules for dependencies and who can import whom.
Naming conventions: File naming and structure guidelines for consistency.

Quick Start

Use this Skill when creating new files or reorganizing code across the monorepo.

Frequently Asked Questions about innozverse-repo-structure

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

FAQPage Schema

How do I organize files in a monorepo with apps, packages, and docs?▼

A monorepo uses top-level directories to separate concerns: apps/ holds applications, packages/ contains reusable libraries, docs/ stores documentation, and .claude/ holds Claude-specific configuration. This structure clarifies boundaries and prevents circular dependencies across your codebase.

What are the naming conventions for files and directories in a monorepo?▼

Naming conventions ensure consistency across a monorepo by standardizing file structure, directory organization, and module paths. Following established patterns reduces confusion when navigating code and helps teams locate files predictably.

How do I know what dependencies are allowed between apps and packages?▼

Clear dependency rules prevent circular imports and enforce clean architecture. Apps can depend on packages, but packages should not depend on apps; understanding these boundaries keeps your monorepo maintainable as it grows.

When should I create a new app versus a new package in my monorepo?▼

Use packages for reusable code shared across multiple applications; create apps for deployable services or standalone products. This distinction clarifies module boundaries and determines what other code can safely depend on your work.

How do environment variables and versioned routing work across monorepo modules?▼

Environment variable handling and versioned routing guidance establish how apps and packages reference configuration and API paths. These conventions prevent conflicts and ensure consistent behavior across your entire monorepo.