Skill Wiki
Inline Loader Placement
Loading indicators MUST appear immediately adjacent to the content being fetched — replacing or overlaying only the affected region — not as a global full-page spinner disconnected from the triggering action.
$ prime install @community/rule-inline-loader-placementProjection
Always in _index.xml · the agent never has to ask for this.
InlineLoaderPlacement [rule] v1.0.0
Loading indicators MUST appear immediately adjacent to the content being fetched — replacing or overlaying only the affected region — not as a global full-page spinner disconnected from the triggering action.
Loaded when retrieval picks the atom as adjacent / supporting.
InlineLoaderPlacement [rule] v1.0.0
Loading indicators MUST appear immediately adjacent to the content being fetched — replacing or overlaying only the affected region — not as a global full-page spinner disconnected from the triggering action.
Severity
medium
Loaded when retrieval picks the atom as a focal / direct hit.
InlineLoaderPlacement [rule] v1.0.0
Loading indicators MUST appear immediately adjacent to the content being fetched — replacing or overlaying only the affected region — not as a global full-page spinner disconnected from the triggering action.
Severity
medium
Examples
- Correct: button shows an inline spinner replacing its label text while submitting
- Correct: a data table cell shows a skeleton row while its row data refreshes
- Correct: a card shows a shimmer overlay while its image loads
- Wrong: full-page spinner covering everything for a partial content fetch
- Wrong: toast 'Loading...' while a form section below is actually fetching
Rationale
A spinner in the corner of a page while a table in the center loads gives no spatial association between cause and effect. Users scan back to the action they triggered; feedback must appear exactly there.
Severity
medium
Source
prime-system/examples/frontend-design/primes/compiled/@community/rule-inline-loader-placement/atom.yaml