Carlos Florêncio
2.0 KiB
2.0 KiB
status, initiative, requirements, system_design
| status | initiative | requirements | system_design | ||
|---|---|---|---|---|---|
| pending | prompt-alias-rendering |
|
|
Prompt alias rendering
Overview
Make recognized saved-prompt @name aliases render consistently as prompt chips
in the transcript, the desktop anchored last-prompt bar, and desktop/mobile
Prompt history without changing prompt delivery or persistence.
Delivery order
- Extract the existing transcript prompt-chip renderer into a reusable UI module, keeping the existing matcher and entity-reference composition intact.
- Wire the anchored last-prompt bar and Prompt history rows to that shared renderer.
- Add focused component tests for recognized and unknown aliases in both surfaces, then extend the existing chat/pinned/history E2E coverage with one end-to-end alias assertion where the seeded prompt is visible.
The work is one vertical frontend slice with no dependency on backend changes.
Work orders
Verification strategy
- Focused Vitest coverage for the shared renderer,
ChatMessage,AnchoredLastPromptBar, andPromptHistoryPanelContent. - Existing prompt alias and last-prompt Playwright flows, extended to assert the chip in the pinned and history surfaces.
- Frontend typecheck and lint after the targeted tests pass.
Risks and exclusions
The proposed task-create chip package extends the shared renderer to task authoring. Its work orders own that change and its verification. This package retains its existing statuses and scope.
- Prompt history currently uses a single-line text projection; the fix must not replace that layout with a second Markdown layout or break overflow detection.
- Pinned content has no message metadata, so it reuses alias rendering but does not gain entity-reference chips.
- No changes to alias parsing, backend expansion, prompt persistence, or raw message rendering.