shared-conventions

Standardize commit formats, directory layout, and testing norms across monorepo modules.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/javicasper/memory-forge --skill shared-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared-conventions
Source: https://github.com/javicasper/memory-forge/tree/main/examples/monorepo/.claude/skills/shared-conventions
Command: npx skills add https://github.com/javicasper/memory-forge --skill shared-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project-wide conventions and patterns that apply to all apps/modules, helping teams discuss structure and standards consistently across the monorepo.

Core Features & Use Cases

  • Defines and enforces a standard commit message format, ensuring clear history and traceability.
  • Documents and promotes a consistent code organization pattern (src/, domain/, application/, infrastructure) to improve maintainability.
  • Provides baseline testing conventions (unit and integration tests) to standardize quality across projects.
  • Use Case: A new module adopts the shared conventions to align its folder structure and commit messages with existing apps, reducing ramp-up time.

Quick Start

Copy the shared-conventions skill into your monorepo to start applying project-wide patterns across all work and modules.

Frequently Asked Questions about shared-conventions

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

FAQPage Schema
How do I standardize project structure and coding conventions across a monorepo?

Standardize project structure across a monorepo by defining a uniform directory layout (src/, domain/, application/, infrastructure) and enforcing consistent commit message formats to ensure maintainability across all modules.

What directory layout should I use for organizing modules in a monorepo?

Organize monorepo modules using a standard directory layout that separates concerns into src/, domain/, application/, and infrastructure folders to improve code maintainability and team alignment.

How do I enforce conventional commit messages across multiple apps?

Enforce conventional commit messages across multiple apps by applying shared project-wide conventions that specify a standard commit format, ensuring clear history and traceability for all team members.

What are the basic testing norms for standardizing quality in a monorepo?

Basic testing norms for a monorepo involve applying baseline conventions for both unit and integration tests to standardize quality and ensure consistent testing practices across all projects.

Does this shared conventions approach work for teams onboarding new modules into an existing monorepo?

Yes, adopting shared conventions works for onboarding new modules by aligning their folder structure and commit messages with existing apps, which significantly reduces ramp-up time for developers.

When do I need to apply project-wide conventions to my codebase?

Apply project-wide conventions when your monorepo grows to multiple apps and modules, helping your team discuss structure and standards consistently across the entire project.