genesis-development

Apply codified workflows and checks to Genesis core software development.

90|16|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/WingedGuardian/GENesis-AGI --skill genesis-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: genesis-development
Source: https://github.com/WingedGuardian/GENesis-AGI/tree/main/.claude/skills/genesis-development
Command: npx skills add https://github.com/WingedGuardian/GENesis-AGI --skill genesis-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates best practices and guardrails for developing Genesis itself, helping teams stay aligned on process and quality when making internal changes.

Core Features & Use Cases

  • Structured guidance for on-load mindset, wiring discipline, and architecture review to reduce runtime issues.
  • Enforced development workflow: pre-commit checks, gating, and risk-aware review practices for multi-file changes.
  • References to governance: load gates, reference router usage, and contribution pathways for Genesis internals.

Quick Start

Describe your Genesis core task (e.g., wiring runtime, adding a feature, or debugging startup) so this skill can guide your approach.

Frequently Asked Questions about genesis-development

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

FAQPage Schema
What is the best way to enforce code-review and pre-commit checks when modifying Genesis core files?

The best way to enforce pre-commit checks for Genesis core changes is applying codified workflows that gate commits and ensure modifications under src/, .claude/, or tests/ are safe, testable, and well-documented.

How do I wire runtime and bootstrap processes safely during Genesis core development?

To wire runtime and bootstrap safely, apply structured guidance for on-load mindset and wiring discipline, ensuring changes to Genesis core internals satisfy architecture review and reduce runtime issues.

When do I need architecture review and timeouts policy for Genesis core software engineering?

You need architecture review and timeouts policy when modifying Genesis core files under src/, .claude/, or tests/, ensuring changes to runtime, bootstrap, and MCP tooling satisfy load gates and reference routing usage.

What limitations exist when applying coding guidelines to MCP tooling and reference routing in Genesis?

Limitations exist when coding guidelines do not satisfy governance requirements for load gates and reference router usage, requiring risk-aware review practices to ensure changes to MCP tooling are safe and testable.

Does Genesis development workflow support debugging startup and adding new features simultaneously?

Yes, Genesis development workflow supports debugging startup and adding features by applying codified workflows and checks to modifications under src/ and tests/, ensuring changes are safe, testable, and well-documented.