fixedcode
v0.2.2
Published
Spec-driven, deterministic code generation engine. Same spec → same code, every time.
Maintainers
Readme
fixedcode
The FixedCode CLI and programmatic API.
Spec-driven, deterministic code generation for the AI era. YAML in, production code out, same spec → same code every time.
Full project docs: https://github.com/gibbon/fixedcode
Install
npm install -g fixedcode
# or as a dev dep:
npm install --save-dev fixedcodeCLI
| Command | Description |
|---|---|
| fixedcode generate <spec.yaml> -o <out> | Generate code from a spec into <out>. |
| fixedcode build <specDir> -o <out> | Generate from every spec in a directory; consolidates migrations. |
| fixedcode verify <spec.yaml> <outputDir> | Verify every expected file exists. |
| fixedcode deploy <buildDir> <targetDir> | Copy generated output into a target project. |
| fixedcode validate <spec.yaml> | Validate a spec without generating. |
| fixedcode draft <kind> "<description>" -o <out.yaml> | LLM-assisted spec drafting. |
| fixedcode enrich <outputDir> | LLM-assisted extension-point fill-in. |
| fixedcode registry list \| search \| install \| publish | Discover, install, publish bundles. |
| fixedcode cfr catalog \| suggest \| check \| report | Cross-Functional Requirements tooling. |
| fixedcode bundle init <name> | Scaffold a new bundle. |
Run fixedcode <command> --help for full options.
Quickstart
# install the CLI
npm install -g fixedcode
# install a bundle (registry-hosted)
fixedcode registry install spring-domain
# generate
fixedcode generate my-domain.yaml -o build
fixedcode verify my-domain.yaml build
# (optional) deploy into an existing project
fixedcode deploy build /path/to/your/projectProgrammatic API
import {
generate,
validate,
build,
deploy,
verify,
fetchRegistry,
searchRegistry,
installPackage,
publishPackage,
renderTemplates,
} from 'fixedcode';
await generate({
specPath: './my-domain.yaml',
outputDir: './build',
});Documentation
- Architecture & contracts
- Writing a bundle
- Writing a generator
- LLM configuration
- Registry
- Cross-Functional Requirements
