lobster-linting

Audit ESLint warnings and protect stability locks in Lobsterized codebases.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/ClawStackStudios/ClawChives --skill lobster-linting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lobster-linting
Source: https://github.com/ClawStackStudios/ClawChives/tree/main/.crustagent/skills/lobster-linting
Command: npx skills add https://github.com/ClawStackStudios/ClawChives --skill lobster-linting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents generic linters from breaking project-specific architectural requirements and ensures that essential stability locks are maintained in Lobsterized codebases.

Core Features & Use Cases

  • Maintain Stability Locks: Protects critical code patterns required for Vite builds and UI features.
  • Audit Lint Warnings: Provides a structured workflow for understanding and categorizing linter issues.
  • Suppress False Positives: Offers a mechanism to safely ignore warnings for standard libraries or known safe deviations.
  • Use Case: When a linter flags an @ts-ignore block that is essential for Vite's environment variable replacement, this Skill guides you on how to protect it and document the deviation.

Quick Start

Audit the current lint warnings by checking the LINT_AUDIT.md file and the stability-locks.md reference.

Frequently Asked Questions about lobster-linting

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

FAQPage Schema
How do I stop ESLint from flagging intentional @ts-ignore blocks needed for Vite build-time replacement?

To stop ESLint from flagging essential @ts-ignore blocks for Vite environment variable replacement, use Stability Locks. This mechanism protects critical code patterns required for Vite builds and documents the intentional deviation.

What is the best way to audit lint warnings and suppress false positives in a TypeScript project?

The best way to audit lint warnings and suppress false positives is by checking the LINT_AUDIT.md file. It provides a structured workflow for categorizing linter issues and safely ignoring warnings for standard libraries or known safe deviations.

Why does my linter break project-specific architectural requirements in a Lobsterized codebase?

Generic linters break architectural requirements because they lack context for project-specific needs. This Skill prevents generic linters from breaking project-specific architectural requirements and ensures essential stability locks are maintained.

Can I use stability locks to protect UI features and Vite build patterns from security warnings?

Yes, you can use stability locks to protect UI features and Vite build patterns. The references/stability-locks.md file provides guidance on protecting critical code patterns required for Vite builds and UI features from lint and security warnings.

What should I do when a linter flags crypto slopsquatting or other false positives in standard libraries?

When a linter flags crypto slopsquatting in standard libraries, you should suppress the false positive. This Skill offers a mechanism to safely ignore warnings for standard libraries or known safe deviations documented in LINT_AUDIT.md.