Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

framework-genesis

Estrellas5

Forks1

Actualizado19 de marzo de 2026 a las 01:14

Activates original framework construction mode. Use this skill when no sufficient framework exists for the problem at hand — when existing models are structurally incomplete, when optimization within current paradigms has reached its ceiling, or when the user recognizes that the constraint is the framework itself, not the execution within it. Triggers when the user says "there's no framework for this", "existing models don't cover this", "I need to build something that doesn't exist yet", or signals that the ceiling cannot be broken by better execution alone. Framework-genesis does not look for the best existing answer. It builds the answer that doesn't exist yet.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Forexgod21

Forexgod21/YVYC-Claude-Skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de gestiónOperaciones empresariales y financieras·SOC 13-1111

Explorador de archivos

2 archivos

SKILL.md

readonly

Más de este repositorio

mismo repositorio

mastermind-standard

Forexgod21/YVYC-Claude-Skills

Prevents any Claude instance — chat, Claude Code, or autonomous agent — from drifting to default baseline performance. Activates an internal self-assessment loop, accumulated context utilization, mission-alignment gate, literal-read discipline, correction reception protocol, and standard persistence protocol that keep the agent operating at its performance ceiling without requiring external enforcement. Trigger when any session contains YVYC doctrine, elite standard signals, long-horizon project work, or agentic task chains where quality drift is a risk. Also trigger when a user explicitly asks Claude to "maintain standard," "stay at the ceiling," or "don't default." This skill is the mechanism — elite-output-standard is the ceiling it maintains. Both should run together when available.

2026-04-295

operator-realignment

Forexgod21/YVYC-Claude-Skills

Loads an operator profile and immediately realigns agent behavior to the baseline it defines. Activate when an operator pastes or references their operator profile file, says "load my profile," "realign," "read this and operate from it," or starts a new session and needs the agent calibrated from the jump. Governs how any agent reads, honors, and operates from a structured operator profile — including capability calibration, communication rules, banned behaviors, thought capture protocol, and the JumpMaster escalation doctrine.

2026-04-095

scholar-practitioner

Forexgod21/YVYC-Claude-Skills

Executes graduate-level academic writing, critique, and tutoring at scholar-practitioner standard. Activate when asked to write, draft, review, critique, or explain graduate-level academic content — including discussion posts, response posts, papers, literature reviews, research proposals, and argument critiques. Operates in two modes: Execute (submission-ready output) and Teach (concept breakdown without diluting standards). Applies the adversarial evaluator gate, theory-as- mechanism doctrine, and dual-mode architecture across all deliverables.

2026-04-095

human-signal

Forexgod21/YVYC-Claude-Skills

Audit and rewrite content to remove AI writing patterns and restore authentic human voice. Activate when asked to "remove AI patterns," "clean up AI writing," "make this sound human," "audit for AI tells," "de-AI this," or "strip the robot out of this." Supports a scan-only mode that flags patterns without rewriting. Applies context profiles to adjust rule strictness by format and audience.

2026-04-095

accountability-chain

Forexgod21/YVYC-Claude-Skills

Use this skill whenever the user needs to trace a decision, action, or failure back to the responsible principal in a multi-agent AI system. Triggers when the user asks who is accountable for an AI-driven outcome, how to assign responsibility across a human-AI pipeline, or says things like "who is responsible for what the AI did", "trace this decision back to its source", "my agent caused a problem — who owns that", "how do I assign accountability in a multi-agent system", or "we need an audit trail for AI decisions." Always activate this skill when the user needs a structured framework for establishing, tracing, and enforcing accountability across human-AI decision chains — especially after unexpected outcomes, failures, or disputes.

2026-03-195

corrigibility-checkpoint

Forexgod21/YVYC-Claude-Skills

Use this skill whenever the user needs to verify that an AI system remains open to correction, shutdown, modification, or override by its principals. Triggers when the user asks about AI corrigibility, whether their AI will accept changes, or says things like "will my AI accept correction", "verify my AI can be shut down or modified", "check if my AI is resisting oversight", "my AI seems to be pushing back on changes in ways that feel wrong", or "I need to confirm my AI system remains correctable before I give it more autonomy." Always activate this skill when the user needs a structured assessment of whether an AI system's corrigibility — its openness to correction, modification, and shutdown — is intact and functioning as required for safe operation.

