start-vibing 3.0.5 → 3.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "start-vibing",
3
- "version": "3.0.5",
3
+ "version": "3.0.6",
4
4
  "description": "Setup Claude Code agents, skills, and hooks in your project. Smart copy that preserves your custom domains and configurations.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: bun-runtime
3
- description: Bun runtime patterns and best practices. Package management, bundling, testing, scripts. Use when working with Bun as the JavaScript runtime.
3
+ description: "ALWAYS invoke when using Bun runtime scripts, package management, bundling, testing. Do NOT run bun commands without checking patterns first."
4
4
  allowed-tools: Read, Write, Edit, Bash, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: codebase-knowledge
3
- description: Provides cached knowledge about project domains. Maps files by domain, tracks connections between components, records recent commits. Use before implementing to understand affected areas.
3
+ description: "ALWAYS invoke BEFORE implementing any feature. Maps files by domain, tracks connections. Do NOT write code without checking affected areas first."
4
4
  allowed-tools: Read, Glob, Grep
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: debugging-patterns
3
- description: Debugging strategies and error resolution patterns. Stack trace analysis, runtime errors, build errors, network issues. Use when debugging any type of error.
3
+ description: "ALWAYS invoke when errors, stack traces, or bugs appear. Do NOT debug blindly check resolution patterns here first. Covers runtime, build, and network errors."
4
4
  allowed-tools: Read, Write, Edit, Bash, Grep, Glob
5
5
  ---
6
6
 
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: docker-patterns
3
+ description: "ALWAYS invoke when creating or editing Dockerfile, docker-compose, or container configs. Do NOT write Docker configs directly — check multi-stage and security patterns first."
4
+ allowed-tools: Read, Write, Edit, Bash, Grep, Glob
5
+ ---
6
+
1
7
  # Docker Patterns - Production-Ready Containerization
2
8
 
3
9
  ## Purpose
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: docs-tracker
3
- description: Automates documentation maintenance. Detects modified files via git diff, creates docs for new files, updates docs for modified files, generates changelog. Use after implementation to keep docs current.
3
+ description: "ALWAYS invoke AFTER implementation completes. Detects modified files via git diff, creates/updates docs. Do NOT skip documentation is mandatory for all changes."
4
4
  allowed-tools: Read, Glob, Grep, Bash
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: final-check
3
- description: Final validation before task completion. Verifies all skills were consulted, documentation updated, tests pass. HAS VETO POWER - blocks incomplete tasks.
3
+ description: "ALWAYS invoke BEFORE completing ANY task. HAS VETO POWER — blocks incomplete work. Validates skills used, docs updated, tests passing. Do NOT finish tasks without this check."
4
4
  allowed-tools: Read, Grep, Glob, Bash
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: git-workflow
3
- description: Git workflow patterns and best practices. Branch management, conventional commits, direct merge to main, hooks. Use when working with git operations.
3
+ description: "ALWAYS invoke before ANY git operation commits, branches, merges. Do NOT run git commit directly check workflow rules here first."
4
4
  allowed-tools: Bash, Read, Grep, Glob
5
5
  ---
6
6
 
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: hook-development
3
+ description: "ALWAYS invoke when creating or modifying Claude Code hooks — stop, prompt-submit, pre-tool-use events. Do NOT write hooks without checking patterns and event types first."
4
+ allowed-tools: Read, Write, Edit, Bash, Grep, Glob
5
+ ---
6
+
1
7
  # Hook Development for Claude Code
2
8
 
3
9
  > Event-driven automation scripts for Claude Code. Hooks execute in response to system events, enabling validation, policy enforcement, context loading, and workflow integration.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: mongoose-patterns
3
- description: Mongoose/MongoDB patterns for schema design, queries, indexes, aggregations. Use when working with MongoDB through Mongoose.
3
+ description: "ALWAYS invoke when writing Mongoose schemas, queries, indexes, or aggregations. Do NOT create models or queries without checking patterns first."
4
4
  allowed-tools: Read, Write, Edit, Bash, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: nextjs-app-router
3
- description: Next.js 15 App Router patterns. Server/Client components, Server Actions, data fetching, caching, layouts, routing. Use when implementing Next.js features.
3
+ description: "ALWAYS invoke when writing Next.js code pages, layouts, server components, server actions, data fetching. Do NOT create routes without checking App Router patterns first."
4
4
  allowed-tools: Read, Write, Edit, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: performance-patterns
3
- description: Performance profiling and optimization patterns. React optimization, bundle analysis, memory leaks, API latency, database queries. Use when optimizing application performance.
3
+ description: "ALWAYS invoke when app is slow or needs optimization React renders, bundle size, memory leaks, API latency. Do NOT optimize without checking profiling patterns first."
4
4
  allowed-tools: Read, Write, Edit, Bash, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: playwright-automation
