Loading...
Loading...
Found 19 Skills
Strategic thinking framework integrating First Principles Analysis, Stanford Design Thinking, and MIT Systems Engineering for deeper problem-solving. Use when performing architecture decisions, technology selection trade-offs, root cause analysis, cognitive bias detection, or first principles decomposition. Do NOT use for code quality validation (use moai-foundation-quality instead) or implementation workflows (use moai-workflow-ddd instead).
Use when facing complex decisions, architectural trade-offs, philosophical questions, or any problem requiring deep analysis before action. Use when the user asks to "think deeply", "question assumptions", "analyze from first principles", "challenge this decision", debates between two approaches (e.g. monolith vs microservices, build vs buy, SSR vs CSR), or invokes /socrates. Also triggered when other skills need a thinking engine for rigorous pre-analysis. Even if the problem seems simple, if there are hidden assumptions worth examining, this skill applies.
Specialized skill for .NET unit testing fundamentals and FIRST principles. Use this skill when you need to create unit tests, understand testing fundamentals, learn the 3A Pattern, or master testing best practices. Covers FIRST principles, AAA Pattern, Fact/Theory, test pyramid, etc. Keywords: unit test, unit testing, test fundamentals, FIRST principle, 3A pattern, AAA pattern, Arrange Act Assert, Fact, Theory, InlineData, how to write tests, testing best practices, creating unit tests
Langgeladi Cognition Check. Two modes: Trace (an idea → trace to the bottom layer → build a system) and Topple (a wrong cognition → flip → see the truth). Trigger methods: /lang-think, "I have an idea", "I think XX is because of YY", "help me figure this out", "is this view correct" Langgeladi cognition check. Two modes: Trace (idea → first principles → system) and Topple (wrong belief → flip → truth). Trigger: /lang-think, "I have an idea", "help me think this through", "is this right"
Deep codebase analysis for building architectural context before vulnerability or bug finding. Uses line-by-line analysis with First Principles, 5 Whys, and 5 Hows. Use when deep comprehension is needed before security auditing, architecture review, or threat modeling.
This skill should be used when the user asks to "audit this code", "deep analysis before security review", "build architectural context", "line-by-line code review", or needs ultra-granular analysis before vulnerability discovery. Provides structured context-building methodology with First Principles, 5 Whys, 5 Hows micro-analysis patterns.
Use when solution space exploration is complete and you're ready to create an implementation plan. Enforces "simple over easy" - the fundamentally right solution, not the path of least resistance. Triggers after /design-solution, when a solution has been chosen, or when asked to "make a plan" or "create a plan".