Missing Project Standards

Detects missing tsconfig, linter, .gitignore, .env.example, and other project standards.

Rule ID:missing-project-standards

Examples#

BadNo tsconfig, no linter, no .gitignore

my-project/
├── src/
│   ├── index.ts        # TypeScript but no tsconfig.json!
│   └── utils.ts
├── node_modules/       # No .gitignore — committed to git!
├── .env                # Secrets committed!
└── package.json        # No lint script, no format script

GoodComplete project standards

my-project/
├── src/
│   ├── index.ts
│   └── utils.ts
├── tsconfig.json       # TypeScript config
├── biome.json          # Linter + formatter
├── .gitignore          # Ignores node_modules, dist, .env
├── .env.example        # Documents required env vars
├── .env                # NOT committed (in .gitignore)
└── package.json        # Has lint, format, test scripts

What It Detects#

highTypeScript installed but no tsconfig.json

TypeScript installed but no tsconfig.json found

Fix: Run: npx tsc --init.

mediumNo linting configuration

No linting configuration found

Fix: Add ESLint or Biome for consistent code quality.

mediumNo .gitignore

No .gitignore file found

Fix: Add a .gitignore to prevent committing node_modules, dist, .env, etc.

medium.env exists but no .env.example

Project uses .env but no .env.example for documentation

Fix: Add .env.example with placeholder values so teammates know what vars are needed.

Configuration#

This rule is enabled by default. To disable it:

.vibertestrc.jsonjson

{
  "rules": {
    "missing-project-standards": {
      "enabled": false
    }
  }
}

#021 Accessibility #023 Missing Production Basics