project-standards

Enforce project hygiene rules for dependencies, packaging, naming, and tooling.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/murphyjoseph/dojo-kit --skill project-standards-murphyjoseph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-standards
Source: https://github.com/murphyjoseph/dojo-kit/tree/main/skills/project-standards
Command: npx skills add https://github.com/murphyjoseph/dojo-kit --skill project-standards-murphyjoseph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hard rules ensure every file, package, and dependency decision is consistent and maintainable across teams.

Core Features & Use Cases

  • Enforces naming, packaging, and security conventions to reduce bikeshedding and errors.
  • Guides project structure and commit hygiene for reliable collaboration.
  • Use case: apply the standards when onboarding new codebases or enforcing CI checks.

Quick Start

Apply the project hygiene rules to initialize and enforce consistent structure, naming, and tooling decisions.

Frequently Asked Questions about project-standards

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

FAQPage Schema
How do I enforce project hygiene rules for naming, packaging, and dependencies in a JavaScript monorepo?

You can enforce project hygiene by applying concrete checks for package manager usage, version pinning, file naming conventions, and dependency installation during setup, CI checks, and code reviews.

What conventions should I use for structured commits and dependency management in TypeScript projects?

Structured commits and dependency management in TS projects should follow universal rules for version pinning, package manager usage, and naming to ensure consistent and maintainable code across teams.

Can I use this tool to apply project structure standards during code onboarding?

Yes, you can apply these project hygiene standards when onboarding new codebases to guide project structure and ensure consistent naming, packaging, and tooling decisions, reducing bikeshedding and errors.

Does this approach work for both frontend and backend JavaScript projects?

Yes, these universal project hygiene rules apply to both frontend and backend JS/TS projects, enforcing consistent standards for dependencies, packaging, naming, and tooling across the entire stack.

What is the best way to stop bikeshedding over file naming and packaging conventions?

The best way to stop bikeshedding over file naming and packaging is to enforce hard project hygiene rules that dictate concrete conventions, ensuring every dependency and file decision is consistent.

When do I need hard rules for project hygiene and dependency version pinning?

You need hard rules for project hygiene and dependency version pinning when managing JS/TS monorepos or team projects where consistent standards, reliable collaboration, and maintainable code are required.