From automation
Run any feature creation workflow. Pass the workflow type as the first argument. Available types: modal, page, inquiry-process, interactive-list, list-actions, secure-fetch, simple-form, task-group, generic.
npx claudepluginhub joshuarweaver/cascade-code-languages-misc-1 --plugin finstreet-fe-claude-pluginsThis skill uses the workspace's default tool permissions.
Route to the correct workflow based on the first argument.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Route to the correct workflow based on the first argument.
| Type | Description | File |
|---|---|---|
modal | End-to-end modal creation (parent paths, translations, modal component) | modal.md |
page | End-to-end page creation (routes, translations, page component) | page.md |
inquiry-process | End-to-end inquiry process creation (routes, parent paths, translations, all files) | inquiry-process.md |
interactive-list | End-to-end interactive list creation (parent paths, translations, list component) | interactive-list.md |
list-actions | End-to-end list actions/pagination creation for interactive lists | list-actions.md |
secure-fetch | End-to-end secure fetch/API request creation (parent paths, schemas, endpoints) | secure-fetch.md |
simple-form | Simple form creation (delegates to form skill) | simple-form.md |
task-group | End-to-end task group creation (translations, all task group files) | task-group.md |
generic | Generic feature creation (parent paths, general implementation) | generic.md |
$ARGUMENTS[0] — the workflow type (required, one of the types listed above)$ARGUMENTS[1..] — passed through to the workflow as its input (subtaskId, or positional args like featureName, subFeatureName, featureType, product, role)$ARGUMENTS[0] to determine the workflow type.md file from this directory$ARGUMENTS[1..] as the workflow's inputgeneral-purpose subagent (if not specified otherwise) and invoke the skill / task inside of the subagent. Never run these in the main thread.