/ConvertVueProject
Convert class-based patterns to modern ones in a vue project — e.g. a vue 2 options-api project.
Your AI Command Vault
Making sure the /Summarize prompt is longer than the original.
Frameworks
36 commands
Convert class-based patterns to modern ones in a vue project — e.g. a vue 2 options-api project.
Convert class-based patterns to modern ones in a javascript-to-typescript migration — e.g. a 40-file javascript codebase with no type coverage.
Migrate to the latest patterns in a state management layer — e.g. a redux app being simplified to context and hooks.
Plan a safe dependency upgrade for a state management layer — e.g. a redux app being simplified to context and hooks.
Convert class-based patterns to modern ones in a tailwind css configuration — e.g. a tailwind config missing custom design tokens.
Migrate to the latest patterns in a next.js configuration — e.g. a next.js app router migration from pages router.
Plan a safe dependency upgrade for a next.js configuration — e.g. a next.js app router migration from pages router.
Migrate to the latest patterns in a css architecture — e.g. a legacy stylesheet with conflicting global classes.
Plan a safe dependency upgrade for a css architecture — e.g. a legacy stylesheet with conflicting global classes.
Convert class-based patterns to modern ones in a state management layer — e.g. a redux app being simplified to context and hooks.
Migrate to the latest patterns in an eslint configuration — e.g. a repo with no shared lint rules across packages.
Plan a safe dependency upgrade for an eslint configuration — e.g. a repo with no shared lint rules across packages.
Convert class-based patterns to modern ones in a next.js configuration — e.g. a next.js app router migration from pages router.
Migrate to the latest patterns in a react application — e.g. a react 17 app being moved to react 18.
Plan a safe dependency upgrade for a react application — e.g. a react 17 app being moved to react 18.
Convert class-based patterns to modern ones in a css architecture — e.g. a legacy stylesheet with conflicting global classes.
Migrate to the latest patterns in a client-side routing setup — e.g. a react-router v5 app needing v6 routes.
Plan a safe dependency upgrade for a client-side routing setup — e.g. a react-router v5 app needing v6 routes.
Convert class-based patterns to modern ones in an eslint configuration — e.g. a repo with no shared lint rules across packages.
Migrate to the latest patterns in a vite build setup — e.g. a webpack project moving to vite.
Plan a safe dependency upgrade for a vite build setup — e.g. a webpack project moving to vite.
Convert class-based patterns to modern ones in a react application — e.g. a react 17 app being moved to react 18.
Migrate to the latest patterns in a frontend package.json — e.g. a package.json with 12 outdated major versions.
Plan a safe dependency upgrade for a frontend package.json — e.g. a package.json with 12 outdated major versions.
Convert class-based patterns to modern ones in a client-side routing setup — e.g. a react-router v5 app needing v6 routes.
Migrate to the latest patterns in a frontend monorepo — e.g. a monorepo with three shared ui packages.
Plan a safe dependency upgrade for a frontend monorepo — e.g. a monorepo with three shared ui packages.
Convert class-based patterns to modern ones in a vite build setup — e.g. a webpack project moving to vite.
Migrate to the latest patterns in a vue project — e.g. a vue 2 options-api project.
Plan a safe dependency upgrade for a vue project — e.g. a vue 2 options-api project.
Convert class-based patterns to modern ones in a frontend package.json — e.g. a package.json with 12 outdated major versions.
Migrate to the latest patterns in a javascript-to-typescript migration — e.g. a 40-file javascript codebase with no type coverage.
Plan a safe dependency upgrade for a javascript-to-typescript migration — e.g. a 40-file javascript codebase with no type coverage.
Convert class-based patterns to modern ones in a frontend monorepo — e.g. a monorepo with three shared ui packages.
Migrate to the latest patterns in a tailwind css configuration — e.g. a tailwind config missing custom design tokens.
Plan a safe dependency upgrade for a tailwind css configuration — e.g. a tailwind config missing custom design tokens.