You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a3f781b
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: AGENTS.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ Tauri-based cross-platform SQL database GUI client with Vue 3 + TypeScript front
9
9
**Before adding or changing client UI, read [DESIGN.md](DESIGN.md).** It is the canonical client design specification; feature design documents describe behavior within that system.
10
10
11
11
- Preserve SQLKit's existing **blue primary**, light/dark/system themes, compact desktop workspace, and shared shadcn-vue/Radix Vue components. Keep semantic color ownership consistent and retain SQLKit's blue brand and primary actions.
12
-
- Use neutral surfaces, typography, spacing, and borders for hierarchy. Keep accent areas scarce (roughly 10% of application chrome); use at most one solid primary action per operation context. Secondary toolbar actions stay neutral.
13
-
- Colors have fixed roles: `primary` = primary actions/interaction; `success` = actual success/connected/completed; `destructive` = errors/destructive actions. Ordinary information, counts, boolean values, database properties, and file formats are neutral. Do not assign a color to each feature or add a separate AI palette.
12
+
- Use neutral surfaces, typography, spacing, and borders for hierarchy. Keep accent areas scarce (roughly 10% of application chrome); use at most one solid primary action per operation context. Toolbar button surfaces stay neutral; small query-action and object-type icons may use the bounded recognition palette in DESIGN.md.
13
+
- Colors have fixed roles: `primary` = primary actions/interaction; `success` = actual success/connected/completed; `destructive` = errors/destructive actions. Ordinary information, counts, boolean values, database properties, and file formats are neutral. Do not tint whole features or add a separate AI palette. Object-type and query-action icon colors are recognition cues, separate from operational status.
14
14
- Reuse semantic CSS tokens from `src/assets/index.css` and their `uno.config.ts` mappings. Do not add palette classes or literal colors for existing UI semantics. `accent` is a neutral interaction surface, not a second brand color.
15
15
-`warning` is registered with light/dark foreground, muted-background, and border pairs; `info` is **not registered**. Use `primary-text` and `destructive-text` for readable colored text, reserving the corresponding base tokens for solid actions. Any new semantic token must include light/dark definitions, necessary foreground pairs, UnoCSS mappings, shared variants where needed, contrast verification, and a DESIGN.md update in the same change.
16
16
- Non-interactive badges explicitly use `outline`/`secondary` by default; status colors require real state and accompanying text or icons. Syntax highlighting, data charts, diffs, and small vendor logos have the bounded exceptions documented in DESIGN.md.
Dark mode uses the approved softly cool graphite palette. Preserve blue primary actions. Use `primary-text` for blue text and icons, and `destructive-text` for error text and icons; solid fill tokens are not readable-text tokens. `success` and `warning` are paired with dark foregrounds in dark mode and white foregrounds in light mode.
83
88
@@ -87,7 +92,7 @@ Dark mode uses the approved softly cool graphite palette. Preserve blue primary
87
92
| --- | --- | --- |
88
93
| Blue `primary / primary-text`| Primary actions, links, selected controls, small active indicators | Success, ordinary badges, large panel backgrounds |
89
94
| Neutrals `foreground / muted / secondary / accent`| Body text, supporting information, toolbars, navigation backgrounds, counts, ordinary attributes, disconnected states | Important errors or risks hidden through low contrast |
| Amber `warning`| Actual warnings, risks, exceptional states requiring attention | JSON format, primary keys, ordinary unsaved indicators, arbitrary toolbar buttons |
93
98
@@ -97,15 +102,15 @@ Use neutral icons and text for ordinary information; do not introduce a separate
97
102
98
103
1.**Start with neutrals, then add emphasis.** Most backgrounds, borders, body text, and icons in a resting workspace use existing neutral tokens. Establish hierarchy through typography, spacing, and position first.
99
104
2.**Aim for accents to occupy no more than roughly 10% of the UI.** This is a review heuristic for the app shell, toolbars, panels, and forms, not a pixel-counting requirement. Evaluate SQL syntax highlighting, actual data charts, and local error feedback separately for readability; these exceptions must not expand decorative color use.
100
-
3.**Use at most one solid primary action per operation context.**This is usually Execute in a query workspace or Save in a form dialog. Other actionsuse outline / secondary / ghost. An independent dialog may have its own primary action. Focus rings and status dots do not count as a second solid primary action.
105
+
3.**Use at most one solid primary action per operation context.**Use a solid action only when the context benefits from it, such as Save in a form dialog. Query toolbar actions, including Execute, use compact ghost buttons with colored icons and neutral hover surfaces. An independent dialog may have its own primary action. Focus rings and status dots do not count as a second solid primary action.
101
106
4.**Success, warning, and failure may coexist when backed by actual state.** Default to an icon / status dot with text, adding a local, subdued background when needed. Do not tint an entire row, card, or panel.
102
-
5.**Features do not own colors.** Do not give copy / export / format / EXPLAIN or individual filter operators a separate color. The result copy/export icons have the bounded exception below.
107
+
5.**Features do not own colors.** Do not tint feature surfaces or filter operators by category. The object-type, query-action, and result copy/export icons have bounded recognition exceptions below.
103
108
104
109
### Allowed and avoided treatments
105
110
106
111
| Context | Default treatment | Avoid |
107
112
| --- | --- | --- |
108
-
|Toolbars | Neutral icons and text; `accent` on hover |Blue / purple / orange / green buttons side by side|
113
+
|Query toolbar | Small colored action icons, ghost buttons, neutral `accent` on hover |Solid blue Execute tiles or colored button backgrounds|
109
114
| Navigation / tabs | Neutral backgrounds and font weight; small blue indicators when needed | Solid saturated blue blocks or multicolor navigation entries |
110
115
| Attribute badges | Explicitly select `outline` or `secondary` on `Badge`| Solid blue badges chosen merely because that variant is the default |
111
116
| Connection cards | Name, engine icon, status text / dot | A different colored background for each database engine |
@@ -114,6 +119,10 @@ Use neutral icons and text for ordinary information; do not introduce a separate
114
119
115
120
### Color exceptions
116
121
122
+
- The object browser uses small recognition icons: green table objects, violet views, blue procedures, amber functions, and gold database icons. Tables category nodes use a blue `table-properties` icon while individual tables use a green `table` icon. Labels, counts, chevrons, row backgrounds, and other chrome remain neutral. Materialized views retain a distinct layers glyph. These icon colors identify object types and do not indicate connection or execution state.
123
+
- The query toolbar uses green Execute, violet EXPLAIN / ANALYZE, amber Format, and blue Save icons. All use compact ghost buttons with neutral hover and pressed surfaces; Execute has no persistent solid primary background. Enabled ANALYZE also retains its pressed state and an outline. Accessible labels and distinct glyphs remain required.
124
+
- Recognition colors live in `--icon-table / view / procedure / function / database`, with light/dark definitions and `icon-*` UnoCSS mappings. Query-action mappings reuse this palette without borrowing the status token names. These are foreground-only icon roles; do not use them for button fills, panels, badges, text labels, or status feedback.
125
+
117
126
- Result copy/export icons retain their established format colors: sky blue for CSV, amber for JSON, and emerald for INSERT, including the overflow menu and light/dark variants. This is an icon-only recognition cue; buttons and menu surfaces remain neutral, and labels still identify each action. These colors do not indicate status or extend to other format controls.
118
127
- Monaco SQL syntax highlighting, code diffs, and actual data charts may use multiple colors when those colors explain content. Do not extend their palettes into application controls.
119
128
- Existing database vendor logos may retain identifying colors inside small icons. Do not extend those colors to cards, buttons, or navigation backgrounds.
@@ -298,7 +307,7 @@ Interactive components must cover default, hover, focus-visible, active / select
298
307
### Don't
299
308
300
309
- Do not assign a color to every feature, database type, filter operator, or file format.
301
-
- Do not use success green for Execute, error red for ordinary counts, or warning colors for ordinary attributes.
310
+
- Do not use success-status tokens for Execute, error red for ordinary counts, or warning colors for ordinary attributes. Execute uses its bounded recognition icon role.
302
311
- Do not replace SQLKit's blue theme, force pure-gray neutral surfaces, or switch to monochrome primary buttons to match the reference project.
303
312
- Do not add rainbow badges, gradient AI panels, large colored icon containers, or light effects without functional value.
304
313
- Do not use historical hardcoding, default Badge styling, or unimplemented tokens as the design basis for new UI.
@@ -320,7 +329,7 @@ Check each affected surface. Documentation-only changes need source, link, and i
320
329
### Theme maintenance
321
330
322
331
- Keep the CSS token source, UnoCSS mappings, Monaco adapter, and this specification synchronized.
323
-
- Shared badges default to neutral secondary. Connection and transfer status signals use semantic tokens; database attributes, booleans, filter operators, task counts, feature icons, and vendor icon containers remain neutral.
332
+
- Shared badges default to neutral secondary. Connection and transfer status signals use semantic tokens; database attributes, booleans, filter operators, task counts, and vendor icon containers remain neutral. Object-type and query-action icons retain the bounded recognition palette above.
324
333
- Theme preview tiles scope the same light/dark tokens instead of maintaining a second miniature palette.
325
334
- Automated contrast checks cover text on workspace, chrome, raised, selection, and semantic feedback surfaces, plus foregrounds on solid actions. Editor theme tests cover light/dark switching and token inheritance.
326
335
- Continue to verify real content, narrow windows, keyboard focus, system appearance changes, and native window controls on the target operating systems. Theme tests do not replace native-platform interaction checks.
0 commit comments