Fix Frontend Review Comments
JetBrains/kotlin-web-site
Apply pull-request review comments to the frontend of kotlinlang.org (Next.js, React, TypeScript, CSS Modules under blocks/, components/, pages/, hooks/, utils/, test/).
Build, review, or test LiteyukiBot v7's React/Vite WebUI under webui/ and its packaged static delivery in packages/webui/.
Install Liteyuki Webui Frontend
$ npx skills add LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LiteyukiStudio/LiteyukiBot liteyuki-webui-frontend --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/LiteyukiStudio/LiteyukiBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/liteyuki-webui-frontend .claude/skills/liteyuki-webui-frontend && 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 "liteyuki-webui-frontend" agent skill from https://github.com/LiteyukiStudio/LiteyukiBot/tree/main/.agents/skills/liteyuki-webui-frontend into .claude/skills/liteyuki-webui-frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "liteyuki-webui-frontend", 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/LiteyukiStudio/LiteyukiBot/tree/main/.agents/skills/liteyuki-webui-frontendType 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 LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LiteyukiStudio/LiteyukiBot liteyuki-webui-frontend --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LiteyukiStudio/LiteyukiBot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/liteyuki-webui-frontend .agents/skills/liteyuki-webui-frontend && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "liteyuki-webui-frontend" agent skill from https://github.com/LiteyukiStudio/LiteyukiBot/tree/main/.agents/skills/liteyuki-webui-frontend into .agents/skills/liteyuki-webui-frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "liteyuki-webui-frontend", 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 LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LiteyukiStudio/LiteyukiBot liteyuki-webui-frontend --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LiteyukiStudio/LiteyukiBot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/liteyuki-webui-frontend .cursor/skills/liteyuki-webui-frontend && 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 "liteyuki-webui-frontend" agent skill from https://github.com/LiteyukiStudio/LiteyukiBot/tree/main/.agents/skills/liteyuki-webui-frontend into .cursor/skills/liteyuki-webui-frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "liteyuki-webui-frontend", 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/LiteyukiStudio/LiteyukiBot.git --path .agents/skills/liteyuki-webui-frontend--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 LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LiteyukiStudio/LiteyukiBot liteyuki-webui-frontend --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LiteyukiStudio/LiteyukiBot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/liteyuki-webui-frontend .gemini/skills/liteyuki-webui-frontend && 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 "liteyuki-webui-frontend" agent skill from https://github.com/LiteyukiStudio/LiteyukiBot/tree/main/.agents/skills/liteyuki-webui-frontend into .gemini/skills/liteyuki-webui-frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "liteyuki-webui-frontend", 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 LiteyukiStudio/LiteyukiBot liteyuki-webui-frontendInstalls 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 LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LiteyukiStudio/LiteyukiBot.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/liteyuki-webui-frontend .github/skills/liteyuki-webui-frontend && 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 "liteyuki-webui-frontend" agent skill from https://github.com/LiteyukiStudio/LiteyukiBot/tree/main/.agents/skills/liteyuki-webui-frontend into .github/skills/liteyuki-webui-frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "liteyuki-webui-frontend", 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 LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LiteyukiStudio/LiteyukiBot liteyuki-webui-frontend --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LiteyukiStudio/LiteyukiBot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/liteyuki-webui-frontend .opencode/skills/liteyuki-webui-frontend && 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 "liteyuki-webui-frontend" agent skill from https://github.com/LiteyukiStudio/LiteyukiBot/tree/main/.agents/skills/liteyuki-webui-frontend into .opencode/skills/liteyuki-webui-frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "liteyuki-webui-frontend", 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
liteyuki-webui-frontend- GitHub stars
- 157
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,227 words
- Files
- 2
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Build, review, or test LiteyukiBot v7's React/Vite WebUI under webui/ and its packaged static delivery in packages/webui/.
- Works in 3 steps: Read the changed view, its API model in… → Check git status -sb. Create a focused… → Treat a screenshot as evidence of the…
- Shared components
- SKILL.md covers Scope, Before Editing, Product Rules and Design System, plus 4 more sections
- Calls pnpm, uv and git
What it does
Liteyuki Webui Frontend is an agent skill from LiteyukiStudio/LiteyukiBot. Build, review, or test LiteyukiBot v7's React/Vite WebUI under webui/ and its packaged static delivery in packages/webui/. Use for UI/UX, shared components, WebUI API views, Vite development, static staging, Playwright visual checks, and WebUI pull requests.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Frontend & Design, covering Browser testing, Pull requests and UI design. It works with Playwright, Vite and React. The repository describes itself as: 一个综合，All in One，轻量的机器人应用程式.
When your agent uses it
- Shared components
- WebUI API views
- Vite development
- Playwright visual checks
Example prompts
- “/liteyuki-webui-frontend”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read the changed view, its API model in webui/src/models/, the matching
- Check git status -sb. Create a focused branch for a functional or visual
- Treat a screenshot as evidence of the running asset set. Compare its visible
What it can do on your machine
Read from SKILL.md and the folder at commit 2ccd25a. 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
Shell commands in SKILL.md call:
pnpmuvgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, uv and git, which can reach the network depending on how they are called.
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
Liteyuki Webui Frontend loads about 2.5k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 1,227 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,227 words (~2,482 tokens).
“shadcn primitives, Playwright tests, and the development launcher.”
- name
- liteyuki-webui-frontend
Files
SKILL.md and 1 other file in .agents/skills/liteyuki-webui-frontend of LiteyukiStudio/LiteyukiBot.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 2ccd25a
Compare with similar skills
Liteyuki Webui Frontend 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 |
|---|---|---|---|---|---|---|
| Liteyuki Webui Frontend this skillLiteyukiStudio/LiteyukiBot | 157 | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Fix Frontend Review CommentsJetBrains/kotlin-web-site | 1.6k | — | ~444 | Automated safety check: Pass | Apache-2.0 | |
| Reactmagnus919/agent-skills | 115 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Playwright Component Testingmellowagain/gitarena | 115 | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Code Reviewnteract/semiotic | 2.7k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Nextjsericrisco/rsc-harness | 180 | — | ~5.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
React
magnus919/agent-skills
Operate React applications as a named tool: inspect and diagnose React/Vite projects, design component boundaries and state flow, implement accessible responsive UI, and verify behavior with the…
Playwright Component Testing
mellowagain/gitarena
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime.
Code Review
nteract/semiotic
Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence.
Nextjs
ericrisco/rsc-harness
A skill your agent uses when building, reviewing, testing, securing, or optimizing a Next.js App Router app: Server vs Client boundaries, use server actions, route handlers, the v15 vs v16 use cache…
Vite
magnus919/agent-skills
Operate Vite projects: inspect versions and configuration, run bounded development and production builds, diagnose dependency and asset failures, and configure environment-aware frontend delivery.
More from LiteyukiStudio/LiteyukiBot
Benchmark Tests
LiteyukiStudio/LiteyukiBot
Maintain LiteyukiBot v7 performance benchmarks and their deterministic tests.
Liteyuki Backend
LiteyukiStudio/LiteyukiBot
Build, review, refactor, or release LiteyukiBot v7 backend code and first-party Python packages.
Related
Works with
Categories
Questions about Liteyuki Webui Frontend
What does Liteyuki Webui Frontend do?
Build, review, or test LiteyukiBot v7's React/Vite WebUI under webui/ and its packaged static delivery in packages/webui/. Liteyuki Webui Frontend is an agent skill from LiteyukiStudio/LiteyukiBot. Build, review, or test LiteyukiBot v7's React/Vite WebUI under webui/ and its packaged static delivery in packages/webui/.
When should I use Liteyuki Webui Frontend?
Liteyuki Webui Frontend fits situations like: shared components; webUI API views; vite development; playwright visual checks.
How do I install Liteyuki Webui Frontend in Claude Code?
Run `npx skills add LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a claude-code`. Or copy the skill folder (.agents/skills/liteyuki-webui-frontend in LiteyukiStudio/LiteyukiBot) into .claude/skills/liteyuki-webui-frontend in your project. Claude Code loads it when a task matches its description.
How do I install Liteyuki Webui Frontend in Codex?
Run `npx skills add LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a codex`. Or copy the skill folder (.agents/skills/liteyuki-webui-frontend in LiteyukiStudio/LiteyukiBot) into .agents/skills/liteyuki-webui-frontend in your project. Codex loads it when a task matches its description.
Can I use Liteyuki Webui Frontend 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 LiteyukiStudio/LiteyukiBot --skill liteyuki-webui-frontend -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/liteyuki-webui-frontend, .gemini/skills/liteyuki-webui-frontend, .github/skills/liteyuki-webui-frontend and .opencode/skills/liteyuki-webui-frontend in your project.
What does Liteyuki Webui Frontend need to run?
Going by SKILL.md and its folder, Liteyuki Webui Frontend needs the command-line tools its instructions call (pnpm, uv and git). Our summary lists: Python 3.
Does Liteyuki Webui Frontend access the network?
SKILL.md contains no URLs. Its commands use uv and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Liteyuki Webui Frontend 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 Liteyuki Webui Frontend use?
Liteyuki Webui Frontend has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Liteyuki Webui Frontend use?
About 2.5k tokens (SKILL.md is roughly 9.9k 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 Liteyuki Webui Frontend?
Skills that share tags, products or a category with Liteyuki Webui Frontend: Fix Frontend Review Comments (JetBrains/kotlin-web-site, 1.6k stars), React (magnus919/agent-skills, 115 stars), Playwright Component Testing (mellowagain/gitarena, 115 stars) and Code Review (nteract/semiotic, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Liteyuki Webui Frontend?
LiteyukiStudio (a GitHub organization) maintains it in LiteyukiStudio/LiteyukiBot, which has 157 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 2, 2026.
Source: LiteyukiStudio/LiteyukiBot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.