The Documentation to install is very misleading with alot of assumptions.
Copy the engine into your project
cp -r engine/* your-project/
Run the setup wizard
/ss-setup
This assumes user is tech savy and knows git pull commands. Also the /ss-setup assumes the user has done the cp command already and then enters Claude Code to run the /ss-setup. This also assumes that the skills were copied into the .claude/skills directory.
Also, the Claude Code Skills page refers to 10 slash commands (skills) for Claude Code..
None of these skills exist in the package. For example /ui-page, /ui-review, /ui-component etc. Instead I see:
/ss-page Scaffold a new mobile page/screen using the StyleSeed layout patterns (project)
/ss-a11y Audit a component or page for accessibility issues and fix them (project)
/ss-copy Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone (project)
/ss-flow Design user flows and navigation structure following proven UX patterns (project)
/ss-lint Quick automated lint — detects common design system violations in seconds (project)
/ss-audit Audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices (project)
And there's a few more...
The documentation needs a run through to capture all steps to install, assume dummy audience....and the package needs to be updated to reflect files that the documentation refers to.
The Documentation to install is very misleading with alot of assumptions.
This assumes user is tech savy and knows git pull commands. Also the /ss-setup assumes the user has done the cp command already and then enters Claude Code to run the /ss-setup. This also assumes that the skills were copied into the .claude/skills directory.
Also, the Claude Code Skills page refers to 10 slash commands (skills) for Claude Code..
None of these skills exist in the package. For example /ui-page, /ui-review, /ui-component etc. Instead I see:
And there's a few more...
The documentation needs a run through to capture all steps to install, assume dummy audience....and the package needs to be updated to reflect files that the documentation refers to.