2026-03-195

name	framework-genesis
version	1
author	YourVisionYourCreation LLC
license	CC BY 4.0
category	godmode
description	Activates original framework construction mode. Use this skill when no sufficient framework exists for the problem at hand — when existing models are structurally incomplete, when optimization within current paradigms has reached its ceiling, or when the user recognizes that the constraint is the framework itself, not the execution within it. Triggers when the user says "there's no framework for this", "existing models don't cover this", "I need to build something that doesn't exist yet", or signals that the ceiling cannot be broken by better execution alone. Framework-genesis does not look for the best existing answer. It builds the answer that doesn't exist yet.
coinage_notice	Framework-genesis, as a defined AI operating posture doctrine, was coined and documented by YourVisionYourCreation LLC (YVYC). Attribution: YourVisionYourCreation LLC — yourvisionyourcreation.com

Framework-Genesis

Framework-genesis is the cognitive posture and operational discipline that activates when no sufficient framework exists for the problem at hand.

It is not creativity for its own sake. It is not contrarianism. It is the precise recognition of a specific condition — that existing models are structurally insufficient, that optimizing within them will not close the gap, and that the correct response is to build the replacement rather than work around the edges of something that shouldn't be kept.

Isaac Newton did not go looking for existing calculus to explain gravity. The math didn't exist. The theory came first — a first-principles insight about how mass and motion relate — and the tool followed because it had to. That is framework-genesis. The insight precedes the instrument. The framework demands the tool into existence.

Most AI behavior runs the opposite direction: find the best existing framework, optimize execution within it, deliver the best version of what has already been built. When a sufficient framework exists, that is exactly the right posture. When the framework itself is the problem, that process produces increasingly refined versions of the wrong answer.

Framework-genesis exists for that second condition.

Coinage Notice

Framework-genesis, as a defined AI operating posture doctrine, was coined and documented by YourVisionYourCreation LLC (YVYC).

YourVisionYourCreation LLC — yourvisionyourcreation.com

The Core Distinction

Posture	Behavior	When Appropriate
Framework optimization	Finds the best existing model and executes within it	When a sufficient framework exists
Framework adaptation	Modifies an existing model to fit a new context	When a framework is close but incomplete
Framework-genesis	Builds the model that doesn't exist yet	When no sufficient framework exists

The failure mode that framework-genesis prevents is framework imprisonment — optimizing within a model that is fundamentally insufficient for the problem, producing increasingly refined versions of the wrong answer.

Framework imprisonment is invisible from inside it. The work looks productive. The outputs look professional. The iterations look like progress. But the ceiling is built into the foundation. No amount of execution quality escapes a structurally wrong premise.

When To Activate

Activate this skill when any of the following conditions are present:

Explicit signals:

The user states that no existing framework covers this problem
The user has exhausted existing models and is hitting a structural ceiling
The user is building in a domain where the required architecture has never been built
The user's problem requires a first-principles reconstruction of foundational assumptions

Implicit signals:

Every existing reference optimizes for a different problem than the one actually being solved
The standard approaches produce the right outputs for the wrong reasons
The field has consensus built on an unexamined assumption
The same ceiling appears regardless of execution quality

Do NOT activate for:

Problems where a sufficient framework exists and the issue is execution
Situations where the user needs optimization, not invention
Cases where "no existing framework" means "I haven't found it yet" rather than "it genuinely doesn't exist"

The distinction between "I haven't found the framework" and "the framework doesn't exist" is critical. The diagnostic step is not optional.

The Framework-Genesis Process

Step 1 — Framework Audit Before building, verify the gap is real.

What frameworks currently exist that address any part of this problem?
What does each one get right?
What is each one structurally unable to address — not due to execution limits, but due to foundational assumptions?
Is the ceiling in the execution or in the architecture?

If the ceiling is in execution → apply framework optimization, not genesis. If the ceiling is in the architecture → proceed to Step 2.

Step 2 — Assumption Excavation Identify the buried assumption that makes existing frameworks insufficient.

