Skill UI

This skill enforces a mandatory, comprehensive quality loop for all code changes. It guides users through running multiple specialized validation tools—including linters, type checkers, and security scanners—for diverse ecosystems (e.g., Node.js/TypeScript, Python). It ensures that code is robust, adheres to established style guides, and maintains type safety across all components before it can be considered complete or committed.

Plankton enforces Claude Code writing-time quality by running formatters and linters on every edit, generating Claude subprocesses to repair remaining violations, and shielding linter configs and package managers across Python, TypeScript, Shell, and documentation.

Guides reviews and production work with Uncle Bob principles—Clean Code, Clean Architecture, Clean Coder, Clean Agile, and disciplined pattern usage—so you can evaluate SOLID, boundaries, smells, professionalism, and process without replacing linters or formatters.

Provides golangci-lint configuration, practical guidance for running linters, interpreting output, suppressing warnings responsibly, and embedding linting into Go workflows and CI pipelines to keep quality high.

Defines mandatory contribution guidance for repository work, insisting contributors locate workflow documentation, follow branch/commit/PR templates, and run required linters or tests before submitting changes, without executing forbidden scripts.