A ClusterRole grants permissions across the entire cluster and a ClusterRoleBinding attaches it to subjects. The ClusterRole and ClusterRoleBinding YAML Generator writes both documents in one file so you do not have to recall the rbac.authorization.k8s.io/v1 schema.
You set the ClusterRole name, then list one or more rules, one per line as apiGroups|resources|verbs (empty apiGroup = core). You then set the ClusterRoleBinding name and subjects, one per line as kind|name|namespace, where kind is User, Group or ServiceAccount. The tool wires up the roleRef automatically. Because these are cluster-scoped, there is no namespace on the resources themselves. The resulting YAML is valid rbac.authorization.k8s.io/v1.
Names are validated as RFC 1123 labels, at least one rule and one subject are required, and each rule needs resources and verbs. Problems are reported in a clear panel. Everything runs locally and nothing is uploaded.