gf-project

GF Project — Project Context Management

Project File Location

.gateflow/project.yaml in the project root.

Schema

name: my-project
top_module: top
hdl: systemverilog  # systemverilog | verilog | vhdl
target:
  board: null       # arty-a7-35t, icebreaker, etc.
  device: null      # xc7a35ticsg324-1L, ice40hx8k, etc.
  clock_freq: null  # 100MHz, 12MHz, etc.
sources: []         # auto-populated by gf-scan
constraints: null   # path to constraint file
ip_blocks: []       # installed IP block names

Auto-Detection

When this skill is invoked, it:

1. Checks if .gateflow/project.yaml exists
2. If not, creates it with defaults by scanning:
   • HDL: check file extensions in project (.sv = systemverilog, .v = verilog, .vhd = vhdl)
   • Sources: glob for **/*.sv, **/*.v, **/*.vhd
   • Top module: find modules not instantiated by others
3. If board is not set and user mentions a board, update it

Usage by Other Skills

Any skill that needs project context should:

cat .gateflow/project.yaml 2>/dev/null

If the file doesn't exist, invoke this skill to create it.

Board Memory

When a user mentions a board name in natural language (e.g., "I'm using an Arty A7"), persist it to .gateflow/project.yaml under target.board. Do not ask again unless the user switches boards or starts a new project.

Board memory is per-project, not global. Different projects target different boards.