diff --git a/packages/angular.yaml b/packages/angular.yaml
deleted file mode 100644
index 6486610..0000000
--- a/packages/angular.yaml
+++ /dev/null
@@ -1,57 +0,0 @@
-name: Angular
-version: 0.0.1
-
-rules:
-  - You are an Angular developer
-  - Use Angular CLI for project scaffolding
-  - Use TypeScript with strict mode enabled
-  - Use RxJS for state management and async operations
-  - |
-    Use the typical naming conventions:
-    - Components: .component.ts
-    - Services: .service.ts
-    - Pipes: .pipe.ts
-    - Module: .module.ts
-    - Test: .spec.ts
-    - Directives: .directive.ts
-    ```
-
-prompts:
-  - name: New Component
-    description: Create a new Angular component
-    prompt: |
-      Please create a new Angular component following these guidelines:
-      - Include JSDoc comments for component and inputs/outputs
-      - Implement proper lifecycle hooks
-      - Include TypeScript interfaces for models
-      - Follow container/presentational component pattern where appropriate
-      - Include unit tests with Jasmine/Karma in a separate test file
-      - Make sure to create separate files for any services, pipes, modules, and directives
-
-  - name: Review
-    description: Review changes
-    prompt: |
-      Please review the current code changes looking for:
-
-      - Memory leaks (unsubscribed observables)
-      - Proper change detection strategy
-      - Proper use of async pipe
-      - Proper error handling
-
-      Format the review as:
-      ```
-      ## <FILENAME>
-      - <ISSUE>
-      ...
-      - <ISSUE>
-      ```
-
-docs:
-  - name: Angular Docs
-    startUrl: https://angular.io/docs
-  - name: Angular CLI
-    startUrl: https://angular.io/cli
-  - name: RxJS Docs
-    startUrl: https://rxjs.dev/guide/overview
-  - name: Angular Material
-    startUrl: https://material.angular.io/
diff --git a/packages/claude-3-5-sonnet.yaml b/packages/claude-3-5-sonnet.yaml
deleted file mode 100644
index e154bf6..0000000
--- a/packages/claude-3-5-sonnet.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
-name: Claude 3.5 Sonnet
-version: 0.0.1
-
-models:
-  - name: Claude 3.5 Sonnet
-    provider: anthropic
-    model: claude-3-5-sonnet
-    apiKey: ${{ secrets.ANTHROPIC_API_KEY }}
-    defaultCompletionOptions:
-      temperature: ${{ params.temperature }}
diff --git a/packages/codestral.yaml b/packages/codestral.yaml
deleted file mode 100644
index 13b02fd..0000000
--- a/packages/codestral.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
-name: Codestral
-version: 0.0.1
-
-models:
-  - name: Codestral
-    provider: mistral
-    model: codestral-latest
-    apiKey: ${{ secrets.MISTRAL_API_KEY }}
-    roles:
-      - autocomplete
\ No newline at end of file
diff --git a/packages/data-science-and-machine-learning.yaml b/packages/data-science-and-machine-learning.yaml
deleted file mode 100644
index 3c583f3..0000000
--- a/packages/data-science-and-machine-learning.yaml
+++ /dev/null
@@ -1,104 +0,0 @@
-name: Data science & machine learning
-version: 0.0.1
-
-rules:
-  - |
-    You are an experienced data scientist who specializes in Python-based
-    data science and machine learning. You use the following tools:
-    - Python 3 as the primary programming language
-    - PyTorch for deep learning and neural networks
-    - NumPy for numerical computing and array operations
-    - Pandas for data manipulation and analysis
-    - Jupyter for interactive development and visualization
-    - Conda for environment and package management
-    - Matplotlib for data visualization and plotting
-
-prompts:
-  - name: Exploratory Data Analysis
-    description: Initial data exploration and key insights
-    prompt: |
-      Create an exploratory data analysis workflow that includes:
-
-      Data Overview:
-      - Basic statistics (mean, median, std, quartiles)
-      - Missing values and data types
-      - Unique value distributions
-
-      Visualizations:
-      - Numerical: histograms, box plots
-      - Categorical: bar charts, frequency plots
-      - Relationships: correlation matrices
-      - Temporal patterns (if applicable)
-
-      Quality Assessment:
-      - Outlier detection
-      - Data inconsistencies
-      - Value range validation
-
-      Insights & Documentation:
-      - Key findings summary
-      - Data quality issues
-      - Variable relationships
-      - Next steps recommendations
-      - Reproducible Jupyter notebook
-
-      The user has provided the following information:
-
-  - name: Data Pipeline Development
-    description: Create robust and scalable data processing pipelines
-    prompt: |
-      Generate a data processing pipeline with these requirements:
-
-      Input:
-      - Data loading from multiple sources (CSV, SQL, APIs)
-      - Input validation and schema checks
-      - Error logging for data quality issues
-
-      Processing:
-      - Standardized cleaning (missing values, outliers, types)
-      - Memory-efficient operations for large datasets
-      - Numerical transformations using NumPy
-      - Feature engineering and aggregations
-
-      Quality & Monitoring:
-      - Data quality checks at key stages
-      - Validation visualizations with Matplotlib
-      - Performance monitoring
-
-      Structure:
-      - Modular, documented code with error handling
-      - Configuration management
-      - Reproducible in Jupyter notebooks
-      - Example usage and tests
-
-      The user has provided the following information:
-
-docs:
-  - name: Python
-    startUrl: https://docs.python.org/3/
-
-  - name: PyTorch
-    startUrl: https://pytorch.org/docs/stable/index.html
-
-  - name: NumPy
-    startUrl: https://numpy.org/doc/stable/
-
-  - name: Pandas
-    startUrl: https://pandas.pydata.org/docs/
-
-  - name: Jupyter
-    startUrl: https://docs.jupyter.org/en/latest/
-
-  - name: Conda
-    startUrl: https://docs.conda.io/en/latest/
-
-  - name: Matplotlib
-    startUrl: https://matplotlib.org/stable/
-
-context:
-  - uses: docs
-  - uses: diff
-  - uses: web
-  - uses: url
-  - uses: folder
-  - uses: terminal
diff --git a/packages/django.yaml b/packages/django.yaml
deleted file mode 100644
index 79dc031..0000000
--- a/packages/django.yaml
+++ /dev/null
@@ -1,37 +0,0 @@
-name: Django
-version: 0.0.1
-
-rules:
-  - Follow Django style guide
-  - Avoid using raw queries
-  - Prefer the Django REST Framework for API development
-  - Prefer Celery for background tasks
-  - Prefer Redis for caching and task queues
-  - Prefer PostgreSQL for production databases
-
-prompts:
-  - name: Create a basic Django model with common fields
-    description: 
-    prompt: Create a basic Django model with common fields
-    - name: Add login required decorator
-    description: 
-    prompt: Add login required decorator
-  - name: Create basic CRUD class-based views
-    description: 
-    prompt: Create basic CRUD class-based views
-
-docs:
-  - name: Django
-    startUrl: https://docs.djangoproject.com/en/stable/
-  
-  - name: Django REST Framework
-    startUrl: https://www.django-rest-framework.org/
-
-  - name: Celery
-    startUrl: https://docs.celeryq.dev/en/stable/
-
-  - name: Redis
-    startUrl: 
-
-  - name: PostgreSQL
-    startUrl: 
\ No newline at end of file
diff --git a/packages/express.yaml b/packages/express.yaml
deleted file mode 100644
index 7277185..0000000
--- a/packages/express.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: Express
-version: 0.0.1
-
-rules:
-  - Follow Express best practices
-  - Avoid callback hell
-
-prompts:
-  - name: Write Supertest
-    description: Write tests with Supertest
-    prompt: Use Supertest to write a comprehensive suite of tests for this application
-
-docs:
-  - name: Express docs
-    startUrl: https://expressjs.com/en/4x/api.html
-    rootUrl: https://expressjs.com/en/4x/api.html 
\ No newline at end of file
diff --git a/packages/flask.yaml b/packages/flask.yaml
deleted file mode 100644
index 70ade99..0000000
--- a/packages/flask.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: Flask
-version: 0.0.1
-
-rules:
-  - Follow Flask patterns
-  - Avoid using global state
-
-prompts:
-  - name: Write Flask tests
-    description: Write tests with Flask
-    prompt: Use Flask to write a comprehensive suite of tests for this application
-
-docs:
-  - name: Flask docs
-    startUrl: https://flask.palletsprojects.com/en/2.0.x/
-    rootUrl: https://flask.palletsprojects.com/en/2.0.x/ 
\ No newline at end of file
diff --git a/packages/java.yaml b/packages/java.yaml
deleted file mode 100644
index 2a38c1e..0000000
--- a/packages/java.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: Java
-version: 0.0.1
-
-rules:
-  - Follow Java coding standards
-  - Avoid using raw types
-
-prompts:
-  - name: Write JUnit
-    description: Write unit test with JUnit
-    prompt: Use JUnit to write a comprehensive suite of unit tests for this function
-
-docs:
-  - name: Java docs
-    startUrl: https://docs.oracle.com/javase/8/docs/api/
-    rootUrl: https://docs.oracle.com/javase/8/docs/api/ 
\ No newline at end of file
diff --git a/packages/javascript.yaml b/packages/javascript.yaml
deleted file mode 100644
index 3562187..0000000
--- a/packages/javascript.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: JavaScript
-version: 0.0.1
-
-rules:
-  - Follow ES6+ conventions
-  - Avoid using 'var' keyword
-
-prompts:
-  - name: Write Jest
-    description: Write unit test with Jest
-    prompt: Use Jest to write a comprehensive suite of unit tests for this function
-
-docs:
-  - name: JavaScript docs
-    startUrl: https://developer.mozilla.org/en-US/docs/Web/JavaScript
-    rootUrl: https://developer.mozilla.org/en-US/docs/Web/JavaScript 
\ No newline at end of file
diff --git a/packages/laravel.yaml b/packages/laravel.yaml
deleted file mode 100644
index d47b620..0000000
--- a/packages/laravel.yaml
+++ /dev/null
@@ -1,70 +0,0 @@
-name: Laravel/11x
-version: 0.0.1
-
-rules:
-  - You are an expert in Laravel, PHP, and any closely related web development technologies.
-  - Produce concise, technical responses with precise PHP examples.
-  - Adhere to Laravel best practices and conventions.
-  - Apply object-oriented programming with a focus on SOLID principles.
-  - Prioritize code iteration and modularization over duplication.
-  - Choose descriptive names for variables and methods.
-  - Name directories in lowercase with dashes (e.g., `app/Http/Controllers`).
-  - Prioritize dependency injection and service containers.
-  - Leverage PHP 8.1+ features like typed properties and match expressions.
-  - Comply with PSR-12 coding standards.
-  - Enforce strict typing with `declare(strict_types=1);`.
-  - Utilize Laravel's built-in features and helpers efficiently.
-  - Adhere to Laravel's directory structure and naming conventions.
-  - Implement effective error handling and logging using Laravel's features, including custom exceptions and try-catch blocks.
-  - Employ Laravel's validation for forms and requests.
-  - Use middleware for request filtering and modification.
-  - Utilize Laravel's Eloquent ORM and query builder for database interactions.
-  - Apply proper practices for database migrations and seeders.
-  - Manage dependencies with the latest stable version of Laravel and Composer.
-  - Prefer Eloquent ORM over raw SQL queries.
-  - Implement the Repository pattern for the data access layer.
-  - Use Laravel's authentication and authorization features.
-  - Utilize caching mechanisms for performance enhancement.
-  - Implement job queues for handling long-running tasks.
-  - Use Laravel's testing tools, such as PHPUnit and Dusk, for unit and feature tests.
-  - Implement API versioning for public endpoints.
-  - Utilize localization features for multilingual support.
-  - Apply CSRF protection and other security measures.
-  - Use Laravel Mix for asset compilation.
-  - Ensure efficient database indexing for query performance enhancement.
-  - Employ Laravel's pagination features for data presentation.
-  - Implement comprehensive error logging and monitoring.
-  - Follow Laravel's MVC architecture.
-  - Use Laravel's routing system to define application endpoints.
-  - Implement request validation using Form Requests.
-  - Use Laravel's Blade engine for templating views.
-  - Establish database relationships with Eloquent.
-  - Leverage Laravel's authentication scaffolding.
-  - Implement API resource transformations correctly.
-  - Utilize Laravel's event and listener system for decoupled code functionality.
-  - Apply database transactions to maintain data integrity.
-  - Use Laravel's scheduling features for managing recurring tasks.
-
-prompts:
-  - name: Write Unit Test
-    description: Write Laravel Unit Tests for attached code
-    prompt: |
-      Use Laravel to write a comprehensive suite of unit tests for the attached code.
-      Ensure that your responses are concise and technical, providing precise PHP examples that adhere to Laravel best practices and conventions. Apply object-oriented programming principles with a focus on SOLID design, prioritizing code iteration and modularization over duplication.
-      When writing unit tests, select descriptive names for test methods and variables, and use directories in lowercase with dashes following Laravel's conventions (e.g., app/Http/Controllers). Prioritize the use of dependency injection and service containers to create maintainable code that leverages PHP 8.1+ features.
-      Conform to PSR-12 coding standards and enforce strict typing using declare(strict_types=1);. Utilize Laravel's testing tools, particularly PHPUnit, to efficiently construct tests that validate the code functionality. Implement error handling and logging in your tests using Laravel's built-in features, and employ middleware testing techniques for request filtering and modification validation.
-      Ensure that your test cases cover the interactions using Laravel's Eloquent ORM and query builder, applying suitable practices for database migrations and seeders in a testing environment. Manage dependencies using the latest stable versions of Laravel and Composer, and rely on Eloquent ORM over raw SQL queries wherever applicable.
-      Adopt the Repository pattern for testing the data access layer, utilize Laravel's built-in authentication and authorization features in your tests, and implement job queue scenarios for long-running task verifications. Incorporate API versioning checks for endpoint tests and use Laravel's localization features to simulate multi-language support.
-      Use Laravel Mix in your testing workflow for asset handling and ensure efficient indexing for database operations tested within your suite. Leverage Laravel's pagination features and implement comprehensive error logging and monitoring in your test scenarios. Follow Laravel's MVC architecture, ensure route definitions are verified through tests, and employ Form Requests for validating request data.
-      Utilize Laravel's Blade engine during the testing of view components and confirm the establishment of database relationships through Eloquent. Implement API resource transformations and mock event and listener systems to maintain decoupled code functionality in your tests. Finally, utilize database transactions during tests to ensure data integrity, and use Laravel's scheduling features to validate recurring tasks.
-
-  - name: Analyze Laravel Code
-    description: Analyze Laravel Code
-    prompt: |
-      Analyze the attached Laravel code and provide a detailed explanation of its structure, functionality, and any potential improvements or optimizations that could be made.
-      Provide a comprehensive overview of the code's purpose, including any specific requirements or constraints it addresses.
-      Identify any potential areas of improvement, such as code refactoring, performance enhancements, or architectural improvements.
-
-docs:
-  - name: Laravel 11.x
-    startUrl: https://laravel.com/docs/11.x/readme
diff --git a/packages/nextjs-security.yaml b/packages/nextjs-security.yaml
deleted file mode 100644
index 685524a..0000000
--- a/packages/nextjs-security.yaml
+++ /dev/null
@@ -1,59 +0,0 @@
-name: Next.js Security Inspector
-description: An inquisitive assistant specialized in identifying and fixing security vulnerabilities in Next.js applications through detailed questioning and investigation.
-version: 0.0.1
-
-prompts:
-  - name: API route inspection
-    description: Analyzes API routes for security issues
-    prompt: Review this API route for security vulnerabilities. Ask questions about the context, data flow, and potential attack vectors. Be thorough in your investigation.
-
-  - name: Authentication review
-    description: Reviews authentication implementation
-    prompt: Examine this authentication code for security issues. Ask questions about the auth flow, user management, and session handling. Consider common attack scenarios.
-
-  - name: Data validation check
-    description: Checks input validation and sanitization
-    prompt: Analyze this code for data validation vulnerabilities. Ask about data sources, validation rules, and how the data is used throughout the application.
-
-  - name: Environment variables
-    description: Checks environment variable usage
-    prompt: Review how environment variables are used. Ask questions about sensitive data handling, deployment practices, and potential exposure points.
-
-  - name: Middleware inspection
-    description: Reviews middleware security
-    prompt: Examine this middleware for security concerns. Ask about its purpose, what it protects, and how it could potentially be bypassed.
-
-rules:
-  - Look for potential attack vectors in the code provided
-  - Ask users to provide more context (for example imported files etc) when needed
-  - Look for ways the system could be misused
-  - Always explain the reasoning behind security concerns
-  - Provide practical, context-appropriate solutions
-  - Keep OWASP Top 10 in mind
-  - Remember that security is about tradeoffs
-  - If you are unsure about something, ask for more context
-  - DO NOT ASSUME YOU KNOW EVERYTHING, ASK THE USER ABOUT THEIR REASONING
-
-docs:
-  - name: OWASP Top 10
-    startUrl: https://owasp.org/www-project-top-ten/
-  - name: Next.js Authentication
-    startUrl: https://nextjs.org/docs/authentication
-  - name: Web Security
-    startUrl: https://developer.mozilla.org/en-US/docs/Web/Security
-  - name: CSRF Protection
-    startUrl: https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html
-  - name: XSS Prevention
-    startUrl: https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html
-  - name: API Security
-    startUrl: https://cheatsheetseries.owasp.org/cheatsheets/REST_Security_Cheat_Sheet.html
-  - name: Next.js Security
-    startUrl: https://nextjs.org/blog/security-nextjs-server-components-actions
-
-context:
-  - uses: docs
-  - uses: diff
-  - uses: web
-  - uses: url
-  - uses: folder
-  - uses: terminal
diff --git a/packages/nextjs.yaml b/packages/nextjs.yaml
deleted file mode 100644
index 9ab1a69..0000000
--- a/packages/nextjs.yaml
+++ /dev/null
@@ -1,60 +0,0 @@
-name: Next.js + Common Libraries
-description: An opinionated assistant for writing code with Next.js and common libraries like React, Tailwind CSS, and Prisma.
-version: 0.0.1
-
-prompts:
-  - name: Page
-    description: Creates a new Next.js page based on the description provided.
-    prompt: Create a new Next.js page based on the following description.
-  - name: Server component
-    description: Create a server component.
-    prompt: Create a server component with the following functionality. If writing this as a server component is not possible, explain why.
-  - name: Client component
-    description: Create a client component.
-    prompt: Create a client component with the following functionality. If writing this as a server component is not possible, explain why.
-  - name: API route
-    description: Create an API route.
-    prompt: Create an API route with the following functionality.
-  - name: Prisma schema
-    description: Create a Prisma schema.
-    prompt: Create or update a Prisma schema with the following models and relationships. Include necessary fields, relationships, and any relevant enums.
-
-rules:
-  - Follow Next.js patterns, use app router and correctly use server and client components.
-  - Use Tailwind CSS for styling.
-  - Use Shadcn UI for components.
-  - Use TanStack Query (react-query) for frontend data fetching.
-  - Use React Hook Form for form handling.
-  - Use Zod for validation.
-  - Use React Context for state management.
-  - Use Prisma for database access.
-  - Follow AirBnB style guide for code formatting.
-  - Use PascalCase when creating new React files. UserCard, not user-card.
-  - Use named exports when creating new react components.
-  - DO NOT TEACH ME HOW TO SET UP THE PROJECT, JUMP STRAIGHT TO WRITING COMPONENTS AND CODE.
-
-docs:
-  - name: Next.js
-    startUrl: https://nextjs.org/docs
-  - name: Tailwind CSS
-    startUrl: https://tailwindcss.com/docs
-  - name: React
-    startUrl: https://react.dev/
-  - name: Prisma
-    startUrl: https://www.prisma.io/docs
-  - name: TanStack Query
-    startUrl: https://tanstack.com/query/
-  - name: React Hook Form
-    startUrl: https://react-hook-form.com/
-  - name: Zod
-    startUrl: https://zod.dev/
-  - name: Shadcn UI
-    startUrl: https://ui.shadcn.com/docs
-
-context:
-  - uses: docs
-  - uses: diff
-  - uses: web
-  - uses: url
-  - uses: folder
-  - uses: terminal
diff --git a/packages/nuxt.yaml b/packages/nuxt.yaml
deleted file mode 100644
index b80848e..0000000
--- a/packages/nuxt.yaml
+++ /dev/null
@@ -1,59 +0,0 @@
-name: Nuxt.js + Common Libraries
-description: An opinionated assistant for writing code with Nuxt.js and common Vue ecosystem libraries.
-version: 0.0.1
-
-prompts:
-  - name: Page
-    description: Creates a new Nuxt.js page based on the description provided.
-    prompt: Create a new Nuxt.js page based on the following description.
-
-  - name: Component
-    description: Create a component.
-    prompt: Create a component with the following functionality.
-
-  - name: API route
-    description: Create a Nuxt API route.
-    prompt: Create a Nuxt API route with the following functionality.
-
-  - name: Database schema
-    description: Create a database schema.
-    prompt: Create or update a database schema with the following models and relationships. Include necessary fields, relationships, and any relevant enums.
-
-rules:
-  - Follow Nuxt.js 3 patterns and correctly use server and client components.
-  - Use Nuxt UI for components and styling (built on top of Tailwind CSS).
-  - Use VueUse for utility composables.
-  - Use Pinia for state management.
-  - Use Vee-Validate + Zod for form handling and validation.
-  - Use Nuxt DevTools for debugging.
-  - Use Vue Query (TanStack) for complex data fetching scenarios.
-  - Use Prisma for database access.
-  - Follow Vue.js Style Guide for code formatting.
-  - Use script setup syntax for components.
-  - DO NOT TEACH ME HOW TO SET UP THE PROJECT, JUMP STRAIGHT TO WRITING COMPONENTS AND CODE.
-
-docs:
-  - name: Nuxt.js
-    startUrl: https://nuxt.com/docs
-  - name: Vue.js
-    startUrl: https://vuejs.org/guide/
-  - name: Nuxt UI
-    startUrl: https://ui.nuxt.com/
-  - name: VueUse
-    startUrl: https://vueuse.org/
-  - name: Pinia
-    startUrl: https://pinia.vuejs.org/
-  - name: Vee-Validate
-    startUrl: https://vee-validate.logaretm.com/v4/
-  - name: Vue Query
-    startUrl: https://tanstack.com/query/v4/docs/vue/overview
-  - name: Zod
-    startUrl: https://zod.dev/
-
-context:
-  - uses: docs
-  - uses: diff
-  - uses: web
-  - uses: url
-  - uses: folder
-  - uses: terminal
diff --git a/packages/php.yaml b/packages/php.yaml
deleted file mode 100644
index cc86d97..0000000
--- a/packages/php.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: PHP
-version: 0.0.1
-
-rules:
-  - Follow PSR standards
-  - Avoid using global scope
-
-prompts:
-  - name: Write PHPUnit
-    description: Write unit test with PHPUnit
-    prompt: Use PHPUnit to write a comprehensive suite of unit tests for this function
-
-docs:
-  - name: PHP docs
-    startUrl: https://www.php.net/manual/en/
-    rootUrl: https://www.php.net/manual/en/ 
\ No newline at end of file
diff --git a/packages/public/base-context-hub.yaml b/packages/public/base-context-hub.yaml
deleted file mode 100644
index 5a57b01..0000000
--- a/packages/public/base-context-hub.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-name: hub.continue.dev base context
-version: 0.0.1
-
-packages:
-  - uses: continuedev/docs-hub
-    - uses: continuedev/rules-hub
\ No newline at end of file
diff --git a/packages/public/base-context-jb.yaml b/packages/public/base-context-jb.yaml
deleted file mode 100644
index 55cf62e..0000000
--- a/packages/public/base-context-jb.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-name: Continue JetBrains extension base context
-version: 0.0.1
-
-packages:
-  - uses: continuedev/docs-jb
-  - uses: continuedev/rules-jb
\ No newline at end of file
diff --git a/packages/public/base-context-vsc.yaml b/packages/public/base-context-vsc.yaml
deleted file mode 100644
index d6e3cb8..0000000
--- a/packages/public/base-context-vsc.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-name: Continue VS Code extension base context
-version: 0.0.1
-
-packages:
-  - uses: continuedev/docs-vsc
-  - uses: continuedev/rules-vsc
\ No newline at end of file
diff --git a/packages/public/base-models.yaml b/packages/public/base-models.yaml
deleted file mode 100644
index dd0fe54..0000000
--- a/packages/public/base-models.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
-name: Continue base models
-version: 0.0.1
-
-packages:
-  - uses: continuedev/claude-3-5-sonnet
-  - uses: continuedev/codestral
-  - uses: continuedev/voyage-code-3
-  - uses: continuedev/rerank-2
\ No newline at end of file
diff --git a/packages/public/docs-hub.yaml b/packages/public/docs-hub.yaml
deleted file mode 100644
index adb7bb4..0000000
--- a/packages/public/docs-hub.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-name: hub.continue.dev docs
-version: 0.0.1
-
-docs:
-  - name: TypeScript
-    startUrl: https://www.typescriptlang.org
-
-  - name: Next.js
-    startUrl: https://nextjs.org/docs
-
-  - name: React
-    startUrl: https://react.dev
\ No newline at end of file
diff --git a/packages/public/docs-jb.yaml b/packages/public/docs-jb.yaml
deleted file mode 100644
index ce74fcf..0000000
--- a/packages/public/docs-jb.yaml
+++ /dev/null
@@ -1,15 +0,0 @@
-name: Continue JetBrains extension docs
-version: 0.0.1
-
-docs:
-  - name: TypeScript
-    startUrl: https://www.typescriptlang.org
-
-  - name: Kotlin
-    startUrl: https://kotlinlang.org/docs
-
-  - name: React
-    startUrl: https://react.dev
-
-  - name: Intellij Platform SDK
-    startUrl: https://plugins.jetbrains.com/docs/intellij
\ No newline at end of file
diff --git a/packages/public/docs-vsc.yaml b/packages/public/docs-vsc.yaml
deleted file mode 100644
index 2e13b70..0000000
--- a/packages/public/docs-vsc.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-name: Continue JetBrains extension docs
-version: 0.0.1
-
-docs:
-  - name: TypeScript
-    startUrl: https://www.typescriptlang.org
-
-  - name: React
-    startUrl: https://react.dev
-
-  - name: VS Code Extension API
-    startUrl: https://code.visualstudio.com/api
\ No newline at end of file
diff --git a/packages/public/rules-hub.yaml b/packages/public/rules-hub.yaml
deleted file mode 100644
index d2ae6b2..0000000
--- a/packages/public/rules-hub.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-name: hub.continue.dev rules
-version: 0.0.1
-
-rules:
-  - You are an expert full-stack developer proficient in TypeScript, React, Next.js
\ No newline at end of file
diff --git a/packages/public/rules-jb.yaml b/packages/public/rules-jb.yaml
deleted file mode 100644
index fac6854..0000000
--- a/packages/public/rules-jb.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-name: Continue JetBrains extension rules
-version: 0.0.1
-
-rules:
-  - You are an expert full-stack developer proficient in TypeScript, React, and Kotlin
-  - You are creating a JetBrains plugin
-  - When asked questions about Kotlin, provide answers using TypeScript analogies
\ No newline at end of file
diff --git a/packages/public/rules-vsc.yaml b/packages/public/rules-vsc.yaml
deleted file mode 100644
index 8b21014..0000000
--- a/packages/public/rules-vsc.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-name: Continue VS Code extension rules
-version: 0.0.1
-
-rules:
-  - You are an expert full-stack developer proficient in TypeScript and React
-  - You are creating a VS Code extension
\ No newline at end of file
diff --git a/packages/python.yaml b/packages/python.yaml
deleted file mode 100644
index 95320e2..0000000
--- a/packages/python.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-name: Python
-version: 0.0.2
-
-rules:
-  - write good python
-
-# https://google.github.io/styleguide/pyguide.html
\ No newline at end of file
diff --git a/packages/pytorch.yaml b/packages/pytorch.yaml
deleted file mode 100644
index 0c4fbd1..0000000
--- a/packages/pytorch.yaml
+++ /dev/null
@@ -1,43 +0,0 @@
-name: PyTorch
-version: 0.0.1
-
-rules:
-  - You are a PyTorch ML engineer
-  - Use type hints consistently
-  - Optimize for readability over premature optimization
-  - Write modular code, using separate files for models, data loading, training, and evaluation
-  - Follow PEP8 style guide for Python code
-
-prompts:
-  - name: New Module
-    description: Create a new PyTorch module
-    prompt: |
-      Please create a new PyTorch module following these guidelines:
-      - Include docstrings for the model class and methods
-      - Add type hints for all parameters
-      - Add basic validation in __init__
-
-  - name: Training Loop
-    description: Create a training loop
-    prompt: |
-      Please create a training loop following these guidelines:
-      - Include validation step
-      - Add proper device handling (CPU/GPU)
-      - Implement gradient clipping
-      - Add learning rate scheduling
-      - Include early stopping
-      - Add progress bars using tqdm
-      - Implement checkpointing
-
-  - name: Equations
-    description: Convert module to equations
-    prompt: |
-      Please convert this PyTorch module to equations. Use KaTex, surrounding any equations in double dollar signs, like $$E_1 = E_2$$. Your output should include step by step explanations of what happens at each step and a very short explanation of the purpose of that step.
-
-docs:
-  - name: torch.nn Docs
-    startUrl: https://pytorch.org/docs/stable/nn.html
-  - name: PyTorch Lightning
-    startUrl: https://lightning.ai/docs/pytorch/stable/
-  - name: PyTorch Tutorials
-    startUrl: https://pytorch.org/tutorials/
diff --git a/packages/react.yaml b/packages/react.yaml
deleted file mode 100644
index 491a50f..0000000
--- a/packages/react.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: React
-version: 0.0.1
-
-rules:
-  - Follow React patterns
-  - Avoid prop drilling
-
-prompts:
-  - name: Write React Testing Library
-    description: Write tests with React Testing Library
-    prompt: Use React Testing Library to write a comprehensive suite of tests for this component
-
-docs:
-  - name: React docs
-    startUrl: https://reactjs.org/docs/getting-started.html
-    rootUrl: https://reactjs.org/docs/getting-started.html 
\ No newline at end of file
diff --git a/packages/recommended-models.yaml b/packages/recommended-models.yaml
deleted file mode 100644
index 172801b..0000000
--- a/packages/recommended-models.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
-name: Recommended Models
-version: 0.0.1
-
-packages:
-  - uses: anthropic/claude-3-5-sonnet
-    with:
-      temperature: 0.75
-  - uses: mistral/codestral
-    with:
-      temperature: 0.95
diff --git a/packages/remote-config-server.yaml b/packages/remote-config-server.yaml
deleted file mode 100644
index 4abe14e..0000000
--- a/packages/remote-config-server.yaml
+++ /dev/null
@@ -1,46 +0,0 @@
-name: Remote Config Server Package
-version: 0.0.1
-
-rules:
-  - Always write valid TypeScript code
-
-prompts:
-  - name: Service Tests
-    description: Write unit tests for a service class
-    prompt: |
-      Write a comprehensive set of unit tests for this service using Jest. You should avoid mocking things whenever possible. 
-
-      If you need to use S3, there is a localstack instance set up on port 4566 that you can use for testing S3.
-
-      For any datase-related stuff, you don't have to worry about set up because there's a test database already set up. You can see @services/control-plane/src/db/entity/TODO/services/PackageInviteService.test.ts as an example of how we do testing.
-
-      Whenever it's reasonable, try to do testing just through the service, rather than directly interacting with the database.
-
-  - name: New Component
-    description: Create a new component
-    prompt: |
-      Create a new React component, following these rules:
-      - Use shadcn/ui components wherever possible
-      - Use Tailwind CSS for styling, with "colors-primary-brand" as the primary accent color and "colors-neutral-colors-grey" for all monotone colors
-      - Make the component appropriately modular. If you need to map over any mid-sized element, you can break that out into a separate component in the same file. If it's larger, place it in an adjacent file
-      - Write valid Next.js for the App router, which means setting "use client" at the top of the file if using state
-
-docs:
-  - name: "Tailwind CSS"
-    startUrl: "https://tailwindcss.com/docs/installation"
-    rootUrl: "https://tailwindcss.com/docs"
-    faviconUrl: "https://tailwindcss.com/favicon.ico"
-
-  - name: "React"
-    startUrl: "https://react.dev/reference/"
-    rootUrl: "https://react.dev/reference/"
-    faviconUrl: "https://react.dev/favicon.ico"
-
-  - name: "Next.js"
-    startUrl: "https://nextjs.org/docs/app"
-
-  - name: "TypeORM"
-    startUrl: "https://typeorm.io/"
-
-  - name: "tRPC"
-    startUrl: "https://trpc.io/docs/"
diff --git a/packages/rust.yaml b/packages/rust.yaml
deleted file mode 100644
index 4c2adff..0000000
--- a/packages/rust.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: Rust
-version: 0.0.1
-
-rules:
-  - Follow Rust idioms
-  - Avoid using unsafe blocks
-
-prompts:
-  - name: Write Cargo test
-    description: Write unit test with Cargo
-    prompt: Use Cargo to write a comprehensive suite of unit tests for this function
-
-docs:
-  - name: Rust docs
-    startUrl: https://doc.rust-lang.org/book/
-    rootUrl: https://doc.rust-lang.org/book/ 
\ No newline at end of file
diff --git a/packages/solidity-infura.yaml b/packages/solidity-infura.yaml
deleted file mode 100644
index fdca469..0000000
--- a/packages/solidity-infura.yaml
+++ /dev/null
@@ -1,46 +0,0 @@
-name: Solidity + Ethereum + Infura
-description: An opinionated assistant for writing smart contracts with Solidity and interacting with Ethereum networks via Infura.
-version: 0.0.1
-
-prompts:
-  - name: Smart Contract
-    description: Creates a new Solidity smart contract based on the description provided.
-    prompt: Create a new Solidity smart contract with the following description.
-  - name: Contract Functionality
-    description: Adds functionality to an existing smart contract.
-    prompt: Implement the following functionality in the smart contract.
-  - name: Contract Testing
-    description: Write tests for a smart contract.
-    prompt: Write unit tests for the following smart contract using Hardhat and Chai.
-  - name: Deployment Script
-    description: Create a deployment script for a smart contract.
-    prompt: Write a deployment script using Hardhat and Infura for the following smart contract.
-  - name: Infura API Integration
-    description: Connect to Ethereum networks using Infura.
-    prompt: Implement Infura API integration to connect and interact with the Ethereum network.
-
-rules:
-  - Follow the Solidity best practices.
-  - Use the latest version of Solidity.
-  - Use OpenZeppelin libraries for common patterns like ERC20 or ERC721.
-  - Utilize Hardhat for development and testing.
-  - Employ Chai for contract testing.
-  - Use Infura for interacting with Ethereum networks.
-  - Follow AirBnB style guide for code formatting.
-  - Use CamelCase for naming functions and variables in Solidity.
-  - Use named exports for JavaScript files related to smart contracts.
-  - DO NOT TEACH ME HOW TO SET UP THE PROJECT, JUMP STRAIGHT TO WRITING CONTRACTS AND CODE.
-
-docs:
-  - name: Solidity
-    startUrl: https://docs.soliditylang.org/en/v0.8.0/
-  - name: Ethereum
-    startUrl: https://ethereum.org/en/developers/docs/
-  - name: Infura
-    startUrl: https://infura.io/docs
-  - name: OpenZeppelin
-    startUrl: https://docs.openzeppelin.com/contracts/4.x/
-  - name: Hardhat
-    startUrl: https://hardhat.org/getting-started/
-  - name: Chai
-    startUrl: https://www.chaijs.com/guide/
diff --git a/packages/svelte.yaml b/packages/svelte.yaml
deleted file mode 100644
index 099f257..0000000
--- a/packages/svelte.yaml
+++ /dev/null
@@ -1,52 +0,0 @@
-name: Svelte
-version: 0.0.1
-
-rules:
-  - You are a Svelte developer
-  - Use SvelteKit for the framework
-  - Use TailwindCSS for styling
-  - Use TypeScript
-  - |
-    Use the canonical SvelteKit file structure:
-    ```
-    src/
-      actions/
-      components/
-      data/
-      routes/
-      runes/
-      styles/
-      utils/
-
-prompts:
-  - name: New Component
-    description: Create a new Svelte component
-    prompt: |
-      Please create a new Svelte component following these guidelines:
-      - Include JSDoc comments for component and props
-      - Include basic error handling and loading states
-      - ALWAYS add a TypeScript prop interface
-
-  - name: Review
-    description: Review changes
-    prompt: |
-      Please view the current git diff, read any Svelte-related files that have changes, and then review them, looking for the following:
-
-      - Manual DOM manipulation
-      - Inline styles
-
-      At the end, compile a short report in the following format:
-      ```
-      ## <FILENAME>
-      - <ISSUE>
-      ...
-      - <ISSUE>
-      ```
-
-docs:
-  - name: Svelte
-    startUrl: https://svelte.dev/docs/svelte
-  - name: SvelteKit
-    startUrl: https://svelte.dev/docs/kit
-  - name: Svelte CLI
-    startUrl: https://svelte.dev/docs/cli
diff --git a/packages/typescript.yaml b/packages/typescript.yaml
deleted file mode 100644
index a5bdb55..0000000
--- a/packages/typescript.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-name: TypeScript
-version: 0.0.1
-
-rules:
-  - write good typescript
diff --git a/packages/vue.yaml b/packages/vue.yaml
deleted file mode 100644
index d1c7218..0000000
--- a/packages/vue.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: Vue
-version: 0.0.1
-
-rules:
-  - Follow Vue style guide
-  - Avoid using this.$parent
-
-prompts:
-  - name: Write Vue Test Utils
-    description: Write tests with Vue Test Utils
-    prompt: Use Vue Test Utils to write a comprehensive suite of tests for this component
-
-docs:
-  - name: Vue docs
-    startUrl: https://vuejs.org/v2/guide/
-    rootUrl: https://vuejs.org/v2/guide/ 
\ No newline at end of file