* feat: add AutoClaw compatibility
- Add root SKILL.md following the open SKILL.md standard
- Add 'autoclaw' to skill.json#platforms
- Add AutoClaw install instructions to README
- Add docs/autoclaw-install.md with detailed install guide
AutoClaw is Z.ai's official general-purpose AI agent (https://autoclaw.z.ai),
part of the GLM Coding Plan family alongside ZCode and OpenClaw. This PR
adds first-class AutoClaw support without changing any existing platform
install paths.
Verified SKILL.md compliance with AutoClaw/ZCode spec:
- name and description in frontmatter (required)
- description < 1024 chars
- body < 100KB
- explicit trigger phrases in description
* text feat(cli): add AutoClaw platform support
- Register 'autoclaw' in AIType, AI_TYPES, and AI_FOLDERS configuration.
- Update SKILL.md to fix broken search script paths and incorrect folder layout documentation.
- Synchronize CLI assets to ensure platform configuration and script paths are correctly bundled.
* fix(cli): install AutoClaw skills where AutoClaw actually loads them
AutoClaw does not scan `.autoclaw`; it reads workspace `skills/` plus the
shared `~/.openclaw-autoclaw/skills` directory. Point the platform config at
those roots so `uipro init --ai autoclaw` produces a skill that AutoClaw
discovers without extra configuration.
- register `autoclaw` in AI_TO_PLATFORM and add templates/platforms/autoclaw.json
with root `skills` and globalRoot `.openclaw-autoclaw/skills`
- detect AutoClaw from `.autoclaw` or an installed `skills/ui-ux-pro-max/SKILL.md`
and add its CLI description
- sync cli/assets, including the packaged autoclaw.json
- restore the `## Using the Search Script (CLI)` section in the canonical skill
template, keep the explanatory paragraph as body text, and remove the
source-repo path from generated content
- make search.py add its own directory to sys.path so sibling imports work on
embedded Python builds whose `._pth` omits the script directory (AutoClaw's
bundled runtime)
- remove the hand-maintained root SKILL.md; templates/base/skill-content.md is
the single source of truth
- rewrite docs/INSTALL.md around the verified local and global CLI workflows
- update e2e coverage for the new platform count, detection, and script paths
Validated with npm run check:assets, npm run typecheck, 49 Playwright tests,
164 Python tests, and local/global installs whose generated search script runs
successfully from the installed skill directory.
* Update search.py
* 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>
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>
droid's install root (.factory) doesn't match its platform
identifier, the same mismatch pattern already covered for codex
(.agents). Extends the existing test cases rather than adding new
assertions.