Slash Command

/tool-build

Build a lab tool or software pipeline — real-time systems, data acquisition, LSL integrations, custom analysis pipelines, or other technical infrastructure.

From neuroflow

Install

Run in your terminal

npx claudepluginhub stanislavjiricek/neuroflow --plugin neuroflow

Command Content

Stats

Stars2

Forks0

Last CommitMar 15, 2026

Actions

View Source View Plugin View on GitHub View README

What this command does

Helps the user design and build a lab tool or software pipeline. No research question driving it — the output is working code and documentation.

Ask:

What kind of tool? (real-time EEG feedback, data acquisition pipeline, BCI system, LSL integration, paradigm, preprocessing pipeline, other)

What hardware or software does it interface with? (amplifier, eye tracker including Pupil Labs Neon, PsychoPy, BrainFlow, LSL, MNE, other)

What programming language?

Standalone or integrates with an existing setup?

What is the definition of "done" — what must the tool do to be considered working?

Steps

Write a tool-spec.md — what the tool does, inputs/outputs, hardware requirements, constraints

Plan the implementation: architecture, key modules, data flow

Build the tool iteratively — write code, test, refine

Apply domain best practices for the tech stack involved (LSL, PsychoPy, BrainFlow, MNE, etc.)

Save specs and notes (tool-spec.md, code plan) in .neuroflow/tool-build/. Write the actual tool code to output_path (from .neuroflow/tool-build/flow.md, default: tools/) — not inside .neuroflow/.

/tool-build

Read the neuroflow:phase-tool-build skill first. Then follow the neuroflow-core lifecycle: read project_config.md, flow.md, and .neuroflow/tool-build/flow.md before starting.

What this command does

Helps the user design and build a lab tool or software pipeline. No research question driving it — the output is working code and documentation.

Ask:

What kind of tool? (real-time EEG feedback, data acquisition pipeline, BCI system, LSL integration, paradigm, preprocessing pipeline, other)
What hardware or software does it interface with? (amplifier, eye tracker including Pupil Labs Neon, PsychoPy, BrainFlow, LSL, MNE, other)
What programming language?
Standalone or integrates with an existing setup?
What is the definition of "done" — what must the tool do to be considered working?

Steps

Write a tool-spec.md — what the tool does, inputs/outputs, hardware requirements, constraints
Plan the implementation: architecture, key modules, data flow
Build the tool iteratively — write code, test, refine
Apply domain best practices for the tech stack involved (LSL, PsychoPy, BrainFlow, MNE, etc.)

At end

Update .neuroflow/tool-build/flow.md
Append to .neuroflow/sessions/YYYY-MM-DD.md
Update project_config.md if phase changed