* feat(cli): add Kimi Code platform (--ai kimi)
Kimi Code discovers skills as SKILL.md folders (name + description frontmatter) in .kimi-code/skills/ (project) and ~/.kimi-code/skills/ (user). Add a kimi platform template, register the type, detect an existing .kimi-code folder, and document it in the README.
Tests: add kimi to the dry-run and script-path e2e specs. check:assets, typecheck and those specs pass; init --ai kimi was run in an empty repo. Kimi Code itself was not run.
Refs #455.
* test(cli): add kimi install and detection specs
Cover the rendered SKILL.md frontmatter, a real install into .kimi-code/skills (skill, data, scripts and sub-skills), and detection of a .kimi-code folder. Refs #455.
* fix(scripts): expect 24 platform configs in validate-agent-guide
Adding the kimi platform template raises the config count from 23 to 24. Keep the check strict and update the expected count. Refs #455.
* test(cli): expect 24 platform configs in agent-query-contract
The kimi platform raises the platform config count from 23 to 24. Refs #455.
uipro init --ai copilot wrote .github/prompts/ui-ux-pro-max.prompt.md,
a prompt file that Copilot does not discover as a skill. It now installs
.github/skills/ui-ux-pro-max/SKILL.md with name/description frontmatter,
the data and scripts in the same folder and the sub-skills next to it,
which is where Copilot loads project skills. --global installs to
~/.copilot/skills/, Copilot's personal skills folder, through a new
optional folderStructure.globalRoot.
init and update remove the .github/prompts/ install they replace: the
prompt file, its data folder and the bundled sub-skills there. Other
files in .github/prompts/ are kept. uninstall removes both layouts.
Copilot is now detected from Copilot files (copilot-instructions.md,
instructions/, prompts/, agents/, skills/ or hooks/ under .github, or
~/.copilot/skills) instead of from any .github folder.
Closes#454
Co-authored-by: Jul11us <233702296+Jul11us@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add OpenClaw platform support
Add OpenClaw as an install target so the skill can be installed with
`uipro init --ai openclaw` and removed via `uipro uninstall`.
OpenClaw discovers AgentSkills-format skills from `.agents/skills` in the
agent workspace and from `~/.agents/skills` (personal library on the default
state dir), so the platform config reuses the `.agents` layout already used
by the universal/codex targets with its own display name, detection entry,
and docs.
- new platform config src/ui-ux-pro-max/templates/platforms/openclaw.json
(synced to cli/assets via sync:assets)
- register 'openclaw' in AIType, AI_TYPES, AI_FOLDERS, AI_TO_PLATFORM
- detect the shared .agents workspace directory and describe the platform
- keep the .agents-family suggestion on codex when all four .agents
consumers are detected (length 2-3 -> 2-4)
- cover openclaw in the dry-run, template-script-paths, and
agent-query-contract e2e specs
- document OpenClaw in README and cli/README
* chore: bump version to 2.15.0 in skill metadata files
Aligns skill.json, marketplace.json, and plugin.json with the latest
v2.15.0 release; main was still at 2.13.0. CLI package version stays on
its own npm release track.
* fix: cover OpenClaw in offline validator and detection regression
- bump scripts/validate-agent-guide.py PLATFORM_COUNT 21 -> 23 (main
already had 22 configs with a stale count of 21; OpenClaw widens the
gap to 23, so update the gate and keep it meaningful)
- add e2e regression: a sole .agents directory detects all four
consumers (antigravity, codex, universal, openclaw) and still
suggests codex rather than all
* feat: add Amazon Q Developer platform support
Add Amazon Q Developer as an install target so the skill can be installed
with `uipro init --ai amazonq` and removed via `uipro uninstall`.
Amazon Q loads every Markdown file under .amazonq/rules/ (recursively) as
always-on chat context, so only the rendered rule file goes there
(.amazonq/rules/ui-ux-pro-max.md). Data, scripts and the bundled
sub-skills go to .amazonq/skills/ via dataPath, the same split copilot
uses, so their reference docs are not pulled into every chat.
- new platform config src/ui-ux-pro-max/templates/platforms/amazonq.json
(synced to cli/assets via sync:assets)
- register 'amazonq' in AIType, AI_TYPES, AI_FOLDERS, AI_TO_PLATFORM
- detect .amazonq workspace directories and describe the platform
- cover amazonq in the dry-run and template-script-paths e2e specs
- document Amazon Q Developer in README and cli/README
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs: note that Amazon Q only auto-loads the rule file
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs: add Vibe Rooster before/after example
* docs: address review feedback on example section
Move the before/after example under a new Examples section after Usage, drop the ?vr_gallery=1 query params, replace the hosted-on wording with neutral framing, and add a provenance line (author-supplied, illustrative, not a benchmark) with the generating command.
* docs: make example section neutral
Remove attribution and promotional wording from the example provenance note; keep a short disclaimer that it is an illustrative, community-contributed example, not an official demo or benchmark.
---------
Co-authored-by: Tim Panagos <tpanagos@users.noreply.github.com>
Add ZCode as a first-class install target so the skill can be installed
with `uipro init --ai zcode` (workspace) or `uipro init --ai zcode --global`
(~/.zcode/skills/), and removed via `uipro uninstall` auto-detection.
- new platform config src/ui-ux-pro-max/templates/platforms/zcode.json
(synced to cli/assets via sync:assets)
- register 'zcode' in AIType union, AI_TYPES, AI_FOLDERS, AI_TO_PLATFORM
- detect .zcode workspace directories and describe the platform in CLI prompts
- cover zcode in the dry-run and template-script-paths e2e specs
- document ZCode in README install/usage sections
Co-authored-by: Dmso <22094486+dmsobtl@users.noreply.github.com>
feat(cli): add --dry-run to init to preview install actions without writing (#489)
Closes#291
- Adds resolveInstallPaths helper shared by real install and dry-run preview
- New planPlatformInstallActions / planAllPlatformInstallActions for read-only preview
- 3 e2e tests verify output content, no-write guarantee, and all-platforms coverage
- README docs included
*Approved and merged by github-maintain cron*
The README instructed users to run `uipro init --ai openclaw`, but
"openclaw" is not a supported AIType in the CLI (cli/src/types/index.ts),
so the command fails.
--persist writes design-system/<project-slug>/MASTER.md, but all four
READMEs document design-system/MASTER.md, omitting the per-project
folder. Following the README leads readers to look for files that are
never created there.
The code is unambiguous (design_system.py:1020):
design_system_dir = base_dir / "design-system" / project_slug
and search.py's own --help already documents it correctly, so this is a
documentation gap rather than a behaviour question.
The slug level is not incidental: without it, two projects persisted
into the same directory would overwrite each other's MASTER.md.
Updated in README.md, README.ko.md, README.vi.md and README.zh.md:
the folder tree, the hierarchical-retrieval steps and the context-aware
retrieval prompt. Uses the concrete slug "myapp" where the surrounding
example runs -p "MyApp", and [project-slug] where the text is generic.
Claude-Session: https://claude.ai/code/session_015UidECV1wVBD8SW6Abuj71
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The star history chart in README.md and README.zh.md is currently broken and fails to render because of GitHub stargazer API restrictions. Point the chart and its link to a working endpoint so visitors can still see the project's growth over time.
Clarify that the full repository archive is not a Claude.ai skill upload artifact and direct Claude Code users to the supported Marketplace and CLI installation paths.\n\nCloses #235.
* feat(cli): add --global flag to update command and support --ai universal (#435, #436)
* fix(cli): support dist package.json resolution in update command
Merged by github-maintain cron. Approved by @clark-cant and @jizc. Pre-existing pytest failure on main (ui-styling/shadcn test) is unrelated to PR scope.
Addresses the behavioral patterns that plausibly triggered the Gen
(Agent Trust Hub) High Risk rating on skills.sh, without changing
runtime functionality:
- Prerequisites no longer instruct agents to run sudo/brew/apt/winget
install commands; agents must ask the user to install Python instead
(SKILL.md, skill-content.md template, README.md, README.zh.md)
- Soften coercive invocation language ("Must Use" -> "Primary Use
Cases") and replace keyword-stuffed frontmatter descriptions with
factual ones (SKILL.md, quick-reference.md, claude/droid.json,
plugin.json)
- Remove design.csv, draft.csv and _sync_all.py: unused by the runtime
(not registered in core.py CSV_CONFIG) and containing prompt-shaped
"System Prompt: ... You are ..." blocks that read as injection risk
- Fix path traversal in --persist: new safe_slug() restricts project
and page names to [a-z0-9_-], so ../ in -p/--page can no longer
escape the design-system/ output folder
Verified: validate-csv.py (35 files), smoke-domains (12/12),
smoke-stacks (22/22), check:assets in sync, persist traversal attempt
stays confined.
Co-authored-by: Andras Polgar <5525341+ruredi@users.noreply.github.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- add CSV structural validation and all-domain smoke tests
- repair malformed CSV rows in source and bundled CLI assets
- run data validation in CI and prepublish checks
- add npm build wrapper with TypeScript fallback when Bun is unavailable
- fix CLI asset resolution for TypeScript fallback builds
Added the comparison between Basic and Premium versions to the README. Users were asking about this difference in Issue #156, so I added it here to improve the documentation.
Add README.zh.md with complete Chinese translation
Add language switcher links in both README files
Support for 简体中文 / English bilingual access
Features:
- Full translation of all UI/UX style names and terminology
- Consistent industry-standard Chinese terms (玻璃拟态、粗野主义等)
- Language switcher with flag icons at the top of both files
Adds WPF, WinUI 3, UWP, Avalonia, and Uno Platform stacks (17 -> 22 total),
each with its own guidelines CSV, registered in core.py and synced to cli/assets.
- New stack CSVs in src/ and cli/assets/data/stacks/
- search.py / core.py registry updated
- smoke-stacks.sh: EXPECTED_STACK_COUNT 21 -> 22 with a smoke-test workflow
- platform template descriptions and README bumped to 22 technology stacks
* fix CLI asset sync
* fix(cli): normalize line endings in asset sync/check
check:assets hashed raw bytes, so identical CSV/JSON/py content with
CRLF vs LF (git autocrlf on checkout) was reported as stale drift,
blocking the release guard on Windows/mixed checkouts.
- fileHash now normalizes CRLF->LF before hashing, so check:assets
compares content, not line endings.
- sync:assets writes LF-normalized copies instead of a raw byte copy,
so re-syncing is deterministic across platforms.
All synced assets are text (csv/json/md/py); no binaries affected.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* ci: enforce CLI asset sync on PRs
Adds a Check asset sync workflow that runs `npm run check:assets` on any
PR touching src/ui-ux-pro-max/** or cli/assets/**, so the bundled CLI
assets can't silently drift from the source of truth.
The check uses only node builtins (no install step) and normalizes
line endings before hashing, so it hard-fails on real content drift
without the CRLF/LF soft-fail hack other approaches needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>