eclipse-store-claude

Guide Claude on using Eclipse Store's JCache (JSR-107) provider — standalone caches, caches backed by an `EmbeddedStorageManager`, expiry and eviction policies, entry listeners, read-through / write-through with `CacheLoader` / `CacheWriter`, properties-file configuration, and integrations with Hibernate second-level cache and Spring's cache abstraction. **Apply this skill whenever a service / repository / facade method has an expensive read** (database query, HTTP call, cross-aggregate computation), whenever a Spring `@Service` is being designed and `@Cacheable` may apply, whenever a Hibernate model is being designed and a second-level cache is on the table, or whenever a read-heavy aggregate is being reviewed for performance. The decisions taken here — *which* operation to memoize, *what* TTL, persistent vs. ephemeral entries, cache-aside vs. read-through, where the cache lives in the bean graph — ossify in the service-layer signature the moment it is committed; retrofitting them later means changing every caller. Load this skill *before* a `@Cacheable` annotation or `JCacheManagerCustomizer` bean is added. Also use this skill when the user asks to "use JCache", "JSR-107", "Hibernate second-level cache", "@Cacheable", "JCacheManagerCustomizer", "CachingProvider", "CacheConfiguration.Builder", "CacheConfiguration.load", "eclipsestore-cache.properties", "storeByValue", "ModifiedExpiryPolicy", "AccessedExpiryPolicy", "EvictionManager.Interval", "EvictionPolicy.LeastRecentlyUsed", "CacheLoader", "CacheWriter", "read-through", "write-through", "cache-aside", "JMX cache stats", or "spring.jpa.properties.hibernate.cache.eclipsestore".

Guide Claude on safe concurrent access to Eclipse Store object graphs — the "mutate + store under the same lock" rule, what is and isn't thread-safe (`EmbeddedStorageManager`, channels, `Storer`, `GigaMap`, `Lazy<T>`, JCache, `Serializer`), and which strategy to use (`XThreads.executeSynchronized`, `ReentrantReadWriteLock`, `LockedExecutor`, `LockScope`, `StripeLockedExecutor`, `StripeLockScope`, Spring `@Read` / `@Write` / `@Mutex`). **Apply this skill whenever an Eclipse Store object model, root aggregate, or service / repository / facade layer is being designed, reviewed, or extended** — not only when the user explicitly mentions "lock" or "synchronized". In Eclipse Store the application owns thread-safety because the library is not in the read/write path, so locking decisions are part of the data model and service-layer design itself: where the locks live, which methods are read vs. write, where `store()` is called, whether to use `LockScope` / `StripeLockedExecutor` / Spring `@Read`/`@Write`/`@Mutex`. If you are sketching entities, root containers, repositories, or any API that mutates persistent state, load this skill before proposing a structure. Also use this skill when the user asks to "handle concurrent access", "make this thread-safe", "synchronize storing", "lock around store()", "ConcurrentModificationException during serialize", "share a Storer across threads", "what's thread-safe in Eclipse Store", "GigaMap concurrency", "gigaMap.store vs storageManager.store", "iterators leaking read locks", "stress-test concurrent writes", or asks why a multi-threaded app is producing inconsistent state on disk.

Guide Claude on configuring an Eclipse Store embedded storage — directories, channel count, backup, deletion, housekeeping intervals/budgets, file size thresholds, read-only mode, and external configuration loading from INI/XML/YAML/JSON/HOCON. Use this skill when the user asks to "configure storage", "set the storage directory", "use INI config", "load config from XML", "change channel count", "backup directory", "deletion directory", "truncation directory", "housekeeping budget", "data file minimum size", "read-only storage", "EmbeddedStorageConfiguration", "storage-embedded- configuration", "ConfigurationLoader", "StorageChannelCountProvider", "StorageFileProvider", or needs help sizing channels/budgets or picking a config file format.

Guide Claude on writing and registering custom binary type handlers for Eclipse Store / Eclipse Serializer — `CustomBinaryHandler<T>` for current-shape types, `BinaryLegacyTypeHandler.AbstractCustom<T>` for legacy reads, the `Binary` API for reading/writing fields at byte offsets. Use this skill when the user asks to "write a custom type handler", "serialize third-party type", "control binary layout", "CustomBinaryHandler", "BinaryHandler", "registerCustomTypeHandler", "XMemory", "PersistenceStoreHandler", "PersistenceLoadHandler", or needs to serialize a class Eclipse Store does not natively support (e.g., native handles, opaque third-party objects, types with computed fields).

Guide Claude on initializing, starting, and shutting down an Eclipse Store embedded database. This skill should be used when the user asks to "start EmbeddedStorage", "initialize StorageManager", "set up Eclipse Store", "bootstrap a database", "create an Eclipse Store application", "use EmbeddedStorageFoundation", "shut down storage", "add the storage-embedded dependency", or needs help with the storage lifecycle, Maven/Gradle coordinates, the difference between `EmbeddedStorage.start()` and the Foundation builder, or running multiple databases in one JVM.