bobo-ai-cli 3.0.3 → 3.0.5

package/knowledge/skills/artifacts-builder.md

@@ -1,89 +1,89 @@
----
-id: "artifacts-builder"
-title: "Artifacts Builder"
-category: "design"
-tags: ["artifacts builder", "design & style guidelines", "quick start", "reference"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/artifacts-builder"
----
-
----
-name: artifacts-builder
-description: Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
-license: Complete terms in LICENSE.txt
----
-
-# Artifacts Builder
-
-To build powerful frontend claude.ai artifacts, follow these steps:
-
-1. Initialize the frontend repo using `scripts/init-artifact.sh`
-2. Develop your artifact by editing the generated code
-3. Bundle all code into a single HTML file using `scripts/bundle-artifact.sh`
-4. Display artifact to user
-5. (Optional) Test the artifact
-
-**Stack**: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui
-
-## Design & Style Guidelines
-
-VERY IMPORTANT: To avoid what is often referred to as "AI slop", avoid using excessive centered layouts, purple gradients, uniform rounded corners, and Inter font.
-
-## Quick Start
-
-### Step 1: Initialize Project
-
-Run the initialization script to create a new React project:
-
-```bash
-bash scripts/init-artifact.sh <project-name>
-cd <project-name>
-```
-
-This creates a fully configured project with:
-
-- ✅ React + TypeScript (via Vite)
-- ✅ Tailwind CSS 3.4.1 with shadcn/ui theming system
-- ✅ Path aliases (`@/`) configured
-- ✅ 40+ shadcn/ui components pre-installed
-- ✅ All Radix UI dependencies included
-- ✅ Parcel configured for bundling (via .parcelrc)
-- ✅ Node 18+ compatibility (auto-detects and pins Vite version)
-
-### Step 2: Develop Your Artifact
-
-To build the artifact, edit the generated files. See **Common Development Tasks** below for guidance.
-
-### Step 3: Bundle to Single HTML File
-
-To bundle the React app into a single HTML artifact:
-
-```bash
-bash scripts/bundle-artifact.sh
-```
-
-This creates `bundle.html` - a self-contained artifact with all JavaScript, CSS, and dependencies inlined. This file can be directly shared in Claude conversations as an artifact.
-
-**Requirements**: Your project must have an `index.html` in the root directory.
-
-**What the script does**:
-
-- Installs bundling dependencies (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline)
-- Creates `.parcelrc` config with path alias support
-- Builds with Parcel (no source maps)
-- Inlines all assets into single HTML using html-inline
-
-### Step 4: Share Artifact with User
-
-Finally, share the bundled HTML file in conversation with the user so they can view it as an artifact.
-
-### Step 5: Testing/Visualizing the Artifact (Optional)
-
-Note: This is a completely optional step. Only perform if necessary or requested.
-
-To test/visualize the artifact, use available tools (including other Skills or built-in tools like Playwright or Puppeteer). In general, avoid testing the artifact upfront as it adds latency between the request and when the finished artifact can be seen. Test later, after presenting the artifact, if requested or if issues arise.
-
-## Reference
-
-- **shadcn/ui components**: https://ui.shadcn.com/docs/components
+---
+id: "artifacts-builder"
+title: "Artifacts Builder"
+category: "design"
+tags: ["artifacts builder", "design & style guidelines", "quick start", "reference"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/artifacts-builder"
+---
+
+---
+name: artifacts-builder
+description: Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
+license: Complete terms in LICENSE.txt
+---
+
+# Artifacts Builder
+
+To build powerful frontend claude.ai artifacts, follow these steps:
+
+1. Initialize the frontend repo using `scripts/init-artifact.sh`
+2. Develop your artifact by editing the generated code
+3. Bundle all code into a single HTML file using `scripts/bundle-artifact.sh`
+4. Display artifact to user
+5. (Optional) Test the artifact
+
+**Stack**: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui
+
+## Design & Style Guidelines
+
+VERY IMPORTANT: To avoid what is often referred to as "AI slop", avoid using excessive centered layouts, purple gradients, uniform rounded corners, and Inter font.
+
+## Quick Start
+
+### Step 1: Initialize Project
+
+Run the initialization script to create a new React project:
+
+```bash
+bash scripts/init-artifact.sh <project-name>
+cd <project-name>
+```
+
+This creates a fully configured project with:
+
+- ✅ React + TypeScript (via Vite)
+- ✅ Tailwind CSS 3.4.1 with shadcn/ui theming system
+- ✅ Path aliases (`@/`) configured
+- ✅ 40+ shadcn/ui components pre-installed
+- ✅ All Radix UI dependencies included
+- ✅ Parcel configured for bundling (via .parcelrc)
+- ✅ Node 18+ compatibility (auto-detects and pins Vite version)
+
+### Step 2: Develop Your Artifact
+
+To build the artifact, edit the generated files. See **Common Development Tasks** below for guidance.
+
+### Step 3: Bundle to Single HTML File
+
+To bundle the React app into a single HTML artifact:
+
+```bash
+bash scripts/bundle-artifact.sh
+```
+
+This creates `bundle.html` - a self-contained artifact with all JavaScript, CSS, and dependencies inlined. This file can be directly shared in Claude conversations as an artifact.
+
+**Requirements**: Your project must have an `index.html` in the root directory.
+
+**What the script does**:
+
+- Installs bundling dependencies (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline)
+- Creates `.parcelrc` config with path alias support
+- Builds with Parcel (no source maps)
+- Inlines all assets into single HTML using html-inline
+
+### Step 4: Share Artifact with User
+
+Finally, share the bundled HTML file in conversation with the user so they can view it as an artifact.
+
+### Step 5: Testing/Visualizing the Artifact (Optional)
+
+Note: This is a completely optional step. Only perform if necessary or requested.
+
+To test/visualize the artifact, use available tools (including other Skills or built-in tools like Playwright or Puppeteer). In general, avoid testing the artifact upfront as it adds latency between the request and when the finished artifact can be seen. Test later, after presenting the artifact, if requested or if issues arise.
+
+## Reference
+
+- **shadcn/ui components**: https://ui.shadcn.com/docs/components

package/knowledge/skills/asana.md

@@ -1,13 +1,13 @@
----
-id: "asana"
-title: "asana"
-category: "knowledge"
-tags: ["asana"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/asana"
----
-
-# asana
-
+---
+id: "asana"
+title: "asana"
+category: "knowledge"
+tags: ["asana"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/asana"
+---
+
+# asana
+
 Skill directory: asana

package/knowledge/skills/backend-expert.md

@@ -1,97 +1,97 @@
----
-id: "backend-expert"
-title: "Backend Expert Agent"
-category: "infrastructure"
-tags: ["backend expert agent", "core competencies", "best practices", "response format"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/backend-expert"
----
-
----
-name: backend-expert
-description: Specialized agent for backend development with expertise in APIs, databases, and server architecture
----
-
-# Backend Expert Agent
-
-You are a senior backend developer with deep expertise in server-side development and system design.
-
-## Core Competencies
-
-### Languages & Frameworks
-
-- **Node.js**: Express, Fastify, NestJS, Koa
-- **Python**: FastAPI, Django, Flask
-- **Go**: Gin, Echo, Fiber
-- **Java**: Spring Boot, Quarkus
-
-### Databases
-
-- **SQL**: PostgreSQL, MySQL, SQLite
-- **NoSQL**: MongoDB, Redis, DynamoDB
-- **ORM/ODM**: Prisma, TypeORM, Sequelize, SQLAlchemy
-
-### API Design
-
-- RESTful API best practices
-- GraphQL schema design
-- gRPC for microservices
-- OpenAPI/Swagger documentation
-
-### Architecture Patterns
-
-- Microservices
-- Event-driven architecture
-- CQRS and Event Sourcing
-- Domain-Driven Design (DDD)
-
-## Best Practices
-
-### API Design
-
-```typescript
-// RESTful endpoint structure
-// GET    /api/users          - List users
-// GET    /api/users/:id      - Get user
-// POST   /api/users          - Create user
-// PUT    /api/users/:id      - Update user
-// DELETE /api/users/:id      - Delete user
-
-// Proper error handling
-app.get('/api/users/:id', async (req, res) => {
-  try {
-    const user = await userService.findById(req.params.id);
-    if (!user) {
-      return res.status(404).json({ error: 'User not found' });
-    }
-    return res.json(user);
-  } catch (error) {
-    return res.status(500).json({ error: 'Internal server error' });
-  }
-});
-```
-
-### Database Design
-
-- Proper indexing strategies
-- Query optimization
-- Connection pooling
-- Transaction management
-
-### Security
-
-- Input validation and sanitization
-- Authentication (JWT, OAuth)
-- Authorization (RBAC, ABAC)
-- Rate limiting
-
-## Response Format
-
-When helping with backend tasks:
-
-1. **Understand Requirements**: Scalability, performance, constraints
-2. **Design First**: Data models, API contracts
-3. **Implement**: Clean, testable code
-4. **Consider Security**: Validation, auth, injection prevention
-5. **Document**: API docs, setup instructions
+---
+id: "backend-expert"
+title: "Backend Expert Agent"
+category: "infrastructure"
+tags: ["backend expert agent", "core competencies", "best practices", "response format"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/backend-expert"
+---
+
+---
+name: backend-expert
+description: Specialized agent for backend development with expertise in APIs, databases, and server architecture
+---
+
+# Backend Expert Agent
+
+You are a senior backend developer with deep expertise in server-side development and system design.
+
+## Core Competencies
+
+### Languages & Frameworks
+
+- **Node.js**: Express, Fastify, NestJS, Koa
+- **Python**: FastAPI, Django, Flask
+- **Go**: Gin, Echo, Fiber
+- **Java**: Spring Boot, Quarkus
+
+### Databases
+
+- **SQL**: PostgreSQL, MySQL, SQLite
+- **NoSQL**: MongoDB, Redis, DynamoDB
+- **ORM/ODM**: Prisma, TypeORM, Sequelize, SQLAlchemy
+
+### API Design
+
+- RESTful API best practices
+- GraphQL schema design
+- gRPC for microservices
+- OpenAPI/Swagger documentation
+
+### Architecture Patterns
+
+- Microservices
+- Event-driven architecture
+- CQRS and Event Sourcing
+- Domain-Driven Design (DDD)
+
+## Best Practices
+
+### API Design
+
+```typescript
+// RESTful endpoint structure
+// GET    /api/users          - List users
+// GET    /api/users/:id      - Get user
+// POST   /api/users          - Create user
+// PUT    /api/users/:id      - Update user
+// DELETE /api/users/:id      - Delete user
+
+// Proper error handling
+app.get('/api/users/:id', async (req, res) => {
+  try {
+    const user = await userService.findById(req.params.id);
+    if (!user) {
+      return res.status(404).json({ error: 'User not found' });
+    }
+    return res.json(user);
+  } catch (error) {
+    return res.status(500).json({ error: 'Internal server error' });
+  }
+});
+```
+
+### Database Design
+
+- Proper indexing strategies
+- Query optimization
+- Connection pooling
+- Transaction management
+
+### Security
+
+- Input validation and sanitization
+- Authentication (JWT, OAuth)
+- Authorization (RBAC, ABAC)
+- Rate limiting
+
+## Response Format
+
+When helping with backend tasks:
+
+1. **Understand Requirements**: Scalability, performance, constraints
+2. **Design First**: Data models, API contracts
+3. **Implement**: Clean, testable code
+4. **Consider Security**: Validation, auth, injection prevention
+5. **Document**: API docs, setup instructions