Who This Is For¶
This guide is for engineers and teams who want a consistent developer workflow across local machines and CI, without every repository inventing its own scripts and check logic.
Typical users:
backend teams (Rust, Node, polyglot repos)
frontend teams that need repeatable quality gates
platform teams standardizing CI workflows across projects
Mission and Objectives¶
Devflow exists to make workflow behavior predictable and shareable.
Objectives:
one canonical command surface across stacks
profile-driven quality gates (
targets.*) instead of ad hoc scriptsreproducible local and CI behavior
extension model that lets projects map canonical commands to stack tooling
Positioning¶
Devflow does not replace Makefile or justfile. It adds a consistent command contract and profile policy layer across repositories, while Make/Just can continue to execute stack-specific internals.
Why This Matters¶
Without a shared workflow contract, local and CI behavior drifts. Teams duplicate shell scripts, command names vary by project, and debugging failed CI becomes expensive.
Devflow turns this into a config-defined contract that can be executed and validated consistently.