Quick API and Quick Exec shown as two types (API, CLI) of one family of quick actions; line icons in Kronn's chrome, the user's emoji kept on a Quick Prompt (KT-1918)

Open
#613 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
react
Domain
design, frontend

Research direction

Start with the Automation list, creation chooser, detail headers, locale files, and JSX mentioned in the issue; trace how Quick API and Quick Exec are displayed and how chrome icons are chosen. Check the existing UI tests and the literal emoji check from KT-1887. Done means the two actions appear as API and CLI types of one family, existing items and forms still work, chrome uses line icons, and Quick Prompt retains its author's emoji.

Written by the indexing model from the issue text.

Description

enhancement UI

Kronn task: KT-1918 (0.15.4), part of design-system lot 6 (the remaining words), KT-1862. Source: UI audit of 2026-11-18.

Design-system lot 6 (UI audit 2026-11-18). Owner decision 2026-11-18: API and CLI are two different things, shown as two types of one family of actions. Aligns with KT-906 (Quick Prompt and skill merged) and KT-1160, KT-1465.

Today the Automation list shows four kinds of "Quick" next to workflows (Quick Prompt, Quick API, Quick Exec, skill), each with its own word and form, and emojis serve as icons in Kronn's own chrome (section headers, tier marks in the mention menu, status marks).

How:

  • Naming: one family, "Quick action" / « Action rapide », with a type shown as a badge on the row and in the detail header: API (calls a configured API) or CLI (runs a command on the host). One "New quick action" entry asks the type first, then opens the existing form of that type. Nothing changes in storage, API or MCP tool names (qa_*, qe_*).
  • Icons: Kronn's chrome uses line icons (lucide-react) only; a table maps each emoji used as an icon to its line icon. The emoji a user chose for a Quick Prompt is content: it stays, shown in a neutral tile (proposal put to the owner on 2026-11-18, applied unless he objects). No migration.
  • The literal emoji check of KT-1887 covers chrome strings in the locale files and JSX.

Done when:

  • The Automation list, the creation chooser and the detail headers present Quick API and Quick Exec as types API and CLI of one family; both forms and every existing item still work (UI tests)
  • No emoji is used as an icon in Kronn's chrome (check blocking in CI); a Quick Prompt keeps the emoji its author chose; captures shown to the owner
Dominant language
Rust
Stars
18
Forks
2
Avg merge
1d 3h
Merged PRs (30d)
48

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DocRoms/Kronn

All issues in DocRoms/Kronn

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.