How do I install the New Store skill?

Run npx skillmds@latest add ff4j/new-store in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is New Store safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with New Store?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is New Store free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published New Store?

ff4j (@ff4j) published this skill. Their other Agent Skills are listed on their SkillMD profile.

New Store by ff4j — Agent Skill

Name: New Store
Author: ff4j

New Store

Scaffold a new ff4j store backend module (FeatureStore/PropertyStore/EventRepository implementation) wired into the Maven reactor and validated against the shared ff4j-test TCK. Use when adding support for a new database or backend.

ff4j 1389cc5 2.0 KB Updated Sep 17, 2026

File contents

Add a new store module ff4j-store-<backend> to the ff4j reactor. Follow an existing similar module as the template — pick the closest match by protocol (e.g. ff4j-store-redis for key/value, ff4j-store-mongodb for document, ff4j-store-springjdbc for SQL).

Module setup
- Create ff4j-store-<backend>/pom.xml with parent org.ff4j:ff4j-parent and add the module to the <modules> list in the root pom.xml.
- Add the client dependency version as a version.<backend> property in the root pom. Watch out for dependencyConvergence (enforcer fails on transitive conflicts).
Implementation (in src/main/java/org/ff4j/store/ and/or org/ff4j/<backend>/)
- FeatureStore implementation extending AbstractFeatureStore (from ff4j-core).
- Optionally PropertyStore (extend AbstractPropertyStore) and EventRepository (extend AbstractEventRepository) if the backend supports them.
- Follow the mapper/driver separation used by the template module.
Tests — extend the shared TCK from ff4j-test, don't write feature-store tests from scratch:
- Unit-testable logic → *Test.java (JUnit 4, runs in the unit-test execution).
- Store tests needing the real backend → *IT.java classes extending FeatureStoreTestSupport / PropertyStoreTestSupport / AbstractEventRepositoryTest, using Testcontainers to start the backend (see ff4j-store-redis tests).
- Verify with mvn install -pl ff4j-store-<backend> -am (Docker running), or -DskipITs for a compile/unit-only pass.
Finish
- The build injects Apache license headers into new files — commit that churn.
- Conventional Commit, e.g. feat: add <backend> store.

---name: new-storedescription: Scaffold a new ff4j store backend module (FeatureStore/PropertyStore/EventRepository implementation) wired into the Maven reactor and validated against the shared ff4j-test TCK. Use when adding support for a new database or backend.---Add a new store module `ff4j-store-<backend>` to the ff4j reactor. Follow an existingsimilar module as the template — pick the closest match by protocol(e.g. `ff4j-store-redis` for key/value, `ff4j-store-mongodb` for document,`ff4j-store-springjdbc` for SQL).1. **Module setup** - Create `ff4j-store-<backend>/pom.xml` with parent `org.ff4j:ff4j-parent` and add the module to the `<modules>` list in the root `pom.xml`. - Add the client dependency version as a `version.<backend>` property in the root pom. Watch out for `dependencyConvergence` (enforcer fails on transitive conflicts).2. **Implementation** (in `src/main/java/org/ff4j/store/` and/or `org/ff4j/<backend>/`) - `FeatureStore` implementation extending `AbstractFeatureStore` (from `ff4j-core`). - Optionally `PropertyStore` (extend `AbstractPropertyStore`) and `EventRepository` (extend `AbstractEventRepository`) if the backend supports them. - Follow the mapper/driver separation used by the template module.3. **Tests** — extend the shared TCK from `ff4j-test`, don't write feature-store tests from scratch: - Unit-testable logic → `*Test.java` (JUnit 4, runs in the `unit-test` execution). - Store tests needing the real backend → `*IT.java` classes extending `FeatureStoreTestSupport` / `PropertyStoreTestSupport` / `AbstractEventRepositoryTest`, using Testcontainers to start the backend (see `ff4j-store-redis` tests). - Verify with `mvn install -pl ff4j-store-<backend> -am` (Docker running), or `-DskipITs` for a compile/unit-only pass.4. **Finish** - The build injects Apache license headers into new files — commit that churn. - Conventional Commit, e.g. `feat: add <backend> store`.

Frequently asked questions