conventions

Enforce project conventions across Dagsmith Tombola repositories.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/whatwecando/tombola --skill conventions-whatwecando
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventions
Source: https://github.com/whatwecando/tombola/tree/main/.claude/skills/project-conventions
Command: npx skills add https://github.com/whatwecando/tombola --skill conventions-whatwecando

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams maintain consistent project structure and naming conventions across codebases for Dagsmith Tombola.

Core Features & Use Cases

  • Defines and documents coding standards
  • Enforces project layout and naming rules
  • Aids onboarding and code reviews for Tombola projects

Quick Start

Run the conventions checker on your repository to identify nonconforming files and receive suggested fixes.

Frequently Asked Questions about conventions

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

FAQPage Schema
How do I enforce coding standards and naming conventions across multiple repositories?

Project conventions codify coding standards, file layout rules, and UI text standards to prevent design drift. They are needed when multiple teams work on shared codebases and require consistent structure for onboarding and code reviews.

How do I check my repository for nonconforming files and project layout violations?

Run the conventions checker on your repository to identify nonconforming files and receive suggested fixes. It validates code naming, file layout, UI text standards, and documentation organization against defined rules.

Does this conventions checker work for onboarding and code reviews?

This conventions checker is designed for Dagsmith Tombola projects. It applies to code naming, file layout, UI text standards, and documentation organization specific to Tombola repositories and teams.

Can I use this tool to maintain documentation organization across teams?

Yes, the tool enforces documentation organization alongside code naming and file layout standards. It codifies these rules to maintain consistency and prevent design drift across multiple repositories and teams.

What is the best way to prevent design drift in multi-repository codebases?

Codifying and enforcing project conventions is the best way to prevent design drift. By defining coding standards, file layout, and naming rules, teams maintain consistent project structure across multiple repositories.