Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

domain-content-data-pipeline

Estrelas2

Forks0

Atualizado22 de fevereiro de 2026 às 21:02

Secondary domain skill for content ingestion, import settings, resources, serialization, and runtime data loading/saving.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

DubDev720

DubDev720/gdref

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	domain-content-data-pipeline
description	Secondary domain skill for content ingestion, import settings, resources, serialization, and runtime data loading/saving.
tier	secondary
godot_version	4.6+
doc_anchors	["godot-docs/tutorials/assets_pipeline/index.rst","godot-docs/tutorials/io/index.rst","godot-docs/classes/class_resource.rst"]
tags	["content","data","pipeline"]
depends_on	["godot-skills/godot-foundations/foundation-asset-resource-pipeline/SKILL.md"]

Domain: Content Data Pipeline

Use When

Scoping content ingestion, resource ownership, and serialized data flows.
Choosing domain focus before asset/import/IO system implementation.

Outcomes

Content pipeline boundaries are clear before Tier 3 contracts are selected.
Resource/data lifecycle concerns are captured early.
Data compatibility and migration risk are visible.

Required Rules

Keep this tier domain-level; defer API specifics to Tier 3.
Separate import governance from runtime mutation responsibilities.
Include schema compatibility concerns for persisted content.
Route to tertiary contracts when concrete file formats or classes are needed.

Workflow

Identify affected content classes and data lifecycles.
Select this domain when import/resource/serialization concerns dominate.
Note constraints (determinism, migration, memory/streaming).
Route to Tier 3 contracts for concrete system behaviors.
Pair with operational validation workflows for delivery.

Validation

Domain selection rationale explains all content/data risks in scope.
Follow-on Tier 3 choices trace back to listed domain constraints.
No game-specific mechanics are embedded in domain notes.

Failure Modes

Domain notes include class/API specifics and leak into Tier 3.
Import and runtime ownership are conflated.
Migration/schema concerns are ignored until late implementation.

Local Doc Anchors

godot-docs/tutorials/assets_pipeline/index.rst
godot-docs/tutorials/io/index.rst
godot-docs/classes/class_resource.rst

Mais deste repositório

mesmo repositório

foundation-architecture

DubDev720/gdref

Foundational architecture skill for Godot workflows. Defines authority boundaries, composition strategy, scene ownership, command pathways, and replaceability constraints.

2026-02-222

foundation-asset-resource-pipeline

DubDev720/gdref

Foundation rules for deterministic asset import, resource ownership, and reproducible content pipeline behavior.

2026-02-222

foundation-data-interfaces

DubDev720/gdref

Foundational skill for data contracts, resources, interface boundaries, command/result schemas, and deterministic ordering.

2026-02-222

foundation-editor-workflow

DubDev720/gdref

Foundational skill for Godot editor-facing workflows: plugin entry points, menu/settings registration lifecycle, editor UX consistency, and teardown cleanliness.

2026-02-222

foundation-gdscript-system-design

DubDev720/gdref

Tier 1 foundation for game-agnostic GDScript system design: ownership boundaries, signal contracts, composition, and resource-backed configuration.

2026-02-222

foundation-godot-version-doc-alignment

DubDev720/gdref

Tier 1 foundation for strict Godot version/documentation alignment using local pinned docs as source of truth and explicit churn checkpoints.

2026-02-222

name	domain-content-data-pipeline
description	Secondary domain skill for content ingestion, import settings, resources, serialization, and runtime data loading/saving.
tier	secondary
godot_version	4.6+
doc_anchors	["godot-docs/tutorials/assets_pipeline/index.rst","godot-docs/tutorials/io/index.rst","godot-docs/classes/class_resource.rst"]
tags	["content","data","pipeline"]
depends_on	["godot-skills/godot-foundations/foundation-asset-resource-pipeline/SKILL.md"]

Domain: Content Data Pipeline

Use When

Scoping content ingestion, resource ownership, and serialized data flows.
Choosing domain focus before asset/import/IO system implementation.

Outcomes

Content pipeline boundaries are clear before Tier 3 contracts are selected.
Resource/data lifecycle concerns are captured early.
Data compatibility and migration risk are visible.

Required Rules

Keep this tier domain-level; defer API specifics to Tier 3.
Separate import governance from runtime mutation responsibilities.
Include schema compatibility concerns for persisted content.
Route to tertiary contracts when concrete file formats or classes are needed.

Workflow

Identify affected content classes and data lifecycles.
Select this domain when import/resource/serialization concerns dominate.
Note constraints (determinism, migration, memory/streaming).
Route to Tier 3 contracts for concrete system behaviors.
Pair with operational validation workflows for delivery.

Validation

Domain selection rationale explains all content/data risks in scope.
Follow-on Tier 3 choices trace back to listed domain constraints.
No game-specific mechanics are embedded in domain notes.

Failure Modes

Domain notes include class/API specifics and leak into Tier 3.
Import and runtime ownership are conflated.
Migration/schema concerns are ignored until late implementation.

Local Doc Anchors

godot-docs/tutorials/assets_pipeline/index.rst
godot-docs/tutorials/io/index.rst
godot-docs/classes/class_resource.rst