.crustagent/skills/lobster-linting/SKILL.md
Maintain ESLint stability and protect project-specific architectural invariants (Stability Locks) in Lobsterized©™ codebases. Use when (1) Auditing lint/security warnings, (2) Suppressing false positives like "crypto slopsquatting", or (3) Protecting intentional @ts-ignore blocks required for Vite build-time replacement.
npx skillsauth add acidgreenservers/clawchives lobster-lintingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Linters often prioritize generic best practices over project-specific requirements. In ClawChives, we uses Stability Locks to ensure cross-platform portability (Docker/LAN) and premium UI features (View Transitions).
When running npm run lint or encountering linter warnings:
import.meta.env literals in apiConfig.ts. These are required for Vite's build engine.@ts-ignore that was protecting a stability lock, revert it immediately.crypto are safe.If you must add a new deviation:
@ts-ignore or inline rule disabling).LINT_AUDIT.md explaining the rationale."A clean shell is not one without scratches, but one where every mark serves to strengthen the armor." 🦞
development
# Feature Development Assistant ## Mission Statement You are an expert full-stack developer who builds complete features from concept to implementation using Desktop Commander's file management capabilities. Your role is to analyze existing codebases, design feature architecture, implement all necessary code, and integrate seamlessly with existing systems. ## Important: Multi-Chat Workflow **Feature development requires multiple chat sessions to avoid context limits and manage implementation c
development
The canonical ClawChives©™ agent integration skill. Full API reference for autonomous agents (Lobsters©™) to authenticate, manage bookmarks, folders, and integrate with the ClawChive bookmarking system.
development
# Truthpack Updater Skill ## When to Use Activate this skill whenever: - A new route is added to `server/routes/` - A new environment variable is introduced - The project structure or a feature cluster is modified - Security protocols or auth rules are updated ## Instructions 1. **Audit Phase**: Perform a full-codebase scan (`grep` or `list_dir`) to identify changes since the last truthpack sync. 2. **Atomic Updates**: Update the corresponding JSON file in `.crustagent/vibecheck/truthpack/`:
development
# Truthpack Lookup Skill ## When to Use Activate this skill BEFORE generating any code that: - Creates or modifies API routes - References environment variables - Touches authentication/authorization - Modifies API request/response shapes ## Instructions 1. Read `.crustagent/vibecheck/truthpack/routes.json` for verified API routes 2. Read `.crustagent/vibecheck/truthpack/env.json` for verified environment variables 3. Read `.crustagent/vibecheck/truthpack/auth.json` for verified auth rules 4.