| title | DevForge CLI Docs |
|---|
DevForge CLI turns project intent into a runnable JavaScript or TypeScript repository with architecture guidance, testing setup, starter surfaces, AI rules, and baseline repository hygiene already in place.
- to avoid rebuilding the same repo setup on every new project
- to catch incompatible stack decisions before code is generated
- to start with docs, starter screens, API metadata, and contributor files on day one
- to standardize AI tooling and rules across projects
- to keep scaffolding quality high through generated runtime verification
- ESLint and Prettier are baseline defaults because most teams want immediate quality and formatting consistency.
- Husky and Commitlint are optional because local git-hook enforcement varies by team and workflow.
- Testing, AI rules, backend capabilities, frontend libraries, and DevOps extras can all stay on recommended defaults or be customized only when needed.
npx --yes @ali-dev11/devforge@latest: run DevForge without a global install.Project prompts: use the Prompt Reference when you want to know what a question changes before answering it.npm run check: validate the DevForge repository itself before pushing changes.npm run smoke: verify a non-interactive scaffold path.npm run runtime:matrix -- --scenario ...: validate generated installs, builds, and runtime behavior for representative stacks.npm run docs:changelog: refresh the GitHub Pages changelog page from the main changelog file.