Skip to main content

​
Libraries

Under App Blueprint → Libraries, GenieForge stores shared helpers that several tools can reuse (formatting, validation, common calculations). You describe the outcome; GenieForge extracts shared helpers when reuse matters. Libraries live in the app blueprint and travel with export and import.

​
Where it lives

App Blueprint → Libraries. Libraries are blueprint recipe, not project customer data.

​
How to verify

  1. Find it under App Blueprint → Libraries.
  2. Open a library to see Used by: each tool that imports it, plus the helper names that tool uses. The tool page lists the same names under Libraries.
  3. Change a shared helper carefully; it affects every tool that uses it.
  4. Preview as (or run) each dependent flow that should still work.
  5. Check Executions if a dependent tool ran as a background job.
  6. Keep a version before large library refactors.

​
Limits and notes

  • GenieForge keeps shared helpers focused when it extracts them; you do not need to design the library layout yourself.
  • Export/import includes libraries with the blueprint; project rows and secrets do not ride along as live values.
  • Libraries can carry a deterministic test suite. Open the library page, then the Tests tab, to see the suite source, last run, and run history. Suites never write live project data. See Tests.