Fluid ForgeFluid Forge
Home
Get Started
  • Local (DuckDB)
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
CLI Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
GitHub
Home
Get Started
  • Local (DuckDB)
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
CLI Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
GitHub
  • Introduction

    • /
    • Getting Started
    • Snowflake Quickstart
    • Vision & Roadmap
  • Walkthroughs

    • Walkthrough: Local Development
    • Walkthrough: Deploy to Google Cloud Platform
    • Walkthrough: Snowflake Team Collaboration
    • Declarative Airflow DAG Generation - The FLUID Way
    • Generating Orchestration Code from Contracts
    • Jenkins CI/CD for FLUID Data Products
    • Universal Pipeline
  • CLI Reference

    • CLI Reference
    • fluid init
    • fluid forge
    • fluid status
    • fluid validate
    • fluid plan
    • fluid apply
    • fluid generate
    • fluid publish
    • fluid market
    • fluid import
    • fluid policy-check
    • fluid diff
    • fluid test
    • fluid verify
    • fluid config
    • fluid split
    • fluid bundle
    • fluid auth
    • fluid doctor
    • fluid providers
    • fluid version
  • Providers

    • Providers
    • Provider Architecture
    • GCP Provider
    • AWS Provider
    • Snowflake Provider
    • Local Provider
    • Creating Custom Providers
    • Provider Roadmap
  • Advanced

    • Blueprints
    • Governance & Compliance
    • Airflow Integration
    • Built-in And Custom Forge Guidance
    • FLUID Forge Contract GPT Packet
    • Forge Discovery Guide
    • Forge Memory Guide
  • Project

    • Contributing to Fluid Forge
    • Fluid Forge Docs Baseline: CLI 0.7.9
    • Fluid Forge v0.7.1 - Multi-Provider Export Release

fluid forge

Use AI-assisted scaffolding when you want domain hints, local discovery, or project memory during project creation.

Syntax

fluid forge [OPTIONS]

Key options

Project

OptionDescription
--target-dir, -d DIRTarget directory for project creation
--provider, -p NAMEProvider hint
--domain NAMEDomain hint such as finance, healthcare, retail, or telco
--blankCreate an empty contract without LLM help
--dry-runPreview without creating files
--non-interactiveUse defaults without prompting
--context VALUEAdditional JSON context or a path to a context file

AI config

OptionDescription
--llm-provider NAMELLM provider
--llm-model NAMEModel identifier
--llm-endpoint URLOverride the model endpoint

Discovery and memory

OptionDescription
--discoverInspect local files before generation
--no-discoverSkip local discovery
--discovery-path PATHAdd extra paths to scan
--memoryLoad copilot memory
--no-memorySkip memory for this run
--save-memoryPersist memory after a successful run
--show-memoryPrint memory summary and exit
--reset-memoryDelete memory and exit

Examples

fluid forge
fluid forge --provider gcp
fluid forge --domain finance
fluid forge --llm-provider openai --llm-model gpt-4o-mini
fluid forge --blank --target-dir ./out

Notes

  • The current promoted syntax is fluid forge, not fluid forge --mode copilot.
  • Use --domain for built-in domain guidance instead of the older --mode agent flow shown in some legacy docs.
  • Discovery and memory guides live in the advanced docs: discovery and memory.

Industry skills — fluid skills

--domain gives the copilot a high-level role (finance, healthcare, retail, telco). For deeper domain knowledge — the vocabulary, typical data products, standard fact tables, regulatory constraints of an industry — install an industry skills pack. Skills live in .fluid/skills.yaml inside the project; the compiled form .fluid/skills.compiled.json is what the copilot loads at runtime.

fluid skills <action>

Subcommands

SubcommandWhat it does
fluid skills install [INDUSTRY]Install a bundled skills pack. INDUSTRY is one of telco, retail, healthcare, finance. Omit for interactive selection.
fluid skills showDisplay the current industry skills file
fluid skills compilePre-compile .fluid/skills.yaml into .fluid/skills.compiled.json for faster copilot runs
fluid skills updateRefresh the tools section of .fluid/skills.yaml to match the current CLI version

Examples

fluid skills install telco
fluid skills show
fluid skills compile
fluid skills update

Run fluid skills compile after any manual edit to skills.yaml to keep the compiled form in sync. fluid skills update is the right command after upgrading the CLI — it rewrites the tools list so the copilot sees the newest fluid_* entries.

Edit this page on GitHub
Last Updated: 4/16/26, 11:38 AM
Contributors: Jeff Watson, jeffwatson-ai
Prev
fluid init
Next
fluid status