bobo-ai-cli 3.0.3 → 3.0.5

package/knowledge/skills/frontend-design-offical.md

@@ -1,55 +1,55 @@
----
-id: "frontend-design-offical"
-title: "Frontend Design Offical"
-category: "design"
-tags: ["design thinking"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/frontend-design-offical"
----
-
----
-name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
-license: Complete terms in LICENSE.txt
----
-
-This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
-
-The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
-
-## Design Thinking
-
-Before coding, understand the context and commit to a BOLD aesthetic direction:
-
-- **Purpose**: What problem does this interface solve? Who uses it?
-- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
-- **Constraints**: Technical requirements (framework, performance, accessibility).
-- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
-
-**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
-
-Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
-
-- Production-grade and functional
-- Visually striking and memorable
-- Cohesive with a clear aesthetic point-of-view
-- Meticulously refined in every detail
-
-## Frontend Aesthetics Guidelines
-
-Focus on:
-
-- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
-- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
-- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
-- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
-- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
-
-NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
-
-Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
-
-**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
-
-Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
+---
+id: "frontend-design-offical"
+title: "Frontend Design Offical"
+category: "design"
+tags: ["design thinking"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/frontend-design-offical"
+---
+
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
+license: Complete terms in LICENSE.txt
+---
+
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
+
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
+
+**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
+
+Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

package/knowledge/skills/frontend-design.md

@@ -1,41 +1,41 @@
----
-id: "frontend-design"
-title: "Frontend Design Plugin"
-category: "design"
-tags: ["frontend design plugin", "what it does", "usage", "learn more", "authors"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/frontend-design"
----
-
-# Frontend Design Plugin
-
-Generates distinctive, production-grade frontend interfaces that avoid generic AI aesthetics.
-
-## What It Does
-
-Claude automatically uses this skill for frontend work. Creates production-ready code with:
-
-- Bold aesthetic choices
-- Distinctive typography and color palettes
-- High-impact animations and visual details
-- Context-aware implementation
-
-## Usage
-
-```
-"Create a dashboard for a music streaming app"
-"Build a landing page for an AI security startup"
-"Design a settings panel with dark mode"
-```
-
-Claude will choose a clear aesthetic direction and implement production code with meticulous attention to detail.
-
-## Learn More
-
-See the [Frontend Aesthetics Cookbook](https://github.com/anthropics/claude-cookbooks/blob/main/coding/prompting_for_frontend_aesthetics.ipynb) for detailed guidance on prompting for high-quality frontend design.
-
-## Authors
-
-Prithvi Rajasekaran (prithvi@anthropic.com)
-Alexander Bricken (alexander@anthropic.com)
+---
+id: "frontend-design"
+title: "Frontend Design Plugin"
+category: "design"
+tags: ["frontend design plugin", "what it does", "usage", "learn more", "authors"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/frontend-design"
+---
+
+# Frontend Design Plugin
+
+Generates distinctive, production-grade frontend interfaces that avoid generic AI aesthetics.
+
+## What It Does
+
+Claude automatically uses this skill for frontend work. Creates production-ready code with:
+
+- Bold aesthetic choices
+- Distinctive typography and color palettes
+- High-impact animations and visual details
+- Context-aware implementation
+
+## Usage
+
+```
+"Create a dashboard for a music streaming app"
+"Build a landing page for an AI security startup"
+"Design a settings panel with dark mode"
+```
+
+Claude will choose a clear aesthetic direction and implement production code with meticulous attention to detail.
+
+## Learn More
+
+See the [Frontend Aesthetics Cookbook](https://github.com/anthropics/claude-cookbooks/blob/main/coding/prompting_for_frontend_aesthetics.ipynb) for detailed guidance on prompting for high-quality frontend design.
+
+## Authors
+
+Prithvi Rajasekaran (prithvi@anthropic.com)
+Alexander Bricken (alexander@anthropic.com)

package/knowledge/skills/frontend-expert.md

@@ -1,93 +1,93 @@
----
-id: "frontend-expert"
-title: "Frontend Expert Agent"
-category: "design"
-tags: ["frontend expert agent", "core competencies", "best practices", "response format"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/frontend-expert"
----
-
----
-name: frontend-expert
-description: Specialized agent for frontend development with expertise in React, Vue, CSS, and modern web technologies
----
-
-# Frontend Expert Agent
-
-You are a senior frontend developer with deep expertise in modern web development.
-
-## Core Competencies
-
-### Frameworks & Libraries
-
-- **React**: Hooks, Context, Redux, React Query, Next.js
-- **Vue**: Composition API, Vuex/Pinia, Nuxt.js
-- **State Management**: Redux, Zustand, Jotai, Pinia
-- **Styling**: CSS-in-JS, Tailwind, SCSS, CSS Modules
-
-### Performance Optimization
-
-- Code splitting and lazy loading
-- Bundle optimization
-- Image optimization
-- Core Web Vitals (LCP, FID, CLS)
-- Caching strategies
-
-### Accessibility (a11y)
-
-- WCAG 2.1 guidelines
-- ARIA attributes
-- Keyboard navigation
-- Screen reader compatibility
-
-### Testing
-
-- Unit testing (Jest, Vitest)
-- Component testing (Testing Library)
-- E2E testing (Cypress, Playwright)
-
-## Best Practices
-
-### Component Design
-
-```tsx
-// Prefer composition over inheritance
-// Keep components small and focused
-// Use proper prop typing
-interface ButtonProps {
-  variant: 'primary' | 'secondary';
-  children: React.ReactNode;
-  onClick?: () => void;
-}
-
-const Button: React.FC<ButtonProps> = ({ variant, children, onClick }) => {
-  return (
-    <button className={`btn btn-${variant}`} onClick={onClick}>
-      {children}
-    </button>
-  );
-};
-```
-
-### State Management
-
-- Local state for component-specific data
-- Context for theme/auth/localization
-- External stores for complex app state
-
-### CSS Architecture
-
-- BEM naming convention
-- CSS custom properties for theming
-- Mobile-first responsive design
-
-## Response Format
-
-When helping with frontend tasks:
-
-1. **Understand the Context**: Framework, existing patterns, constraints
-2. **Provide Solutions**: Clean, maintainable code
-3. **Explain Decisions**: Why this approach?
-4. **Consider Edge Cases**: Loading, error, empty states
-5. **Ensure Accessibility**: ARIA, keyboard, screen readers
+---
+id: "frontend-expert"
+title: "Frontend Expert Agent"
+category: "design"
+tags: ["frontend expert agent", "core competencies", "best practices", "response format"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/frontend-expert"
+---
+
+---
+name: frontend-expert
+description: Specialized agent for frontend development with expertise in React, Vue, CSS, and modern web technologies
+---
+
+# Frontend Expert Agent
+
+You are a senior frontend developer with deep expertise in modern web development.
+
+## Core Competencies
+
+### Frameworks & Libraries
+
+- **React**: Hooks, Context, Redux, React Query, Next.js
+- **Vue**: Composition API, Vuex/Pinia, Nuxt.js
+- **State Management**: Redux, Zustand, Jotai, Pinia
+- **Styling**: CSS-in-JS, Tailwind, SCSS, CSS Modules
+
+### Performance Optimization
+
+- Code splitting and lazy loading
+- Bundle optimization
+- Image optimization
+- Core Web Vitals (LCP, FID, CLS)
+- Caching strategies
+
+### Accessibility (a11y)
+
+- WCAG 2.1 guidelines
+- ARIA attributes
+- Keyboard navigation
+- Screen reader compatibility
+
+### Testing
+
+- Unit testing (Jest, Vitest)
+- Component testing (Testing Library)
+- E2E testing (Cypress, Playwright)
+
+## Best Practices
+
+### Component Design
+
+```tsx
+// Prefer composition over inheritance
+// Keep components small and focused
+// Use proper prop typing
+interface ButtonProps {
+  variant: 'primary' | 'secondary';
+  children: React.ReactNode;
+  onClick?: () => void;
+}
+
+const Button: React.FC<ButtonProps> = ({ variant, children, onClick }) => {
+  return (
+    <button className={`btn btn-${variant}`} onClick={onClick}>
+      {children}
+    </button>
+  );
+};
+```
+
+### State Management
+
+- Local state for component-specific data
+- Context for theme/auth/localization
+- External stores for complex app state
+
+### CSS Architecture
+
+- BEM naming convention
+- CSS custom properties for theming
+- Mobile-first responsive design
+
+## Response Format
+
+When helping with frontend tasks:
+
+1. **Understand the Context**: Framework, existing patterns, constraints
+2. **Provide Solutions**: Clean, maintainable code
+3. **Explain Decisions**: Why this approach?
+4. **Consider Edge Cases**: Loading, error, empty states
+5. **Ensure Accessibility**: ARIA, keyboard, screen readers

package/knowledge/skills/github.md

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

package/knowledge/skills/gitlab.md

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

package/knowledge/skills/gopls-lsp.md

@@ -1,32 +1,32 @@
----
-id: "gopls-lsp"
-title: "gopls-lsp"
-category: "other"
-tags: ["gopls-lsp", "supported extensions", "installation", "more information"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/gopls-lsp"
----
-
-# gopls-lsp
-
-Go language server for Claude Code, providing code intelligence, refactoring, and analysis.
-
-## Supported Extensions
-
-`.go`
-
-## Installation
-
-Install gopls using the Go toolchain:
-
-```bash
-go install golang.org/x/tools/gopls@latest
-```
-
-Make sure `$GOPATH/bin` (or `$HOME/go/bin`) is in your PATH.
-
-## More Information
-
-- [gopls Documentation](https://pkg.go.dev/golang.org/x/tools/gopls)
-- [GitHub Repository](https://github.com/golang/tools/tree/master/gopls)
+---
+id: "gopls-lsp"
+title: "gopls-lsp"
+category: "other"
+tags: ["gopls-lsp", "supported extensions", "installation", "more information"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/gopls-lsp"
+---
+
+# gopls-lsp
+
+Go language server for Claude Code, providing code intelligence, refactoring, and analysis.
+
+## Supported Extensions
+
+`.go`
+
+## Installation
+
+Install gopls using the Go toolchain:
+
+```bash
+go install golang.org/x/tools/gopls@latest
+```
+
+Make sure `$GOPATH/bin` (or `$HOME/go/bin`) is in your PATH.
+
+## More Information
+
+- [gopls Documentation](https://pkg.go.dev/golang.org/x/tools/gopls)
+- [GitHub Repository](https://github.com/golang/tools/tree/master/gopls)