/**
 * The content-root policy lives in `@skaile/workspaces/core` so the flow
 * connector's resolution surfaces can reach it too — `factory-assets → cli`
 * would be a module cycle. Re-exported here because this module is the CLI's
 * documented path surface and every CLI caller imports it from here.
 *
 * @docLink cli/dev-guide#paths
 */
export { aiResourceRoots } from "@skaile/workspaces/core";
/**
 * Absolute path to the monorepo root, or `null` when the CLI is running
 * outside the skaile-dev workspace (typical for `npm i -g` installs).
 *
 * Consumers that only make sense inside the workspace (e.g.
 * `skaile serve --compile-test`) MUST check for `null` and report a
 * "monorepo-only feature" error before proceeding.
 *
 * @docLink cli/dev-guide#paths
 */
export declare const MONOREPO_ROOT: string | null;
/**
 * Default content root used by path display and the `validate` command.
 *
 * The primary first-party `factory-assets/` root resolved through the shared
 * `factoryAssetRoots()` helper — the `SKAILE_FACTORY_ASSETS_DIR` override when
 * set, else the in-repo source during dev / bundled `dist/factory-assets/` after
 * `npm i`. Falls back to `~/.skaile/libraries/` — the user-library directory
 * managed by `skaile library add` — when the package cannot be located.
 * Consumers `fs.existsSync` first and degrade to "no skills / flows discovered".
 *
 * @docLink cli/dev-guide#paths
 */
export declare const AI_RESOURCES: string;
//# sourceMappingURL=paths.d.ts.map