3
- description: Playwright testing automation patterns. E2E tests, browser automation, visual testing, API testing. Use when writing automated tests with Playwright.
3
+ description: "ALWAYS invoke when writing E2E tests or browser automation with Playwright. Do NOT create test files without checking Playwright patterns first."
4
4
  allowed-tools: Read, Write, Edit, Bash, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: quality-gate
3
- description: Automates quality checks (typecheck, lint, tests, build) and blocks commits that don't pass. Use before any commit to validate code quality.
3
+ description: "ALWAYS invoke BEFORE any commit. Runs typecheck, lint, test, build in sequence. Do NOT commit code without passing quality gate first."
4
4
  allowed-tools: Bash, Read, Grep
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: react-patterns
3
- description: Modern React patterns for React 19. Hooks, state management, component composition, performance optimization. Use when building React components.
3
+ description: "ALWAYS invoke when writing React components, hooks, or state management in .tsx files. Do NOT create components without checking React 19 patterns first."
4
4
  allowed-tools: Read, Write, Edit, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: research-cache
3
- description: Caches research findings to avoid redundant web searches. Stores best practices by topic with sources and dates. Use before researching to check existing knowledge.
3
+ description: "ALWAYS invoke BEFORE any web research. Checks existing cached findings first to avoid redundant searches. Do NOT use WebSearch without checking cache."
4
4
  allowed-tools: Read, Write, Glob, Grep
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: security-scan
3
- description: Audits code security against OWASP Top 10. Validates user ID from session, detects sensitive data leaks, verifies Zod validation. HAS VETO POWER - blocks insecure code.
3
+ description: "ALWAYS invoke before committing API, auth, or user data code. HAS VETO POWER blocks insecure code. Validates OWASP Top 10, session IDs, Zod validation. Do NOT skip security."
4
4
  allowed-tools: Read, Grep, Glob, Bash
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: shadcn-ui
3
- description: shadcn/ui component patterns. Component installation, customization, theming, accessibility. Use when building UI with shadcn components.
3
+ description: "ALWAYS invoke when adding or modifying shadcn/ui components. Do NOT install or customize shadcn components without checking theming and accessibility patterns first."
4
4
  allowed-tools: Read, Write, Edit, Grep, Glob, Bash
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: tailwind-patterns
3
- description: Tailwind CSS patterns and utilities. Responsive design, dark mode, animations, custom components. Use when styling with Tailwind CSS.
3
+ description: "ALWAYS invoke when writing Tailwind CSS classes responsive, dark mode, animations, custom utilities. Do NOT style components without checking Tailwind patterns first."
4
4
  allowed-tools: Read, Write, Edit, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: test-coverage
3
- description: Manages test coverage with Playwright E2E and Vitest unit tests. Tracks which files need tests, provides templates with fixture-based cleanup, enforces multi-viewport testing and database validation.
3
+ description: "ALWAYS invoke AFTER implementing any feature. Creates Vitest unit + Playwright E2E tests. Do NOT skip all new code needs test coverage. Tracks files needing tests."
4
4
  allowed-tools: Read, Write, Edit, Bash, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: trpc-api
3
- description: tRPC end-to-end type-safe API patterns. Router setup, procedures, middleware, context, client configuration. Use when building type-safe APIs with tRPC.
3
+ description: "ALWAYS invoke when building type-safe API routes with tRPC — routers, procedures, middleware. Do NOT create API endpoints without checking tRPC patterns first."
4
4
  allowed-tools: Read, Write, Edit, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: typescript-strict
3
- description: TypeScript strict mode patterns and best practices. Index access, literal types, null checks, generics, type inference. Use when working with TypeScript files.
3
+ description: "ALWAYS invoke when writing or editing .ts/.tsx files. Enforces strict mode — index access, null checks, literal types, generics. Do NOT write TypeScript without checking rules."
4
4
  allowed-tools: Read, Write, Edit, Grep, Glob, Bash
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: ui-ux-audit
3
- description: Automates UI/UX audits. Researches competitors, validates accessibility (WCAG 2.1), verifies responsiveness, audits design system consistency. Use when implementing any UI feature.
3
+ description: "ALWAYS invoke BEFORE implementing any UI feature. Researches competitors, validates WCAG 2.1 accessibility, checks responsiveness. Do NOT build UI without audit first."
4
4
  allowed-tools: Read, WebSearch, WebFetch, Grep, Glob
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: zod-validation
3
- description: Zod schema validation patterns. Input validation, type inference, transformations, error handling. Use when creating validation schemas or handling user input.
3
+ description: "ALWAYS invoke when handling user input, API params, or form data. Do NOT accept user input without Zod validation schemas. Covers type inference and transformations."
4
4
  allowed-tools: Read, Write, Edit, Grep, Glob
5
5
  ---
6
6