
eliteforge-frontend-generator
Generate EliteForge frontend projects with the same logic as cisdigital-generator-app. Reuse the exact project type to template mapping for frontendapp/frontendui/frontendsdk, naming rules for company/product/service, and onebase-cli command assembly. Use when users ask to scaffold EliteForge frontend app projects, Vue3 component monorepo projects, JS SDK/lib projects, or request a dry-run command preview aligned with this generator. Always require user-provided required parameters and never infer missing required fields.
- Installs
- 43
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/cloudsen/eliteforge-skills --skill eliteforge-frontend-generator- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads eliteforge-frontend-generator automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
EliteForge 前端生成器
Overview
Generate frontend projects with deterministic rules from the online generator app.
Use the bundled script to produce a dry-run payload/command preview or run project creation directly.
Project name is mandatory: fe-<company_name>-<product_name>-<service_name>.
Package Manager Policy
- Treat
pnpmas the only package manager for generated frontend projects. - After project generation, always initialize dependencies with
pnpm iinside the generated project directory. - Do not replace
pnpm iwithnpm install,yarn, orpnpm install.
Project Naming Policy
- Always pass
project_nameto scaffold CLI asfe-<company_slug>-<product_slug>-<service_slug>. - Never drop the
fe-prefix. - Never append project-type suffixes such as
-app,-ui, or-sdk.
Mandatory Input Policy
- Treat
project_type,company_name,product_name, andservice_nameas required and user-provided only. - Never infer required fields from repository name, current directory, previous conversation values, defaults, or examples.
- If any required field is missing, stop and ask only for missing fields first.
- Do not run dry-run or generation before all required fields are explicitly provided by the user.
- If user input is ambiguous (for example "same as before" or "use default"), ask for explicit values.
Inputs
Collect the following fields.
Required (must come from the user message):
project_type:frontend_app,frontend_ui, orfrontend_sdkcompany_name: kebab-caseproduct_name: kebab-caseservice_name: kebab-case
Optional:
cli_name: defaultonebase-clioutput_dir: default current working directoryauto_slugify: defaultfalse; use only when the user explicitly asks to convert non-kebab names
Workflow
- Collect required fields only from explicit user input.
- If required fields are missing, ask only for the missing fields and wait for user response.
- Validate naming fields as kebab-case.
- If naming is invalid and
auto_slugifyis not explicitly requested, ask the user to provide kebab-case values. - Run dry-run first to show payload and command.
- Verify dry-run command uses
-p fe-<company_slug>-<product_slug>-<service_slug>. - Execute the create command.
- Change to generated project directory and run
pnpm i. - Confirm generated folder exists and initialization completed.
Read references/frontend-generation-logic.md when the user asks why a template or project name is chosen.
Commands
Dry-run:
python3 scripts/create_frontend_project.py \
--project-type frontend_app \
--company-name cisdigital \
--product-name your-product \
--service-name your-service \
--dry-run
Generate frontend_app:
python3 scripts/create_frontend_project.py \
--project-type frontend_app \
--company-name cisdigital \
--product-name your-product \
--service-name your-service
cd fe-cisdigital-your-product-your-service
pnpm i
Generate frontend_ui:
python3 scripts/create_frontend_project.py \
--project-type frontend_ui \
--company-name cisdigital \
--product-name your-product \
--service-name your-component
cd fe-cisdigital-your-product-your-component
pnpm i
Generate frontend_sdk:
python3 scripts/create_frontend_project.py \
--project-type frontend_sdk \
--company-name cisdigital \
--product-name your-product \
--service-name your-jsdk
cd fe-cisdigital-your-product-your-jsdk
pnpm i
Use custom CLI or output directory:
python3 scripts/create_frontend_project.py \
--project-type frontend_app \
--company-name cisdigital \
--product-name your-product \
--service-name your-service \
--cli-name onebase-cli \
--output-dir /path/to/workspace
cd /path/to/workspace/fe-cisdigital-your-product-your-service
pnpm i
Convert non-kebab input (only when user explicitly requests conversion):
python3 scripts/create_frontend_project.py \
--project-type frontend_app \
--company-name "CIS Digital" \
--product-name "My Product" \
--service-name "Portal UI" \
--auto-slugify \
--dry-run
Notes
frontend_project_typeexists in the form data but does not affect template selection in current generator logic.- The script blocks generation if target project directory already exists.
- Always initialize generated projects with
pnpm i. - Generated project directory name is exactly
fe-<company_slug>-<product_slug>-<service_slug>. - Keep output concise: return generated directory, create command, and
pnpm iresult. - Never guess or fill missing required fields on behalf of the user.
FAQ
What does the eliteforge-frontend-generator skill do?
Generate EliteForge frontend projects with the same logic as cisdigital-generator-app. Reuse the exact project type to template mapping for frontendapp/frontendui/frontendsdk, naming rules for company/product/service, and onebase-cli command assembly. Use when users ask to scaffold EliteForge frontend app projects, Vue3 component monorepo projects, JS SDK/lib projects, or request a dry-run command preview aligned with this generator. Always require user-provided required parameters and never infer missing required fields.
How do I install eliteforge-frontend-generator?
Run npx skills add https://github.com/cloudsen/eliteforge-skills --skill eliteforge-frontend-generator in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/eliteforge-frontend-generator/ (personal) or .claude/skills/eliteforge-frontend-generator/ (project).
Which AI agents can use eliteforge-frontend-generator?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is eliteforge-frontend-generator safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains eliteforge-frontend-generator?
It is published by cloudsen in cloudsen/eliteforge-skills. It has 43 recorded installs.
More from cloudsen/eliteforge-skills
wechat-message-sender
cloudsen/eliteforge-skills
在 macOS 上通过微信桌面版向指定联系人发送文本消息。用户提供联系人名称和消息内容时使用,例如“给张三发微信:xxx”“打开微信给某人发送一句话”“用微信发送指定文本”。运行前必须已安装微信桌面版,并给当前终端或 Codex 辅助功能权限。执行时只做精确匹配:先搜索联系人,再校验当前会话标题与目标完全一致;匹配失败就停止,避免误发。
eliteforge-framework-specification
cloudsen/eliteforge-skills
约束 Java 开发优先复用璀璨工坊统一框架能力,避免重复造轮子。基于《璀璨工坊统一框架-使用手册-nightly》提供统一框架接入、升级、配置、Starter 选型与排障指引。命中框架能力时必须使用框架内 Starter 和对应抽象 API,禁止回退到 Spring 官方 starter 或绕过框架抽象层(如缓存场景绕过 CacheService 直接用 StringRedisTemplate)。用户提到“统一框架”“starter清单”“接入步骤”“升级步骤”“系统要求”“Web MVC/服务间调用/Mybatis-Plus/加解密/缓存/多数据源/代码生成器/资源抽象层”或需要判断“该功能是否应直接使用某个 starter(如 cache-starter)”时使用。
eliteforge-task-progress-tracker
cloudsen/eliteforge-skills
Open the skill to read its SKILL.md instructions.
eliteforge-java-uml
cloudsen/eliteforge-skills
Open the skill to read its SKILL.md instructions.
eliteforge-java-service-generator
cloudsen/eliteforge-skills
Generate an EliteForge Java service project via Maven archetype wrapper script. Use when users ask to scaffold a new EliteForge service, provide companyName/productName/serviceName (kebab-case), need Maven archetype generation execution, or want tech stack to enableXXX mapping.
eliteforge-sonar-pmd-generator
cloudsen/eliteforge-skills
Transform user-provided coding specification files into a layered governance plan and validated SonarQube plugin workflow. Automatically classify each requirement into L1/L2/L3/L4, implement L1-L2 as PMD rules for supported languages, route L3 to automation tooling, route L4 to human or AI review, package rules into a custom sonar-pmd plugin, and verify with Docker Sonar + real project scans.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.