# Support

Get help with the Loop Engineering field guide, resource data, patterns, contracts, and runtime starters through the public channels below.

## Best Channels

- **Resource suggestions**: use the [resource suggestion form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=resource-suggestion.yml).
- **Loop patterns**: use the [loop pattern form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=pattern-suggestion.yml) or the [community pattern discussion](https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2).
- **Corrections**: use the [annotation-correction form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=annotation-correction.yml) when a summary or source record is inaccurate, or open a pull request when the fix is clear.
- **Translations**: use the [translation proposal form](https://github.com/ChaoYue0307/awesome-loop-engineering/issues/new?template=translation.yml) and follow `TRANSLATIONS.md`.
- **Security concerns**: follow [`SECURITY.md`](SECURITY.md).

## What Maintainers Can Help With

- deciding whether a resource fits the narrow AI/coding-agent meaning of Loop Engineering;
- improving annotations, categories, and source quality;
- reviewing loop pattern contracts for trigger, intake, verification, state, budget, escalation, and exit;
- fixing broken links or replacing unstable sources.

## Where Else To Get Help

- Ask each tool's maintainer for product support.
- Use an appropriate professional channel for private consulting on proprietary loops.
- Take one-off prompt engineering questions to a prompt-focused community.
- Use domain-specific communities for software event loops, growth loops, control theory, and generic automation.