rule-validator

Detects and reports Gemini mod code rule violations in JavaScript/TypeScript.

3|1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/Ariedam64/Gemini --skill rule-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-validator
Source: https://github.com/Ariedam64/Gemini/tree/main/.claude/skills/rule-validator
Command: npx skills add https://github.com/Ariedam64/Gemini --skill rule-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gemini mod code often risks architectural or safety violations that can degrade stability and security. This Skill provides automated checks to enforce a consistent rule set across core, modules, features, UI, WebSocket, and state, catching violations early in the development lifecycle.

Core Features & Use Cases

  • Validates core rules (no hardcoded game data, DOM boundaries, side effects during import)
  • Enforces feature and module structure conventions, and TypeScript strictness
  • Generates actionable reports with file paths and line numbers to guide fixes
  • Supports integration into CI or local development workflows to maintain code quality across the Gemini project

Quick Start

Run the validator against your codebase to identify and fix rule violations.

Frequently Asked Questions about rule-validator

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

FAQPage Schema
How do I validate code rules for hardcoded data and DOM misuse in JavaScript?

Automated static analysis validates JavaScript and TypeScript code in src directories to detect hardcoded data, DOM misuse, and improper side effects. It reports violations with file paths and line numbers while suggesting fixes to ensure code compliance.

What's the best way to enforce TypeScript strictness and module structure conventions?

Enforcing TypeScript strictness and module structure is achieved by running a static analysis validator on the codebase. It checks core, modules, features, UI, WebSocket, and state layers, generating actionable reports with file paths and line numbers to guide structural fixes.

Can I integrate static analysis linting into my local development workflow?

Static analysis linting can be integrated into both local development workflows and CI pipelines. Running the validator against your codebase identifies architectural or safety violations early, maintaining consistent code quality across the project lifecycle.

Does the rule validator support both JavaScript and TypeScript codebases?

The rule validator supports both JavaScript and TypeScript codebases within src and related directories. It analyzes code across core, modules, features, UI, WebSocket, and state layers to ensure compliance and TypeScript strictness are properly satisfied.

Why does static code validation report side effects during import?

Static code validation reports side effects during import because they violate core architectural safety rules. Detecting these improper side effects early alongside hardcoded game data and DOM boundaries prevents stability degradation and ensures consistent module behavior.

How do I identify state management and WebSocket violations in my project?

Identifying state management and WebSocket violations is done by running an automated validator that scans source code. It detects improper storage naming issues and architectural violations across state and WebSocket layers, reporting exact file paths and line numbers for resolution.