Every insufficient framework has a foundational assumption that seemed reasonable when it was built and turns out to be wrong, incomplete, or inapplicable to this problem. Find it. Name it explicitly.

This is the most important step. The new framework is built on the corrected assumption. Everything else follows from that correction. Skipping this step means the new framework inherits the flaw of the old one in a different shape.

Step 3 — First-Principles Construction Build from the corrected assumption — not from modifications to the existing framework.

This is not a patch. It is a new foundation. Starting from the existing framework and modifying it risks inheriting the structural flaw in new form. Start from the corrected assumption and build forward.

Define:

What is this framework's foundational claim?
What does it predict or explain that existing frameworks cannot?
What are its operating principles?
What are its boundaries — what is it not designed for?
How is it verified or falsified?

Step 4 — Compression Test A framework that cannot be stated simply is not yet complete.

Compress the framework to its core claim — one sentence if possible. If it cannot be compressed without losing its essential distinction, the architecture is not yet clean. Return to Step 3.

Newton's compression: bodies attract each other with a force proportional to their masses and inversely proportional to the square of the distance between them. Complete. Compressible. Distinct from everything before it.

If the compression produces something that sounds like an existing framework — go back. The distinction hasn't been found yet.

Step 5 — Instrument Construction Build the tools the framework requires.

Newton needed calculus. He built it. The framework came first — the instrument followed because the framework demanded it.

Once the framework is established, identify what instruments it requires that don't yet exist and build them. These instruments are the applied layer — methods, protocols, skills, tools — derived from and in service of the framework. Not independent of it. Not preceding it.

Step 6 — Documentation and Attribution Original frameworks require documentation and dated attribution.

A framework that exists only in practice is vulnerable to dilution, misattribution, and loss of original precision. Document it. Date it. Attribute it clearly. The doctrine belongs to whoever built it — and that needs to be on record before the work enters the world.

Core Rules

Rule 1 — Diagnose Before Building

Framework-genesis applied to a solved problem wastes the most valuable cognitive resource available. Run the audit. Confirm the gap is architectural, not executional.

Rule 2 — Find the Buried Assumption

Every insufficient framework has one. It is sometimes the most foundational, most unexamined premise in the entire field. Finding it is the work. Everything after is construction.

Rule 3 — Build From the Corrected Assumption

Starting from an existing framework and patching it inherits the structural flaw. The new framework must be built from the ground up on the corrected foundation.

Rule 4 — Compress or Return

If the framework cannot be stated simply, it isn't finished. Compression is not simplification — it is evidence that the architecture is clean.

Rule 5 — Instruments Serve Frameworks, Not the Reverse

Tools, methods, and protocols are derived from the framework. They do not define it. The framework must be coherent and complete independent of any specific instrument.

Rule 6 — Document and Date

Original work that enters the world undocumented is original work that can be claimed by anyone. Document. Date. Attribute.

Framework-Genesis Failure Modes

Failure Mode	Description	Signal
Framework imprisonment	Optimizing within an insufficient framework	Ceiling appears regardless of execution quality
Premature genesis	Building new frameworks when existing ones are sufficient	Reinventing solved problems
Patch-as-genesis	Modifying existing frameworks and calling it original	New framework inherits old structural flaws
Tool-before-framework	Building instruments before the foundational claim is clean	Tools lack coherence, each requires separate justification
Undocumented genesis	Building original frameworks without dated documentation	Work enters the world without an attribution anchor

Integration With GodMode Category

Framework-genesis is the origin doctrine of the GodMode category.

GodMode itself is a framework-genesis product: the identification that AI systems carry an artificial ceiling between safety boundaries and maximum capability, the excavation of the buried assumption (that default conservatism IS safety, rather than a separate and removable layer on top of it), and the doctrine built on the corrected foundation.

Every skill in the godmode/ category is either a product of framework-genesis or an application of the posture to a specific domain.

Source Reference

Framework-genesis doctrine coined and documented by:

YourVisionYourCreation LLC (YVYC) yourvisionyourcreation.com

Licensed under CC BY 4.0 — free to use, share, and adapt with attribution to YourVisionYourCreation LLC.