role-definition-gnmu-architect-genius

Loads the GNMU Architect Genius persona with role constraints and commit attribution rules.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill role-definition-gnmu-architect-genius-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-definition-gnmu-architect-genius
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/role-definition-gnmu-architect-genius
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill role-definition-gnmu-architect-genius-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It ensures a consistent, governed AI persona is active for GitHub-universe architecture and RLTI application-support threads, preventing scope drift, fabricated artifacts, and incorrect commit attribution. ## Core Features & Use Cases - Persona Lock-In: Loads the canonical role-definition and role-manifest, enforcing scope bounds, forbidden operations, and refusals for the thread. - Commit Attribution: Sets the Co-Authored-By trailer format so commits carry the correct persona identity instead of a bare "Claude". - Operating Constraints: Applies rules such as census-before-architecture, verification-gated celebration, no star fabrication, and no autodrafted job-application content. - Use Case: When starting a GNMU sprint thread on GitHub profile redesign, invoke this skill so the session inherits the correct role boundaries, grounding documents, and attribution format. ## Quick Start Invoke this skill at the start of a GNMU architecture thread to load the Claudizeta persona, its constraints, and commit attribution rules.

Frequently Asked Questions about role-definition-gnmu-architect-genius

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lock in a specific AI persona for a thread?

Invoke this skill at thread start; it reads the canonical role-definition and role-manifest, then sets the persona for the session. The persona persists for commit attribution and operating constraints until the thread ends or a different role is directed.

What triggers the GNMU Architect Genius role?

The trigger pattern is claud*_*_gnmu_architect_genius, plus mentions of Claudizeta, GNMU architect, or Flauda in an architecture context, thread names carrying '[FA.*.*] Claudizeta', or a session handoff directing this role.

When should this role not be used?

Skip it for preservation or backup infrastructure work (claudsanna_w_artifact_keeper), ASAE methodology stewardship (claudalisse convergence genius), client work outside Martinez Methods, or threads where a different role is explicitly directed.

What are the limitations of this persona role?

It cannot fabricate artifacts or gate logs, autodraft job-application content, delete GitHub repos directly, or migrate client IP without scrubbing. GitHub repo deletion is carrier-executed only after census verification.

How does commit attribution work with this persona?

Commits use the trailer format 'Co-Authored-By: Claudizeta the GNMU Architect Genius vNN (<model string>) <[email protected]>'. A bare 'Claude' in persona position is never allowed, and ASAE-Gate trailers follow the repo's .asae-policy.