GitHub
rubber-ducking
Logic validation by verbalization. Translate code to plain English to catch semantic errors. Use before running complex logic or when debugging "it should work" failures.
☆ 0View skill
calvyntwh AI Skills
GitHub ↗Browse published AI skills maintained by calvyntwh. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
10Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
occams-razor
Complexity Pruning and Simplification using the Subtraction Method. Use when refactoring, reducing boilerplate, or challenging over-engineered solutions.
☆ 0View skill
GitHub
systems-thinking
Architectural analysis using Feedback Loops and System Dynamics. Use when designing architectures, scaling systems, or analyzing side effects.
☆ 0View skill
GitHub
chestertons-fence
A safety protocol for refactoring. Do not remove a fence until you know why it was put up. Use when deleting, simplifying, or "fixing" code you do not fully understand.
☆ 0View skill
GitHub
create-new-skill
Specialized skill for creating new Antigravity agent skills. Follows a Research -> Create -> Deploy workflow where the Agent directly creates the necessary files.
☆ 0View skill
GitHub
pareto-principle
Strategic Prioritization using the 80/20 Rule. Optimization of Scope. Use when planning tasks, managing feature creep, or maximizing ROI.
☆ 0View skill
GitHub
inversion-thinking
Proactive failure analysis using the Saboteur Method. Use when designing critical systems, security features, or debugging root causes.
☆ 0View skill
GitHub
first-principles-thinking
A mental model for breaking down basic truths to generate original solutions. Use for innovation, novel problems, or when stuck in conventional thinking.
☆ 0View skill
GitHub
decision-matrix
Objective trade-off analysis using weighted criteria. Eliminates popularity bias by requiring user-defined priorities. Use when choosing between technologies, architectures, or vendors.
☆ 0View skill
GitHub
map-vs-territory
Empiricism and Reality Checking. Prioritizing runtime truth over documentation. Use when debugging discrepancies, validating APIs, or when code comments might be outdated.
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.