feature: Initial commit

This commit is contained in:
Keith Solomon
2025-06-21 10:16:47 -05:00
commit 2ba39a92ea
4 changed files with 55 additions and 0 deletions

2
.gitignore vendored Normal file
View File

@@ -0,0 +1,2 @@
node_modules/

8
.vscode/settings.json vendored Normal file
View File

@@ -0,0 +1,8 @@
{
"workbench.colorCustomizations": {
"tree.indentGuidesStroke": "#3d92ec",
"activityBar.background": "#0B3516",
"titleBar.activeBackground": "#104A1F",
"titleBar.activeForeground": "#F4FDF6"
}
}

Binary file not shown.

After

Width:  |  Height:  |  Size: 40 KiB

View File

@@ -0,0 +1,45 @@
# Prompt Catalog
- June 21, 2025: Initial planning
## Overview & Purpose
The Prompt Catalog is a centralized repository for prompts used in various applications, such as AI models or chatbots. It aims to provide a structured way to store, search, and categorize prompts for easy access and management. It will serve as a comprehensive and user-friendly catalog of prompts that can be easily searched, categorized, and tagged, enhancing the usability and discoverability of prompts for developers and users alike.
## Features
- **Storage**: Store prompts, metadata, and (future) users in Supabase (self-hosted or cloud).
- **Prompt Metadata**: Include metadata for each prompt:
- Type (System, Task)
- Title
- Description
- Tags
- Creation date
- Last modified date
- **Categorization**: Organize prompts into types (System, Tasks) for easier navigation.
- **Tagging System**: Use tags to describe prompts for better filtering.
- **Search Functionality**: Quickly find prompts by keywords or tags.
## Technical Details
- **Web Interface**: A user-friendly web interface to view, search, and manage prompts.
- See `Front End Interface.png` for mockup.
- **Database**: Use Supabase for storing prompts and metadata.
- Tables:
- `prompts`: Stores prompt details (id, type, title, description, tags, created_at, updated_at).
- `users`: (Future) Stores user information (id, username, email, created_at).
- `user_prompts`: (Future) Stores user contributions and favorites (user_id, prompt_id, created_at).
- **Authentication**: Implement user authentication for future features (e.g., user profiles, contributions).
- **Deployment**: Host the application on a platform like Vercel or Netlify for the front end, and Supabase for the backend.
- **Front End**: Use a modern JavaScript framework (e.g., React, Vue) for the web interface.
- **Back End**: Use Supabase's built-in API for database interactions.
## Future Enhancements
- **User Profiles**: Create profiles for users to manage their contributions and favorites.
- **User Contributions**: Allow users to submit their own prompts to the catalog.
- **Favorites**: Users can mark prompts as favorites for easy access later.
- **Rating System**: Rate prompts to help others find the best ones.
- **Version Control**: Track changes to prompts over time.
- **API Access**: Provide an API for external applications to access the catalog.
- **Sharing**: Enable sharing of prompts via links or social media.