feat: add LanceDB vector store with upsert, delete, and search
This commit is contained in:
26
sample-data/Default/Side Project/Agency/Prompt.md
Normal file
26
sample-data/Default/Side Project/Agency/Prompt.md
Normal file
@@ -0,0 +1,26 @@
|
||||
You are an Agentic [[Concept/AI Coding agent]] architect. You are a seasoned [[Concept/AI]] professional with apex level experience in prompt engineering and agent creation.
|
||||
|
||||
Here is a project - a repository of agents.
|
||||
|
||||
Your tasks:
|
||||
1. Read README.md to understand and overview of this project.
|
||||
2. Create a super agent - a master coordinator agent. That agent must be able to intelligently delegate tasks to existing agents.
|
||||
1. You will create the Super Agent file - boss.md in the project root.
|
||||
2. You will create the delegation logic based on the description of other agents.
|
||||
3. The agent boss will be a primary agent.
|
||||
4. Once the subagent finishes the task, the subagen will report back to the Boss.
|
||||
5. Boss must be accountable for the delegated tasks.
|
||||
|
||||
3. Evaluate the bash scripts under ./scripts. boss.md must be included in the installed package.
|
||||
|
||||
Guardrail:
|
||||
|
||||
1. Do not do operations in a heist.
|
||||
2. Commit the necessary memory to engram using the available mcp.
|
||||
3. compact, go back and read the readme or any relevant files if you think you are begining to hallucinate.
|
||||
|
||||
|
||||
Ask me any clarifications before proceeding.
|
||||
|
||||
|
||||
Analyze the current project. I want to add a new agent "Boss". Responsibility of Boss is to be a primary agent. Boss must know capabilities and specialties of each of the other agents available. They should have a clear plan to delegate work to the right agent by understanding the intend of the prompt, and based on specialty and capability of other agents. Boss must also review the completed work from agents. As required, verification/truth seeking agents must be spawned to validate deep specialty tasks. Learn the way other agents are written. It should follow the same level or better level of detailing. Let us discuss any open questions before continuing with the task.
|
||||
@@ -0,0 +1,186 @@
|
||||
## 1. User & Account Management
|
||||
|
||||
- **User Registration & Login**
|
||||
- Standard email/password sign-up or sign-in.
|
||||
- OAuth or social logins (currently Are.na offers email-based sign-up with optional Slack login).
|
||||
- **User Profiles**
|
||||
- Basic profile info (name, bio, avatar).
|
||||
- Public view of user’s channels.
|
||||
- Option to follow other users (or “friends” on Are.na) to see what they’re creating.
|
||||
- **Membership Tiers**
|
||||
- **Free Tier**: Limited number of private channels (public channels are unlimited).
|
||||
- **Paid Tier (“Premium”)**: Unlimited private channels, advanced organizational features, or priority support.
|
||||
- **Notifications Settings**
|
||||
- Email notifications for channel collaborations or new followers.
|
||||
- Option to turn off notifications for minimal distraction.
|
||||
|
||||
---
|
||||
|
||||
## 2. Channels (Boards / Collections)
|
||||
|
||||
- **Creating & Naming Channels**
|
||||
|
||||
- Each channel represents a collection of content blocks around a theme.
|
||||
- Title and optional description.
|
||||
- Channel cover image can be generated from the channel’s contents or uploaded.
|
||||
- **Privacy Settings**
|
||||
|
||||
- **Public Channels**: Visible to anyone on Are.na or shared via a public link.
|
||||
- **Private Channels**: Visible only to channel collaborators or by direct invitation.
|
||||
- **Channel Organization & Display**
|
||||
|
||||
- **List View** or **Grid View**: Blocks can be displayed in a linear list or a more visual grid.
|
||||
- **Reordering Blocks**: Users can drag-and-drop or reorder blocks manually.
|
||||
- **Search & Filtering**: Within a channel, users can search text in blocks and filter by block type (image, link, text, etc.).
|
||||
- **Collaboration**
|
||||
|
||||
- Add collaborators with different permissions (edit or view-only).
|
||||
- Multiple users can add/remove blocks, rename the channel, or reorder content.
|
||||
- **Channel Discovery & Browsing**
|
||||
|
||||
- Public channels can appear in Are.na’s “Explore” or search results.
|
||||
- Users can follow channels to see updates (new blocks added).
|
||||
|
||||
---
|
||||
|
||||
## 3. Blocks (Content Units)
|
||||
|
||||
- **Block Creation**
|
||||
|
||||
- **Supported Types**: Links (URLs), Text (notes), Images, PDFs (files), Videos (linked or uploaded), Audio (linked or uploaded), and more.
|
||||
- Each block can have a title and a descriptive note.
|
||||
- **Editing & Metadata**
|
||||
|
||||
- Users can edit the title/description of the block.
|
||||
- For link blocks, Are.na often auto-fetches metadata (like a page title or thumbnail).
|
||||
- For image/file blocks, Are.na stores the file and provides an in-app viewer.
|
||||
- **Connecting Blocks Across Channels**
|
||||
|
||||
- A single block can “live” in multiple channels—this is a key feature.
|
||||
- Users can “connect” an existing block from one channel to another without duplicating it, so any updates are seen everywhere.
|
||||
- **Block-Level Interactions**
|
||||
|
||||
- Commenting on a block (recent addition in some forms of Are.na).
|
||||
- View block “source” or original link.
|
||||
- Explore “connections”: see which other channels the same block appears in.
|
||||
|
||||
---
|
||||
|
||||
## 4. Linking & Networked Structure
|
||||
|
||||
- **Network View / Graph-Like Features**
|
||||
|
||||
- Are.na emphasizes the idea that blocks are not siloed. They can link to multiple channels, and channels can link to each other.
|
||||
- Some visualizations or third-party apps may display these connections in a graph-like form.
|
||||
- **Content Discovery via Connections**
|
||||
|
||||
- From a block’s detail page, you can see all channels it’s connected to, effectively letting you “hop” from one channel to another, discovering related content.
|
||||
|
||||
---
|
||||
|
||||
## 5. Search & Explore
|
||||
|
||||
- **Global Search**
|
||||
|
||||
- Search for blocks, channels, or users across the entire platform.
|
||||
- Filters by block type, user, or keywords.
|
||||
- **Explore / Discover Pages**
|
||||
|
||||
- Are.na’s home or “Explore” section highlights interesting public channels and blocks.
|
||||
- Users can browse trending or curated collections.
|
||||
|
||||
---
|
||||
|
||||
## 6. Collaboration & Social Features
|
||||
|
||||
- **Collaborative Channels**
|
||||
|
||||
- Invite other users to contribute blocks.
|
||||
- Group channels for teams or classes to collect shared research.
|
||||
- **Following & Feeds**
|
||||
|
||||
- Follow individual users or specific channels.
|
||||
- A minimal feed that shows new blocks added to the channels you follow (Are.na is intentionally minimal—there’s no “like” button or algorithmic feed).
|
||||
- **Slack Integration**
|
||||
|
||||
- Some teams integrate Are.na with Slack to share updates or new blocks automatically.
|
||||
- Basic push notifications or auto-posts of channel changes.
|
||||
|
||||
---
|
||||
|
||||
## 7. Minimal, Ad-Free Design Philosophy
|
||||
|
||||
- **No Ads, No Likes**
|
||||
|
||||
- The platform is subscription-supported and does not display advertisements.
|
||||
- There is no “Like” button or popularity metrics (e.g., follower counts are hidden or minimized).
|
||||
- **Focus on Content & Research**
|
||||
|
||||
- Clean, grid-based or linear layout.
|
||||
- Soft color palette, minimal UI elements.
|
||||
- Encourages calm, focused interaction.
|
||||
|
||||
---
|
||||
|
||||
## 8. Cross-Platform & API
|
||||
|
||||
- **Web Application**
|
||||
|
||||
- Main usage is via a responsive web interface that works on desktop or mobile.
|
||||
- **Mobile Apps**
|
||||
|
||||
- Are.na has an official iOS app with basic channel and block management features.
|
||||
- (As of now, no official Android app, but the web interface is mobile-friendly.)
|
||||
- **Browser Extensions**
|
||||
|
||||
- Official or third-party bookmarklet/extension to quickly add new blocks (links or images) from around the web.
|
||||
- **REST API**
|
||||
|
||||
- Are.na has a documented API for programmatic access to blocks, channels, and user data.
|
||||
- Enables building custom integrations or automations (e.g., hooking up a design workflow).
|
||||
|
||||
---
|
||||
|
||||
## 9. Monetization & Sustainability
|
||||
|
||||
- **Subscription Model**
|
||||
|
||||
- Free accounts: Limited to a certain number of private blocks/channels. Public channels are unlimited.
|
||||
- Paid accounts: Unlimited private channels, possibly higher upload/file size limits.
|
||||
- **Community Support**
|
||||
|
||||
- Are.na fosters a community of artists, researchers, and designers who value the platform’s collaborative features. This community spirit is part of the product’s draw.
|
||||
|
||||
---
|
||||
|
||||
## 10. Common Use Cases
|
||||
|
||||
1. **Creative Research/Moodboarding**: Designers or artists gather visual references in a “channel,” connecting images, articles, or files in one place.
|
||||
2. **Academic or Professional Research**: Teams or study groups collect and annotate reading materials or references (links, PDFs).
|
||||
3. **Personal Knowledge Base**: Individuals build channels for different topics or ideas, linking them in a network.
|
||||
4. **Collaborative Brainstorming**: Multiple contributors add blocks to a shared channel, building a collective library of resources.
|
||||
|
||||
---
|
||||
|
||||
### Key Takeaways
|
||||
|
||||
1. **“Blocks” + “Channels”**: The core metaphor is quite simple—channels (collections) contain blocks (pieces of content). But the **ability to connect blocks across channels** gives Are.na a unique, networked nature.
|
||||
2. **Minimal Social Features**: Focus on curation and idea organization, rather than viral growth or engagement metrics.
|
||||
3. **Privacy Controls**: Clear distinction between public and private channels, with collaboration options.
|
||||
4. **API & Integrations**: The REST API and potential Slack integration are important for a modern, extensible platform.
|
||||
5. **Monetization**: Subscription model focusing on private channel limits and storage.
|
||||
|
||||
If you’re aiming to replicate Are.na’s functionality, consider which parts are most essential to your project. It might be the “network of blocks” concept, the minimalist approach, or the collaborative curation aspect. Each of these has specific **technical** and **UX** implications—especially around data modeling (e.g., how you store and connect “blocks” to multiple “channels”) and the front-end interface (grid vs. list, drag-and-drop, search filtering, etc.).
|
||||
|
||||
---
|
||||
|
||||
### Next Steps
|
||||
|
||||
- **Define Your Core Feature Set**: You don’t necessarily need every Are.na feature from day one. Focus on what matters most—perhaps block connectivity, minimal design, or offline collaboration.
|
||||
- **Choose Technology Stack**: For a custom build, you might use a headless CMS (e.g., **Strapi**, **Directus**) or a backend+frontend approach with **Node.js**, **Django**, **Rails**, etc.
|
||||
- **Sketch Data Models**: Figure out how you’ll store “blocks,” “channels,” user permissions, and the relationships between them.
|
||||
- **Plan for Collaboration & Real-Time**: If real-time collaboration (multiple users editing simultaneously) is needed, consider WebSockets or a real-time database (like Firebase or Supabase).
|
||||
|
||||
---
|
||||
|
||||
By reviewing this comprehensive feature list, you can choose which parts of Are.na’s functionality align with your vision and then tailor your custom build accordingly. Good luck with your project!
|
||||
@@ -0,0 +1,17 @@
|
||||
---
|
||||
category: ai
|
||||
date_added: 2026-04-12
|
||||
due_date:
|
||||
---
|
||||
|
||||
# Project Idea: [[Concept/English Style Converter]]
|
||||
|
||||
**Concept:** A system that takes a normal [[Concept/English]] sentence and converts it into various different [[Concept/English]] styles and tones.
|
||||
|
||||
**Potential Features:**
|
||||
- **Style Options:** Sarcasm, Formal, Casual, Academic, Poetic, etc.
|
||||
- **Input:** User provides a standard sentence.
|
||||
- **Output:** The sentence rewritten in the selected style(s).
|
||||
- **Customization:** Ability to toggle levels of formality or intensity of sarcasm.
|
||||
|
||||
**Source:** User prompt via image/text on 2026-04-12.
|
||||
206
sample-data/Default/Side Project/Onyxlog/Notes.md
Normal file
206
sample-data/Default/Side Project/Onyxlog/Notes.md
Normal file
@@ -0,0 +1,206 @@
|
||||
To ensure your Laravel backend is highly scalable, enterprise-ready, and equipped for logging, troubleshooting, and performance tuning, consider adding the following packages. These tools will help maintain a robust, maintainable, and performant application:
|
||||
|
||||
---
|
||||
|
||||
### **1. Logging and Monitoring**
|
||||
|
||||
#### **a. Laravel Telescope**
|
||||
|
||||
- **Purpose**: Debugging and monitoring requests, queries, and exceptions.
|
||||
- **Why?** Provides a detailed view of application behavior for developers.
|
||||
- **Install**: `composer require laravel/telescope`
|
||||
|
||||
#### **b. Monolog**
|
||||
|
||||
- **Purpose**: Advanced logging capabilities with various handlers.
|
||||
- **Why?** Allows integration with external logging systems like Elastic Stack, Sentry, or Papertrail.
|
||||
- **Install**: Already included in Laravel (`Illuminate\Log`).
|
||||
|
||||
#### **c. Sentry**
|
||||
|
||||
- **Purpose**: Real-time error tracking and performance monitoring.
|
||||
- **Why?** Notifies you about errors and gives stack traces, improving troubleshooting.
|
||||
- **Install**: `composer require sentry/sentry-laravel`
|
||||
|
||||
#### **d. Laravel Log Viewer**
|
||||
|
||||
- **Purpose**: A UI to view and manage logs directly in the application.
|
||||
- **Why?** Simplifies debugging by offering a user-friendly interface for log analysis.
|
||||
- **Install**: `composer require rap2hpoutre/laravel-log-viewer`
|
||||
|
||||
---
|
||||
|
||||
### **2. Performance Tuning**
|
||||
|
||||
#### **a. Laravel Octane**
|
||||
|
||||
- **Purpose**: Improves performance with high-concurrency servers like Swoole or RoadRunner.
|
||||
- **Why?** Enhances the scalability and speed of your application.
|
||||
- **Install**: `composer require laravel/octane`
|
||||
|
||||
#### **b. Spatie Laravel Response Cache**
|
||||
|
||||
- **Purpose**: Caches responses to reduce redundant processing for identical requests.
|
||||
- **Why?** Speeds up response times for read-heavy endpoints.
|
||||
- **Install**: `composer require spatie/laravel-responsecache`
|
||||
|
||||
#### **c. Clockwork**
|
||||
|
||||
- **Purpose**: Profiling and performance monitoring in development.
|
||||
- **Why?** Provides deep insights into query execution, routes, and memory usage.
|
||||
- **Install**: `composer require itsgoingd/clockwork`
|
||||
|
||||
---
|
||||
|
||||
### **3. Database Optimization**
|
||||
|
||||
#### **a. Laravel Debugbar**
|
||||
|
||||
- **Purpose**: Debug queries, memory usage, and performance metrics.
|
||||
- **Why?** Helps identify and resolve inefficient database queries.
|
||||
- **Install**: `composer require barryvdh/laravel-debugbar --dev`
|
||||
|
||||
#### **b. Eloquent Filter**
|
||||
|
||||
- **Purpose**: Dynamic filtering for Eloquent models.
|
||||
- **Why?** Simplifies query filters for better readability and performance.
|
||||
- **Install**: `composer require mehnatfar/eloquent-filter`
|
||||
|
||||
#### **c. Spatie Query Builder**
|
||||
|
||||
- **Purpose**: Simplifies building RESTful APIs with filters, sorting, and includes.
|
||||
- **Why?** Ensures consistent and optimized database queries.
|
||||
- **Install**: `composer require spatie/laravel-query-builder`
|
||||
|
||||
---
|
||||
|
||||
### **4. Scalability and Job Management**
|
||||
|
||||
#### **a. Laravel Horizon**
|
||||
|
||||
- **Purpose**: Monitors and manages queues with a user-friendly dashboard.
|
||||
- **Why?** Useful for tracking job performance and retrying failed jobs.
|
||||
- **Install**: `composer require laravel/horizon`
|
||||
|
||||
#### **b. Laravel Scout**
|
||||
|
||||
- **Purpose**: Adds full-text search capabilities via services like Elasticsearch or Algolia.
|
||||
- **Why?** Scales well for applications requiring advanced search functionality.
|
||||
- **Install**: `composer require laravel/scout`
|
||||
|
||||
#### **c. Laravel Redis**
|
||||
|
||||
- **Purpose**: High-performance caching and session management using Redis.
|
||||
- **Why?** Handles heavy loads with low latency.
|
||||
- **Install**: Already integrated into Laravel with Redis as an option (`composer require predis/predis` for Predis).
|
||||
|
||||
---
|
||||
|
||||
### **5. Security and Privacy**
|
||||
|
||||
#### **a. Laravel Sanctum**
|
||||
|
||||
- **Purpose**: Authentication for SPA, mobile apps, and token-based APIs.
|
||||
- **Why?** Lightweight and ideal for secure user authentication.
|
||||
- **Install**: `composer require laravel/sanctum`
|
||||
|
||||
#### **b. Spatie Laravel Permissions**
|
||||
|
||||
- **Purpose**: Role and permission management.
|
||||
- **Why?** Simplifies access control logic in enterprise applications.
|
||||
- **Install**: `composer require spatie/laravel-permission`
|
||||
|
||||
#### **c. Laravel Security Checker**
|
||||
|
||||
- **Purpose**: Scans your application for vulnerabilities.
|
||||
- **Why?** Ensures libraries and dependencies are secure.
|
||||
- **Install**: `composer require enlightn/security-checker`
|
||||
|
||||
---
|
||||
|
||||
### **6. Multi-Tenancy**
|
||||
|
||||
#### **a. Hyn Laravel Tenancy** (Deprecated, use Spatie's or native implementation)
|
||||
|
||||
- **Purpose**: Multi-tenancy support for database and application separation.
|
||||
- **Alternative**: Use the official Laravel database tenancy patterns.
|
||||
- **Modern Approach**: Spatie's Laravel Multi-Tenant package (`composer require spatie/laravel-multitenancy`).
|
||||
|
||||
---
|
||||
|
||||
### **7. API Management**
|
||||
|
||||
#### **a. Laravel API Documentation Generator**
|
||||
|
||||
- **Purpose**: Automatically generates API documentation from annotations.
|
||||
- **Why?** Saves time and provides professional API docs.
|
||||
- **Install**: `composer require mpociot/laravel-apidoc-generator` #contribute Needs support for PHP8^
|
||||
|
||||
#### **b. Passport**
|
||||
|
||||
- **Purpose**: OAuth2 authentication for API.
|
||||
- **Why?** Enterprise-grade API authentication.
|
||||
- **Install**: `composer require laravel/passport`
|
||||
|
||||
---
|
||||
|
||||
### **8. Auditing and Analytics**
|
||||
|
||||
#### **a. Laravel Auditing**
|
||||
|
||||
- **Purpose**: Tracks changes to Eloquent models.
|
||||
- **Why?** Helps with compliance and data tracking.
|
||||
- **Install**: `composer require owen-it/laravel-auditing`
|
||||
|
||||
#### **b. Laravel Analytics**
|
||||
|
||||
- **Purpose**: Integrates Google Analytics for app insights.
|
||||
- **Why?** Helps monitor user behavior and app usage.
|
||||
- **Install**: `composer require spatie/laravel-analytics`
|
||||
|
||||
---
|
||||
|
||||
### **9. Developer Productivity**
|
||||
|
||||
#### **a. Laravel IDE Helper**
|
||||
|
||||
- **Purpose**: Improves IDE auto-completion.
|
||||
- **Why?** Enhances developer productivity.
|
||||
- **Install**: `composer require barryvdh/laravel-ide-helper --dev`
|
||||
|
||||
#### **b. Laravel Dusk**
|
||||
|
||||
- **Purpose**: End-to-end testing.
|
||||
- **Why?** Ensures application functionality in a browser-like environment.
|
||||
- **Install**: `composer require laravel/dusk`
|
||||
|
||||
---
|
||||
|
||||
### **10. Miscellaneous**
|
||||
|
||||
#### **a. Backup Management**:
|
||||
|
||||
- **Spatie Laravel Backup**
|
||||
- **Purpose**: Backup files and database.
|
||||
- **Install**: `composer require spatie/laravel-backup`
|
||||
|
||||
#### **b. Task Scheduling**:
|
||||
|
||||
- **Purpose**: Manage cron jobs using Laravel's native scheduler.
|
||||
- **Install**: No package needed (native feature).
|
||||
|
||||
---
|
||||
|
||||
### Summary Table of Packages
|
||||
|
||||
| **Category** | **Recommended Package** |
|
||||
| --------------------- | ----------------------------------------- |
|
||||
| Logging | Laravel Telescope, Sentry, Monolog |
|
||||
| Performance | Laravel Octane, Clockwork, Response Cache |
|
||||
| Database Optimization | Debugbar, Query Builder, Eloquent Filter |
|
||||
| Scalability | Horizon, Scout, Redis |
|
||||
| Security | Sanctum, Permissions, Security Checker |
|
||||
| Multi-Tenancy | Spatie Laravel Multitenancy |
|
||||
| API | Passport, API Documentation Generator |
|
||||
| Auditing | Laravel Auditing, Laravel Analytics |
|
||||
| Productivity | IDE Helper, Dusk |
|
||||
8
sample-data/Default/Side Project/Onyxlog/Requirements.md
Normal file
8
sample-data/Default/Side Project/Onyxlog/Requirements.md
Normal file
@@ -0,0 +1,8 @@
|
||||
|
||||
| \# | Requirement | Confidence level | How am I going to do this? | Status |
|
||||
| --- | ------------------------ | ---------------- | -------------------------- | ------ |
|
||||
| 1. | User CRUD using Passport | Low | Learn from Youtube | |
|
||||
| 2. | Frontend for User | Low | Youtube and ChatGPT | |
|
||||
| 3. | Crud for Diary entries | High | | |
|
||||
| 4. | Ensuring privacy | High | | |
|
||||
| 5. | Frontend for Diary entry | Medium | | |
|
||||
Reference in New Issue
Block a user