noobygains/godmode

1

fault-diagnosis Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

noobygains/godmode

60

2

design-research Use when building ANY website, web app, landing page, or web-based UI - searches real template marketplaces for profe…

noobygains/godmode

54

3

ux-patterns Use when building ANY user interface - web app, game, CLI, dashboard, landing page, or component - ensures all UI out…

noobygains/godmode

54

4

specification-first Use when building any feature, API, module, or system before writing implementation code - produces a structured beha…

noobygains/godmode

53

5

task-planning Use when you have a spec or requirements for a multi-step task, before touching code

noobygains/godmode

53

6

github-search Use when about to build any feature, library, or system - searches GitHub and package registries for existing impleme…

noobygains/godmode

52

7

comprehension-check Use when implementing any substantial feature, multi-file modification, or architectural change - produces a plain-la…

noobygains/godmode

51

8

intent-discovery Use when starting any creative work - creating features, building components, adding functionality, or modifying beha…

noobygains/godmode

51

9

agent-messaging Use when dispatching subagents, composing prompts for teammates, structuring handoff reports, or managing context bou…

noobygains/godmode

50

10

parallel-execution Use when facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation o…

noobygains/godmode

50

11

rationale Use when a user requests new work - features, components, integrations, or additions - to challenge assumptions, eval…

noobygains/godmode

50

12

system-design Use when making technology or structural decisions - selecting databases, APIs, auth strategies, caching layers, file…

noobygains/godmode

50

13

ui-engineering Use when constructing frontend components, selecting layout strategies, orchestrating state, or assembling interactiv…

noobygains/godmode

50

14

codebase-research Use when building ANY feature within an existing project - search the current codebase for existing patterns, convent…

noobygains/godmode

49

15

environment-awareness Use when starting a session, running shell commands, installing packages, or diagnosing platform-specific failures - …

noobygains/godmode

49

16

error-recovery Use when repeated fix attempts fail, the agent appears stuck in a loop, or complexity is increasing without progress

noobygains/godmode

49

17

merge-protocol Use when implementation is finished, tests are green, and you need to decide how to land the work - presents structur…

noobygains/godmode

49

18

pattern-matching Use when contributing code to an existing project - guarantees that every new line mirrors the established convention…

noobygains/godmode

49

19

quality-enforcement Use when preparing code for commit, PR, or merge - covers linting, type safety, bundle budgets, coverage thresholds, …

noobygains/godmode

49

20

security-protocol Use when writing code that processes user input, manages authentication or authorization, constructs database queries…

noobygains/godmode

49

21

test-first Use when implementing any feature or bugfix, before writing implementation code

noobygains/godmode

49

22

activation Use when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before A…

noobygains/godmode

48

23

completion-gate Use when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verifica…

noobygains/godmode

48

24

delegated-execution Use when executing implementation plans with independent tasks in the current session

noobygains/godmode

48

25

deployment-advisor Use when making technology, hosting, or infrastructure decisions — recommends services, databases, and deployment str…

noobygains/godmode

48

26

design-integration Use when operating in a codebase that employs an existing design system (shadcn/ui, Material UI, Ant Design, Chakra, …

noobygains/godmode

48

27

knowledge-capture Use when completing any meaningful task - distill patterns, lessons, and insights from the interaction and persist th…

noobygains/godmode

48

28

performance-tuning Use when performance is a concern - sluggish pages, slow queries, bloated bundles, high-latency APIs, or whenever som…

noobygains/godmode

48

29

protocol-authoring Use when creating new protocols, editing existing protocols, or validating protocols work before deployment

noobygains/godmode

48

30

quality-gate Use when finishing tasks, shipping significant features, or before landing changes to ensure work meets standards thr…

noobygains/godmode

48

31

reference-engine Use when building ANYTHING - the universal reference-first system that routes every task to proven reference implemen…

noobygains/godmode

48

32

review-response Use when processing code review feedback before making changes, particularly when suggestions are ambiguous, technica…

noobygains/godmode

48

33

team-orchestration Use when a task benefits from multiple Claude instances collaborating with peer-to-peer messaging - parallel research…

noobygains/godmode

48

34

workspace-isolation Use when starting feature work that needs isolation from the current workspace or before executing implementation pla…

noobygains/godmode

48

35

project-bootstrap Use when launching a new project, initializing a repository, or building a codebase from the ground up - addresses di…

noobygains/godmode

47

36

task-runner Use when you have a written implementation plan to execute in a separate session with review checkpoints

noobygains/godmode

47