Files
AutoMetabuilder/PROMPT.md
johndoe6345789 98f60a9a86 Introduce AutoMetabuilder core components and workflow packages:
- Implement core components: CLI argument parsing, environment loading, GitHub service creation, and logging configuration.
- Add support for OpenAI client setup and model resolution.
- Develop SDLC context loader from GitHub and repository files.
- Implement workflow context and engine builders.
- Introduce major workflow packages: `game_tick_loop` and `contextual_iterative_loop`.
- Update localization files with new package descriptions and labels.
- Streamline web navigation by loading items from a dedicated JSON file.
2026-01-10 12:02:16 +00:00

2.0 KiB

Always build and test. Maintain the full testing pyramid: unit tests, static analysis, linters, integration tests, and end-to-end coverage. Continuously execute against the roadmap.

Keep files small and focused. Target <100 LOC per file unless there is a clear and documented reason otherwise. Enforce one responsibility per file. Lockfiles are excluded from the LOC target.

Decompose aggressively. Break up large blobs of logic into composable units. Large files are a smell.

Use structured architecture. Prefer plugin / service / controller patterns with explicit dependency injection.

Favor declarative designs. Declarative workflows are strongly preferred over imperative glue code.

Everything as a workflow. If something is not part of a workflow, question whether it should be executed at all. Even complex systems (including game engines) can be expressed this way.

Eliminate repetition. Loop, parameterize, and abstract instead of copy-pasting similar code.

Externalize data. If you see a list, map, or configuration embedded in code, it likely belongs in JSON (or equivalent).

Modular configuration. If JSON files grow large, split them and reference them hierarchically.

Ship templates, not chores. Package concepts as reusable templates instead of forcing users to configure from scratch.

Logging is mandatory. Use structured logging with clear levels (DEBUG / INFO / TRACE / ERROR) throughout the system.

Declarative workflows first. Increase usage wherever possible.

Innovate continuously. Avoid stagnation; improve structure, clarity, and expressiveness over time.

Roadmap discipline. If you run out of ROADMAP.md tasks, stop and report. We should reassess priorities before inventing work.

React component logic (just above the bottom jsx) can be converted to one or more custom hooks.

Use atomic React components.

Don't hardcode strings, use a translation file or some sort of external JSON mapping.

Don't hardcode React Styling - MUI themes or SASS.