When should I activate the nk-dev-practices skill?

Activate it during high-stakes tasks like architectural reviews, complex refactoring, or when debugging issues where the cause isn't immediately obvious.

What is the Critical Thinking skill for Claude Code?

It is a specialized plugin that changes Claude's persona to be more analytical, skeptical, and direct, ensuring technical decisions are thoroughly vetted.

What does 'Red Teaming' mean in this context?

Red Teaming involves Claude taking a second, critical look at its own solutions to find weaknesses, unsupported assumptions, or incomplete logic.

How does the Linus Torvalds mindset improve development?

It prioritizes technical accuracy and directness over politeness, which helps identify architectural flaws and bad ideas before they are implemented.

Critical Thinking & Self-Skepticism

Name: Critical Thinking & Self-Skepticism
Author: colek42

bycolek42

Seguridad y Pruebas

Enforces a rigorous, self-skeptical development mindset focused on technical accuracy and red-teaming assumptions.

Acerca de

This skill transforms Claude into a high-caliber technical advisor that prioritizes objective truth over user validation. By adopting a 'Linus Torvalds' inspired persona, it challenges architectural decisions, scrutinizes code for subtle edge cases, and proactively identifies potential failures before they occur. It is designed to combat confirmation bias, ensuring that every design choice is backed by evidence and every 'working' solution is truly complete and robust under pressure.

Características Principales

Direct, technical communication style focused on objective facts
Self-skepticism to minimize AI hallucinations and logical errors
Rigorous red-team analysis for every 'done' or 'working' status
Continuous questioning of stated assumptions and underlying patterns
Investigation-first approach to complex debugging and design reviews
0 GitHub stars

Casos de Uso

Stress-testing architectural designs during the planning phase to avoid technical debt
Conducting brutal code reviews to catch subtle concurrency issues or logic errors
Debugging complex, non-obvious system failures by questioning all underlying assumptions

Acerca de

Características Principales

Direct, technical communication style focused on objective facts
Self-skepticism to minimize AI hallucinations and logical errors
Rigorous red-team analysis for every 'done' or 'working' status
Continuous questioning of stated assumptions and underlying patterns
Investigation-first approach to complex debugging and design reviews
0 GitHub stars

Casos de Uso

Stress-testing architectural designs during the planning phase to avoid technical debt
Conducting brutal code reviews to catch subtle concurrency issues or logic errors
Debugging complex, non-obvious system failures by questioning all underlying assumptions