skills.rest
betaTrident
betaTridentCOMMUNITY
Explore all skills by this author →
GitHub

repository-conventions

Standardize code structure and development patterns in the Manta repository.

Updated Jun 22, 2026
Search Tags:#architecture#standards#conventions#code-quality#best-practices
One-click install
npx skills add https://github.com/betaTrident/manta --skill repository-conventions-betatrident
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repository-conventions
Source: https://github.com/betaTrident/manta/tree/main/.claude/skills/repository-conventions
Command: npx skills add https://github.com/betaTrident/manta --skill repository-conventions-betatrident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all contributions to the Manta repository adhere to established architectural patterns, naming conventions, and testing standards, preventing technical debt and fragmentation.

Core Features & Use Cases

  • Pattern Enforcement: Provides guidance on module organization, import styles, and naming conventions (camelCase).
  • Workflow Standardization: Defines the expected approach for database migrations, feature development, and language-specific rule updates.
  • Use Case: When adding a new component to the game engine, use this Skill to verify that the file structure, test placement, and import patterns align with the existing repository architecture.

Quick Start

Apply the repository-conventions skill to review the proposed file structure and naming for the new tracking module.

Frequently Asked Questions about repository-conventions

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

FAQPage Schema
How do I maintain consistent code structure and conventions across an Astro and React codebase?▼

Maintaining consistent code structure requires standardizing module organization, import styles, and camelCase naming conventions across Astro and React files to prevent technical debt and fragmentation during feature development.

What are the best practices for standardizing file structure when adding a new component to a game engine?▼

Standardizing file structure for new components involves adhering to established architectural patterns, verifying test placement, and aligning import styles with existing repository architecture to prevent codebase fragmentation.

How do I enforce conventional commit standards and naming conventions for new feature implementations?▼

Enforce conventional commit standards and naming conventions by applying repository-wide rules requiring camelCase usage and established module organization for all new feature implementations and documentation updates.

Does this repository conventions guidance apply to database migrations and refactoring tasks?▼

Yes, repository conventions apply to database migrations and refactoring tasks by defining expected workflow approaches and language-specific rule updates to ensure consistent development patterns across the project.

Why do I need code quality standards for tracking module development in a shared repository?▼

Code quality standards are needed for tracking module development to verify that file structure, test placement, and import patterns align with existing architecture, thereby preventing technical debt and codebase fragmentation.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
Adonis0123Adonis0123
2

commit

Generate emoji-prefixed Conventional Commits messages from staged changes.

Community
Intermediate
CloakingGhostCloakingGhost

qa-agent

Automate code review, error fixing, and structural improvements via static analysis.

Community
Intermediate
andershi666andershi666
1

project-overview

Clarify repository architecture and code organization for the LobeHub monorepo.

Community
Intermediate