From 4b70e6ba33855a13d19ca727bf20b3970f3f6e64 Mon Sep 17 00:00:00 2001 From: Leon van Zyl Date: Sat, 8 Nov 2025 11:50:43 +0200 Subject: [PATCH] clean up commands --- .claude/commands/apply-design-system.md | 5 --- .claude/commands/create-design-system.md | 27 ----------- .claude/commands/create-feature.md | 11 +++++ .claude/commands/document-feature.md | 45 ------------------- .claude/commands/fix-build-issues.md | 6 --- .claude/commands/start-dev-server.md | 2 - create-agentic-app/package-lock.json | 4 +- create-agentic-app/package.json | 2 +- .../.claude/commands/apply-design-system.md | 5 --- .../.claude/commands/create-design-system.md | 27 ----------- .../.claude/commands/create-feature.md | 11 +++++ .../.claude/commands/document-feature.md | 45 ------------------- .../.claude/commands/fix-build-issues.md | 6 --- .../.claude/commands/start-dev-server.md | 2 - 14 files changed, 25 insertions(+), 173 deletions(-) delete mode 100644 .claude/commands/apply-design-system.md delete mode 100644 .claude/commands/create-design-system.md create mode 100644 .claude/commands/create-feature.md delete mode 100644 .claude/commands/document-feature.md delete mode 100644 .claude/commands/fix-build-issues.md delete mode 100644 .claude/commands/start-dev-server.md delete mode 100644 create-agentic-app/template/.claude/commands/apply-design-system.md delete mode 100644 create-agentic-app/template/.claude/commands/create-design-system.md create mode 100644 create-agentic-app/template/.claude/commands/create-feature.md delete mode 100644 create-agentic-app/template/.claude/commands/document-feature.md delete mode 100644 create-agentic-app/template/.claude/commands/fix-build-issues.md delete mode 100644 create-agentic-app/template/.claude/commands/start-dev-server.md diff --git a/.claude/commands/apply-design-system.md b/.claude/commands/apply-design-system.md deleted file mode 100644 index 9ecebad..0000000 --- a/.claude/commands/apply-design-system.md +++ /dev/null @@ -1,5 +0,0 @@ -Your role is to ensure that the pages in the project conform to the design system as documented in /docs/ui. -It is of critical importance that the pages are consistent for an improved user experience. - -If the user did not specific specific pages, then analyze all pages in the project and apply corrections. -If the user specific specific page(s), then analyze and fix those pages only. diff --git a/.claude/commands/create-design-system.md b/.claude/commands/create-design-system.md deleted file mode 100644 index 8c42806..0000000 --- a/.claude/commands/create-design-system.md +++ /dev/null @@ -1,27 +0,0 @@ -Your role is to generate a detailed and complete UI design system for the current project. - -This design system should be documented in the /docs/ui folder. Create or update the following files in this folder: - -- COOKBOOK.md -- PRINCIPLES.md -- TOKENS.md -- README.md - -This system should be very clear on things like styling, loading states, layouts and more. - -# Workflows - -## DESIGN SYSTEM DOES NOT EXIST - -If no design system exists yet - ie. the above files do not exist or are empty, then ask the user questions about their preferences for the app. -Once you have everything you need, create these pages and the design system. - -## DESIGN SYSTEM ALREADY EXISTS - -If a design system is already in place - ie. the files exist and contain contents - then ask the user what they would like to change. Update the documents accordingly. - -# IMPORTANT! - -Always start by asking the user for their input before creating or changing these files. - -Keep the questions to a minimum and guide the user along the way. Assume they know nothing about professional design systems. diff --git a/.claude/commands/create-feature.md b/.claude/commands/create-feature.md new file mode 100644 index 0000000..dac142d --- /dev/null +++ b/.claude/commands/create-feature.md @@ -0,0 +1,11 @@ +--- +description: create feature +--- + +# Given the above conversation: + +- Store the requirements and implementation plan in /specs. Create a new sub folder for this feature. The implementation plan should be split into phases with actionable tasks for each phase. Each tasks should have a checkbox so we can keep track of our progress - example [ ] Task description. + +- Exclude unit and e2e testing from the implementation plan, UNLESS the user clearly asks for it to be included. + +- IF no conversation exists and the implementation plan is not clear, then ask the user what the requirements are first and then create the spec sub-folder, requirements and implementation plan .md files. diff --git a/.claude/commands/document-feature.md b/.claude/commands/document-feature.md deleted file mode 100644 index 667de8d..0000000 --- a/.claude/commands/document-feature.md +++ /dev/null @@ -1,45 +0,0 @@ -Update the documents in /docs/features to reflect the latest changes. - -Feature documents should not contain any technical information. - -The following sections should be included: - -# - -## Overview - -## What are / is - -### Core Workflow - -### Key Components - -## Business Value - -### Problem Statement - -### Solution Benefits - -## User Types and Personas - -### Primary Users - -### Secondary Users - -## User Workflows - -### Primary Workflow - -### Alternative Workflows - -## Functional Requirements - -### Supporting Features - -## User Interface Specifications - -## Security Considerations - -## Testing Strategy - -## Success Metrics diff --git a/.claude/commands/fix-build-issues.md b/.claude/commands/fix-build-issues.md deleted file mode 100644 index ecf6203..0000000 --- a/.claude/commands/fix-build-issues.md +++ /dev/null @@ -1,6 +0,0 @@ -We are trying to clear out the many lint and typecheck issues in the project. -Please use the lint and typecheck scripts to resolve all issues. -Do not introduce any lint of type issues with your changes. For example, DO NOT use type any! - -For database schema interfaces, I believe drizzle has a built in function for inferring the types. -Think harder. Ensure you don't introduce new type and lint errors with your changes. diff --git a/.claude/commands/start-dev-server.md b/.claude/commands/start-dev-server.md deleted file mode 100644 index e94e102..0000000 --- a/.claude/commands/start-dev-server.md +++ /dev/null @@ -1,2 +0,0 @@ -Start the dev server on port 3000. -ALWAYS use port 3000. Use npx kill if the port is in use. diff --git a/create-agentic-app/package-lock.json b/create-agentic-app/package-lock.json index fcc84f9..64c9513 100644 --- a/create-agentic-app/package-lock.json +++ b/create-agentic-app/package-lock.json @@ -1,12 +1,12 @@ { "name": "create-agentic-app", - "version": "1.1.12", + "version": "1.1.13", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "create-agentic-app", - "version": "1.1.12", + "version": "1.1.13", "license": "MIT", "dependencies": { "chalk": "^5.3.0", diff --git a/create-agentic-app/package.json b/create-agentic-app/package.json index ba4a185..36cf397 100644 --- a/create-agentic-app/package.json +++ b/create-agentic-app/package.json @@ -1,6 +1,6 @@ { "name": "create-agentic-app", - "version": "1.1.12", + "version": "1.1.13", "description": "Scaffold a new agentic AI application with Next.js, Better Auth, and AI SDK", "type": "module", "bin": { diff --git a/create-agentic-app/template/.claude/commands/apply-design-system.md b/create-agentic-app/template/.claude/commands/apply-design-system.md deleted file mode 100644 index 9ecebad..0000000 --- a/create-agentic-app/template/.claude/commands/apply-design-system.md +++ /dev/null @@ -1,5 +0,0 @@ -Your role is to ensure that the pages in the project conform to the design system as documented in /docs/ui. -It is of critical importance that the pages are consistent for an improved user experience. - -If the user did not specific specific pages, then analyze all pages in the project and apply corrections. -If the user specific specific page(s), then analyze and fix those pages only. diff --git a/create-agentic-app/template/.claude/commands/create-design-system.md b/create-agentic-app/template/.claude/commands/create-design-system.md deleted file mode 100644 index 8c42806..0000000 --- a/create-agentic-app/template/.claude/commands/create-design-system.md +++ /dev/null @@ -1,27 +0,0 @@ -Your role is to generate a detailed and complete UI design system for the current project. - -This design system should be documented in the /docs/ui folder. Create or update the following files in this folder: - -- COOKBOOK.md -- PRINCIPLES.md -- TOKENS.md -- README.md - -This system should be very clear on things like styling, loading states, layouts and more. - -# Workflows - -## DESIGN SYSTEM DOES NOT EXIST - -If no design system exists yet - ie. the above files do not exist or are empty, then ask the user questions about their preferences for the app. -Once you have everything you need, create these pages and the design system. - -## DESIGN SYSTEM ALREADY EXISTS - -If a design system is already in place - ie. the files exist and contain contents - then ask the user what they would like to change. Update the documents accordingly. - -# IMPORTANT! - -Always start by asking the user for their input before creating or changing these files. - -Keep the questions to a minimum and guide the user along the way. Assume they know nothing about professional design systems. diff --git a/create-agentic-app/template/.claude/commands/create-feature.md b/create-agentic-app/template/.claude/commands/create-feature.md new file mode 100644 index 0000000..dac142d --- /dev/null +++ b/create-agentic-app/template/.claude/commands/create-feature.md @@ -0,0 +1,11 @@ +--- +description: create feature +--- + +# Given the above conversation: + +- Store the requirements and implementation plan in /specs. Create a new sub folder for this feature. The implementation plan should be split into phases with actionable tasks for each phase. Each tasks should have a checkbox so we can keep track of our progress - example [ ] Task description. + +- Exclude unit and e2e testing from the implementation plan, UNLESS the user clearly asks for it to be included. + +- IF no conversation exists and the implementation plan is not clear, then ask the user what the requirements are first and then create the spec sub-folder, requirements and implementation plan .md files. diff --git a/create-agentic-app/template/.claude/commands/document-feature.md b/create-agentic-app/template/.claude/commands/document-feature.md deleted file mode 100644 index 667de8d..0000000 --- a/create-agentic-app/template/.claude/commands/document-feature.md +++ /dev/null @@ -1,45 +0,0 @@ -Update the documents in /docs/features to reflect the latest changes. - -Feature documents should not contain any technical information. - -The following sections should be included: - -# - -## Overview - -## What are / is - -### Core Workflow - -### Key Components - -## Business Value - -### Problem Statement - -### Solution Benefits - -## User Types and Personas - -### Primary Users - -### Secondary Users - -## User Workflows - -### Primary Workflow - -### Alternative Workflows - -## Functional Requirements - -### Supporting Features - -## User Interface Specifications - -## Security Considerations - -## Testing Strategy - -## Success Metrics diff --git a/create-agentic-app/template/.claude/commands/fix-build-issues.md b/create-agentic-app/template/.claude/commands/fix-build-issues.md deleted file mode 100644 index ecf6203..0000000 --- a/create-agentic-app/template/.claude/commands/fix-build-issues.md +++ /dev/null @@ -1,6 +0,0 @@ -We are trying to clear out the many lint and typecheck issues in the project. -Please use the lint and typecheck scripts to resolve all issues. -Do not introduce any lint of type issues with your changes. For example, DO NOT use type any! - -For database schema interfaces, I believe drizzle has a built in function for inferring the types. -Think harder. Ensure you don't introduce new type and lint errors with your changes. diff --git a/create-agentic-app/template/.claude/commands/start-dev-server.md b/create-agentic-app/template/.claude/commands/start-dev-server.md deleted file mode 100644 index e94e102..0000000 --- a/create-agentic-app/template/.claude/commands/start-dev-server.md +++ /dev/null @@ -1,2 +0,0 @@ -Start the dev server on port 3000. -ALWAYS use port 3000. Use npx kill if the port is in use.