What is the main benefit of the Innozverse Repo Structure skill?

It ensures that all contributions follow the project's specific architectural patterns, reducing technical debt and speeding up the onboarding process for new contributors.

How does it handle shared code and utilities?

The skill provides clear instructions for utilizing the packages/shared directory and managing internal workspace dependencies using pnpm.

Does this skill cover both backend and frontend conventions?

Yes, it includes detailed organizational structures for the Next.js web app, Fastify API, and Flutter mobile application within the monorepo.

Can this skill help with file naming?

Absolutely. It defines specific naming conventions for different languages, such as kebab-case for TypeScript files and snake_case for Dart files.

How does it prevent architectural rot?

By enforcing strict module boundaries, such as preventing apps from importing directly from other apps, it ensures a clean and maintainable dependency graph.

Innozverse Monorepo Structure & Conventions

Name: Innozverse Monorepo Structure & Conventions
Author: lastcow

bylastcow

API Development

Navigates and maintains the Innozverse monorepo architecture by enforcing standardized file organization and naming conventions.

About

This skill provides comprehensive guidance for developers working within the Innozverse production-grade monorepo. It covers the architectural layout for Next.js web applications, Fastify APIs, and Flutter mobile apps, alongside shared TypeScript packages. By codifying naming conventions, module boundaries, and import path rules, this skill ensures that new features, endpoints, and shared utilities are implemented consistently according to established project patterns, preventing technical debt and architectural drift.

Key Features

Detailed blueprints for adding new API endpoints, pages, and shared modules
Strict module boundary validation to prevent cross-app dependency leaks
Monorepo navigation across specialized apps (Web, API, Mobile) and shared packages
Enforcement of language-specific naming conventions for TypeScript, React, and Dart
Standardized import path management using workspace-aware aliases
0 GitHub stars

Use Cases

Creating cross-platform features that require synchronized changes across multiple apps
Onboarding developers to the complex Next.js, Fastify, and Flutter codebase
Architecting shared logic into reusable packages while maintaining clean boundaries

About

Key Features

Detailed blueprints for adding new API endpoints, pages, and shared modules
Strict module boundary validation to prevent cross-app dependency leaks
Monorepo navigation across specialized apps (Web, API, Mobile) and shared packages
Enforcement of language-specific naming conventions for TypeScript, React, and Dart
Standardized import path management using workspace-aware aliases
0 GitHub stars

Use Cases

Creating cross-platform features that require synchronized changes across multiple apps
Onboarding developers to the complex Next.js, Fastify, and Flutter codebase
Architecting shared logic into reusable packages while maintaining clean boundaries