seis-god-mode-developer

Coordinates cross-layer SEIS improvements across product, AI, security, and governance surfaces.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-god-mode-developer-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-god-mode-developer
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/plugins/seis/skills/seis-god-mode-developer
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-god-mode-developer-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Broad engineering requests that touch product experience, application behavior, AI/AGI learning, cloud/security posture, and governance often produce shallow, unverifiable changes. This Skill enforces a controlled cross-layer operating lane so every wide-scope change ships visible behavior backed by contract evidence. ## Core Features & Use Cases - Cross-Layer Mapping: Maps each request to product, application, AI/AGI, cloud/security, and governance layers before any editing begins. - Contract-Backed Changes: Requires adding or updating a telemetry, native parity, or AI/AGI contract whenever a mode changes runtime behavior. - Evidence-Gated Validation: Runs a dedicated check script and reserves the full governance quality gate for repository closure. - Use Case: When a user asks to improve everything across the SEIS demo at once, the Skill forces visible behavior changes in the web feature, parity updates in the Swift native contract, and a passing run of the dedicated validation script. ## Quick Start Ask the agent to use SEIS God Mode Developer to make one high-impact improvement across the SEIS demo and validate it with the dedicated check script.

Frequently Asked Questions about seis-god-mode-developer

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

FAQPage Schema
How do I run a cross-layer improvement across the SEIS platform?▼

Invoke the God Mode Developer lane, which first maps the work to product, application, AI/AGI, cloud/security, and governance layers. It then requires visible behavior changes and contract updates before validation with the dedicated check script.

When should I use God Mode instead of a single-feature change?▼

Use it when the request is too broad to count as one isolated feature, such as when the user says every topic or everything must improve. Single-scope changes should follow normal feature workflows instead.

How do I validate God Mode Developer changes in SEIS?▼

Run npm run check:seis-god-mode-developer for the dedicated validation of the lane. Use npm run quality:governance only when the change is ready for full repository closure.

Does God Mode let me skip security or rollback checks?▼

No. The operating rules explicitly state it is not permission to skip discovery, security, rollback, or validation. It exists to stop shallow progress claims and force contract-backed evidence.

What files must stay in parity when changing SEIS demo behavior?▼

The web telemetry contract and the Swift native shell contract must stay aligned, along with the AI/AGI contract in content/development. Any mode that changes runtime behavior requires a contract addition or update.