flowerpower
Create and manage data pipelines using the FlowerPower framework with Hamilton DAGs and uv. Use when users request creating flowerpower projects, pipelines, Hamilton dataflows, or ask about flowerpower configuration, execution, or CLI commands.
What this skill does
# FlowerPower Pipeline Skill
Create and manage data processing pipelines using FlowerPower with Hamilton DAGs.
## Quick Start
```bash
# Install flowerpower
uv pip install flowerpower
# Initialize project
flowerpower init --name my-project
# Create pipeline
flowerpower pipeline new my_pipeline
# Run pipeline
flowerpower pipeline run my_pipeline
```
## Project Initialization
Use `scripts/init_project.py` or CLI:
```bash
# CLI
flowerpower init --name <project-name>
# Python
from flowerpower import FlowerPowerProject
project = FlowerPowerProject.init(name='my-project')
```
Creates structure:
```
my-project/
├── conf/
│ ├── project.yml
│ └── pipelines/
├── pipelines/
└── hooks/
```
## Creating Pipelines
Use `scripts/create_pipeline.py` or CLI:
```bash
flowerpower pipeline new <name>
```
Creates:
- `pipelines/<name>.py` - Hamilton functions
- `conf/pipelines/<name>.yml` - Configuration
### Pipeline Module Template
```python
from hamilton.function_modifiers import parameterize
from pathlib import Path
from flowerpower.cfg import Config
PARAMS = Config.load(
Path(__file__).parents[1], pipeline_name="my_pipeline"
).pipeline.h_params
@parameterize(**PARAMS.input_config)
def load_data(source: str) -> dict:
"""Load data from source."""
return {"source": source}
def process_data(load_data: dict) -> dict:
"""Process loaded data."""
return {"processed": load_data}
def final_result(process_data: dict) -> str:
"""Return final result."""
return str(process_data)
```
### Pipeline Config Template
```yaml
params:
input_config:
source: "data.csv"
run:
final_vars:
- final_result
executor:
type: threadpool
max_workers: 4
retry:
max_retries: 3
retry_delay: 1.0
```
## Running Pipelines
```bash
# Basic run
flowerpower pipeline run my_pipeline
# With inputs
flowerpower pipeline run my_pipeline --inputs '{"key": "value"}'
# With executor
flowerpower pipeline run my_pipeline --executor threadpool --executor-max-workers 8
# With retries
flowerpower pipeline run my_pipeline --max-retries 3 --retry-delay 2.0
```
Python API:
```python
from flowerpower import FlowerPowerProject
project = FlowerPowerProject.load('.')
result = project.run('my_pipeline')
# With RunConfig
from flowerpower.cfg.pipeline.run import RunConfig
config = RunConfig(inputs={"key": "value"}, final_vars=["output"])
result = project.run('my_pipeline', run_config=config)
```
## CLI Commands
| Command | Description |
|---------|-------------|
| `flowerpower init --name <name>` | Initialize project |
| `flowerpower pipeline new <name>` | Create pipeline |
| `flowerpower pipeline run <name>` | Run pipeline |
| `flowerpower pipeline show-pipelines` | List pipelines |
| `flowerpower pipeline show-dag <name>` | Visualize DAG |
| `flowerpower pipeline delete <name>` | Delete pipeline |
## Executor Types
| Type | Use Case | Config |
|------|----------|--------|
| `synchronous` | Default, sequential | - |
| `threadpool` | I/O-bound tasks | `max_workers: N` |
| `processpool` | CPU-bound tasks | `max_workers: N` |
| `ray` | Distributed computing | `num_cpus: N` |
| `dask` | Distributed computing | `num_cpus: N` |
## Optional Dependencies
```bash
uv pip install flowerpower[io] # I/O plugins
uv pip install flowerpower[ui] # Hamilton UI
uv pip install flowerpower[all] # All extras
```
## Resources
- **references/overview.md** - Key concepts, architecture, project structure
- **references/configuration.md** - Complete YAML configuration patterns
- **references/hamilton-patterns.md** - Hamilton function decorators and patterns
## Scripts
- **scripts/init_project.py** - Initialize new flowerpower project
- **scripts/create_pipeline.py** - Create new pipeline with template
- **scripts/run_pipeline.py** - Execute pipeline with options
- **scripts/list_pipelines.py** - List available pipelines
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.