No Divergent Platform Flows
Entirely different task flows for the same user goal on different platforms are prohibited unless the platform constraints that necessitate the divergence are explicitly documented and justified.
$ aoe install @community/rule-no-divergent-platform-flowsProjection
Always in _index.xml · the agent never has to ask for this.
NoDivergentPlatformFlows [rule] v1.0.0
Entirely different task flows for the same user goal on different platforms are prohibited unless the platform constraints that necessitate the divergence are explicitly documented and justified.
Loaded when retrieval picks the atom as adjacent / supporting.
NoDivergentPlatformFlows [rule] v1.0.0
Entirely different task flows for the same user goal on different platforms are prohibited unless the platform constraints that necessitate the divergence are explicitly documented and justified.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
warning
Distinction
This rule targets FLOW divergence (different steps, different decision points, different outcomes) — not LAYOUT divergence (responsive design adapting the same flow to a narrower screen is expected and correct).
Process
- Document every platform flow divergence in a decision record: what diverges, on which platform, and why.
- Review the divergence at each design review to confirm the platform constraint still holds.
- If a constraint is removed (e.g. Apple relaxes IAP rules), resolve the divergence.
Loaded when retrieval picks the atom as a focal / direct hit.
NoDivergentPlatformFlows [rule] v1.0.0
Entirely different task flows for the same user goal on different platforms are prohibited unless the platform constraints that necessitate the divergence are explicitly documented and justified.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
warning
Distinction
This rule targets FLOW divergence (different steps, different decision points, different outcomes) — not LAYOUT divergence (responsive design adapting the same flow to a narrower screen is expected and correct).
Process
- Document every platform flow divergence in a decision record: what diverges, on which platform, and why.
- Review the divergence at each design review to confirm the platform constraint still holds.
- If a constraint is removed (e.g. Apple relaxes IAP rules), resolve the divergence.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
warning
Distinction
This rule targets FLOW divergence (different steps, different decision points, different outcomes) — not LAYOUT divergence (responsive design adapting the same flow to a narrower screen is expected and correct).
Process
- Document every platform flow divergence in a decision record: what diverges, on which platform, and why.
- Review the divergence at each design review to confirm the platform constraint still holds.
- If a constraint is removed (e.g. Apple relaxes IAP rules), resolve the divergence.
Source
aoe-engine/examples/frontend-design/primes/compiled/@community/rule-no-divergent-platform-flows/atom.yaml