Stats
Actions
Tags
From zeppelin-dev
Zeppelin frontend development guide for Angular, proxy setup, E2E tests, and linting
How this skill is triggered — by the user, by Claude, or both
Slash command
/zeppelin-dev:frontendThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The active frontend is in `zeppelin-web-angular/` (Angular 13, Node 18).
The active frontend is in zeppelin-web-angular/ (Angular 13, Node 18).
cd zeppelin-web-angular
npm install
npm start # Dev server on port 4200, proxies API to localhost:8080
npm run build # Production build
npm run lint:fix # ESLint + Prettier
npm run e2e # Playwright E2E tests
The dev proxy (proxy.conf.js) forwards:
http://127.0.0.1:8080ws://127.0.0.1:8080/wszeppelin-web-angular/ — Main Angular 13 app
zeppelin-sdk, zeppelin-visualizationzeppelin-web/ — Legacy AngularJS frontend (activated with -Pweb-classic)ESLint + Prettier are auto-enforced via pre-commit hook (Husky + lint-staged). Always run before committing:
cd zeppelin-web-angular && npm run lint:fix
Playwright-based E2E tests. Run with:
cd zeppelin-web-angular && npm run e2e
CI runs E2E in both anonymous and authenticated modes (.github/workflows/frontend.yml).
| Profile | Purpose |
|---|---|
-Pweb-e2e | Enable Angular E2E tests |
-Pweb-dist | Build web distribution |
-Pweb-classic | Include legacy AngularJS frontend |
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub jongyoul/claude-plugins-zeppelin --plugin zeppelin-dev