Worklog Design
regisx001/Worklog
Design and UI skill for the Worklog desktop project manager.
Guidelines for writing UI code in Warp's GUI desktop client, centered on reusing shared components and themes instead of adding one-off styling.
Install Warp GUI UI Guidelines
$ npx skills add warpdotdev/warp --skill gui-ui-guidelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install warpdotdev/warp gui-ui-guidelines --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/gui-ui-guidelines .claude/skills/gui-ui-guidelines && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gui-ui-guidelines" agent skill from https://github.com/warpdotdev/warp/tree/master/.agents/skills/gui-ui-guidelines into .claude/skills/gui-ui-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gui-ui-guidelines", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/warpdotdev/warp/tree/master/.agents/skills/gui-ui-guidelinesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add warpdotdev/warp --skill gui-ui-guidelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install warpdotdev/warp gui-ui-guidelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/gui-ui-guidelines .agents/skills/gui-ui-guidelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gui-ui-guidelines" agent skill from https://github.com/warpdotdev/warp/tree/master/.agents/skills/gui-ui-guidelines into .agents/skills/gui-ui-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gui-ui-guidelines", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add warpdotdev/warp --skill gui-ui-guidelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install warpdotdev/warp gui-ui-guidelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/gui-ui-guidelines .cursor/skills/gui-ui-guidelines && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gui-ui-guidelines" agent skill from https://github.com/warpdotdev/warp/tree/master/.agents/skills/gui-ui-guidelines into .cursor/skills/gui-ui-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gui-ui-guidelines", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/warpdotdev/warp.git --path .agents/skills/gui-ui-guidelines--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add warpdotdev/warp --skill gui-ui-guidelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install warpdotdev/warp gui-ui-guidelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/gui-ui-guidelines .gemini/skills/gui-ui-guidelines && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gui-ui-guidelines" agent skill from https://github.com/warpdotdev/warp/tree/master/.agents/skills/gui-ui-guidelines into .gemini/skills/gui-ui-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gui-ui-guidelines", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install warpdotdev/warp gui-ui-guidelinesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add warpdotdev/warp --skill gui-ui-guidelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/gui-ui-guidelines .github/skills/gui-ui-guidelines && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gui-ui-guidelines" agent skill from https://github.com/warpdotdev/warp/tree/master/.agents/skills/gui-ui-guidelines into .github/skills/gui-ui-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gui-ui-guidelines", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add warpdotdev/warp --skill gui-ui-guidelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install warpdotdev/warp gui-ui-guidelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/gui-ui-guidelines .opencode/skills/gui-ui-guidelines && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gui-ui-guidelines" agent skill from https://github.com/warpdotdev/warp/tree/master/.agents/skills/gui-ui-guidelines into .opencode/skills/gui-ui-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gui-ui-guidelines", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gui-ui-guidelines- GitHub stars
- 65k
- Used in
- 1 other repo
- Token cost
- ~947 tokens
- SKILL.md length
- 495 words
- Files
- 1
- Skills in repo
- 46
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Guidelines for writing UI code in Warp's GUI desktop client, centered on reusing shared components and themes instead of adding one-off styling.
- Starting any UI change in the Warp desktop client codebase
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Styling a new button in Warp and choosing which shared theme to use
- Reviewing a Warp UI pull request for reinvented components or design-system drift
What it does
This is a growing catalog of rules for the UI code of Warp's desktop client, which is built on the WarpUI pixel and GPU framework in the `app/` crate. The agent reads the list once at the start of any UI task and keeps the relevant rules in mind while implementing. Each rule records a lesson reviewers kept having to repeat, such as reinventing a component or bypassing a shared abstraction.
The guideline visible here covers button colors: pick one of the existing shared themes, such as `PrimaryTheme`, `SecondaryTheme`, `NakedTheme` or `DangerPrimaryTheme`, and use it unchanged rather than inventing colors. The skill applies only to the GUI front-end. The headless TUI front-end has its own skills, and a separate skill covers the settings modal.
When your agent uses it
- Starting any UI change in the Warp desktop client codebase
- Styling a new button in Warp and choosing which shared theme to use
- Reviewing a Warp UI pull request for reinvented components or design-system drift
Example prompts
- “Add a Retry button to the update banner in the Warp client, following the UI guidelines.”
- “Check my new dialog against Warp's GUI guidelines before I open the PR.”
- “Which button theme should a destructive Delete action use in the Warp app UI.”
Requirements
- A checkout of the Warp repository
What it can do on your machine
Read from SKILL.md and the folder at commit f571865. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Warp GUI UI Guidelines loads about 947 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 495 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from warpdotdev/warp at commit f571865, republished under its AGPL-3.0 licence (© warpdotdev). 495 words, ~947 tokens.
Download SKILL.mdSave it as
.claude/skills/gui-ui-guidelines/SKILL.md (or your agent's skills folder).- name
- gui-ui-guidelines
- description
- GUI desktop app only. Catalog of guidelines for writing UI code in the Warp client. Read whenever doing any UI work in this repo, up front before writing the change, so the relevant guidelines shape the implementation.
gui-ui-guidelines
Scope — GUI desktop app only. This skill applies to Warp's GUI desktop front-end (the app/ crate on the WarpUI pixel/GPU framework). It does not apply to the headless TUI front-end (crates/warp_tui; cell-grid TuiElement library under crates/warpui_core/src/elements/tui), which has its own components, tests, and change-verification workflow. For TUI work, see the tui-ui-guidelines, tui-testing, and tui-verify-change skills instead.
This skill is a growing catalog of guidelines for working on Warp's UI code. Each guideline captures a lesson that would otherwise be re-learned through review — typically because an agent or contributor reinvented a component, drifted from the design system, or bypassed a shared abstraction.
How to use this skill:
- Read through the guidelines below once at the start of any UI task, then keep them in mind while implementing. The list is short enough to scan.
- Each guideline is self-contained. Not every one will apply to every task — use judgment. But if a guideline does apply, follow it.
- When in doubt, prefer reusing an existing abstraction over introducing a new one. The Warp UI has accumulated a well-factored set of shared components and themes; new one-offs almost always drift.
For work on the settings modal (app/src/settings_view/) — a settings page, a SettingsWidget, or anything that affects settings search — also read the gui-settings-ui skill, which covers the page-title, widget-gating, and widget-splitting rules specific to that surface.
New guidelines get added here over time. If you discover a recurring UI mistake that would have been caught by a written rule, add it.
Show full SKILL.md (248 more words)Show less
Guideline: Reuse button themes
Button colors come from a shared set of ActionButtonTheme impls in app/src/view_components/action_button.rs (and the parallel Theme impls in crates/ui_components/src/button/themes.rs) — PrimaryTheme, SecondaryTheme, NakedTheme, DangerPrimaryTheme, etc. These encode the design system and keep button colors consistent across the app.
When styling a button, use one of the existing themes unchanged. The shared themes are well-established and vetted; if one looks "wrong" for your use case, the most likely explanation is that you're reaching for the wrong theme, not that the theme is buggy.
Do not modify a shared theme on your own initiative. Changing PrimaryTheme, SecondaryTheme, etc. affects every button in the app, and a tweak that fixes your screen can silently regress others. Only edit a shared theme when the user has explicitly confirmed that the design-system component itself needs to change.
Red flags that you're about to make buttons inconsistent:
- Writing a new
impl ActionButtonTheme for FooPrimaryThemethat delegates toPrimaryThemeand only tweaks one method (usuallytext_color). Almost always the right move is to usePrimaryThemedirectly and accept the result. - Hard-coding
ColorU::new(...)instead of usingappearance.theme()accessors (accent,font_color(bg),foreground, etc.). - Setting
should_opt_out_of_contrast_adjustmenttotrueto force a specific label color. - Naming a theme after a feature or view (
FooPrimaryTheme,BarSubmitTheme) rather than a design-system role.
If an existing theme genuinely doesn't fit and you think the shared theme should change, surface that to the user before editing it, rather than either editing it unilaterally or papering over it with a one-off.
© warpdotdev, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/gui-ui-guidelines of warpdotdev/warp.
Open the folder on GitHubat commit f571865
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in warpdotdev/warp, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Warp GUI UI Guidelines next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Warp GUI UI Guidelines this skillwarpdotdev/warp | 65k | 1 repos | ~947 | Automated safety check: Pass | AGPL-3.0 | |
| Worklog Designregisx001/Worklog | 258 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Beava Designbeava-dev/beava | 138 | — | ~443 | Automated safety check: Pass | Apache-2.0 | |
| Nxv Designutensils/nxv | 136 | — | ~607 | Automated safety check: Pass | MIT | |
| Standards Kitwednesday-solutions/ai-agent-skills | 170 | — | ~436 | Automated safety check: Pass | MIT | |
| Loop Execution EvaluatorIbrahim-3d/orchestrator-supaconductor | 380 | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Beava Design
beava-dev/beava
A skill your agent uses to generate well-branded interfaces and assets for beava (beava.dev, an open-source single-binary feature server for stream processing), either for production or throwaway…
Nxv Design
utensils/nxv
A skill your agent uses to generate well-branded interfaces and assets for nxv (Nix Version Index) — either for production or throwaway prototypes/mocks.
Standards Kit
wednesday-solutions/ai-agent-skills
Unified development and design standards. An agent skill from wednesday-solutions/ai-agent-skills.
Loop Execution Evaluator
Ibrahim-3d/orchestrator-supaconductor
Evaluate-Loop Step 4: EVALUATE EXECUTION. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
UI Styling
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
More from warpdotdev/warp
All 46 skills in this repoFigma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
Warp Factory Files
warpdotdev/warp
Authors and edits file-based Warp software factory definitions rooted at factory.yaml, covering agents, automations, scorers and webhooks, and validates them before a pull request.
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
Warp GUI to Agent CLI Migration
warpdotdev/warp
Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.
Figma Design System Rules Generator
warpdotdev/warp
Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.
Related
Works with
Categories
Questions about Warp GUI UI Guidelines
What does Warp GUI UI Guidelines do?
Guidelines for writing UI code in Warp's GUI desktop client, centered on reusing shared components and themes instead of adding one-off styling. This is a growing catalog of rules for the UI code of Warp's desktop client, which is built on the WarpUI pixel and GPU framework in the `app/` crate. The agent reads the list once at the start of any UI task and keeps the relevant rules in mind while implementing.
When should I use Warp GUI UI Guidelines?
Warp GUI UI Guidelines fits situations like: starting any UI change in the Warp desktop client codebase; styling a new button in Warp and choosing which shared theme to use; reviewing a Warp UI pull request for reinvented components or design-system drift.
How do I install Warp GUI UI Guidelines in Claude Code?
Run `npx skills add warpdotdev/warp --skill gui-ui-guidelines -a claude-code`. Or copy the skill folder (.agents/skills/gui-ui-guidelines in warpdotdev/warp) into .claude/skills/gui-ui-guidelines in your project. Claude Code loads it when a task matches its description.
How do I install Warp GUI UI Guidelines in Codex?
Run `npx skills add warpdotdev/warp --skill gui-ui-guidelines -a codex`. Or copy the skill folder (.agents/skills/gui-ui-guidelines in warpdotdev/warp) into .agents/skills/gui-ui-guidelines in your project. Codex loads it when a task matches its description.
Can I use Warp GUI UI Guidelines in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add warpdotdev/warp --skill gui-ui-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gui-ui-guidelines, .gemini/skills/gui-ui-guidelines, .github/skills/gui-ui-guidelines and .opencode/skills/gui-ui-guidelines in your project.
What does Warp GUI UI Guidelines need to run?
SKILL.md names no scripts, command-line tools or credentials: Warp GUI UI Guidelines is instructions for the agent only. Our summary lists: A checkout of the Warp repository.
Does Warp GUI UI Guidelines access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Warp GUI UI Guidelines safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Warp GUI UI Guidelines use?
Warp GUI UI Guidelines is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Warp GUI UI Guidelines use?
About 947 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Warp GUI UI Guidelines?
Skills that share tags, products or a category with Warp GUI UI Guidelines: Worklog Design (regisx001/Worklog, 258 stars), Beava Design (beava-dev/beava, 138 stars), Nxv Design (utensils/nxv, 136 stars) and Standards Kit (wednesday-solutions/ai-agent-skills, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Warp GUI UI Guidelines?
warpdotdev (a GitHub organization) maintains it in warpdotdev/warp, which has 65,380 GitHub stars. The repository holds 46 skills in this directory. The repository was last updated on October 7, 2026.
Source: warpdotdev/warp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.