root-and-object-graph

Design root objects for Eclipse Store persistent object graphs.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/cyrock-ai/eclipse-store-skills --skill root-and-object-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: root-and-object-graph
Source: https://github.com/cyrock-ai/eclipse-store-skills/tree/main/skills/root-and-object-graph
Command: npx skills add https://github.com/cyrock-ai/eclipse-store-skills --skill root-and-object-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps users effectively design and utilize the root instance of an Eclipse Store database, ensuring a clear structure for persistent object graphs.

Core Features & Use Cases

  • Establishing the root structure: Guides on choosing between default and custom roots for various application architectures.
  • Designing top-level object models: Assists in defining the main entry point object to facilitate maintainability and performance.
  • Use Case: When creating a new application, use this Skill to determine how to set up the root container for your persistent data, such as a AppRoot class with collections and constants.

Quick Start

Use the root-and-object-graph skill to decide how to structure the persistent root object in your Eclipse Store database.

Frequently Asked Questions about root-and-object-graph

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

FAQPage Schema
How do I design the root object for an Eclipse Store database?

To design the root object for an Eclipse Store database, establish a main entry point class like AppRoot containing necessary collections and constants to ensure maintainability and efficient persistent data access.

What is a persistent root in an object graph?

A persistent root in an object graph is the single entry point object for an Eclipse Store database, serving as the starting reference for navigating and managing all persistent application data.

When should I use a custom root instead of a default root in Eclipse Store?

You should use a custom root in Eclipse Store instead of a default root when your application architecture requires a specific top-level object model to manage complex collections and domain constants efficiently.

How do I structure top-level objects for maintainable application architecture?

To structure top-level objects for maintainable application architecture, define a primary root container that aggregates core collections and constants, establishing a clear, navigable hierarchy for your persistent object graph.

Does Eclipse Store require a single root instance for persistent data?

Eclipse Store uses a single root instance as the entry point for persistent data to guarantee a structured object graph, though you can design this root using either default or custom implementation strategies.