Menu
Create a paired git worktree workspace for bookings-api (backend) and anny-ui (frontend) for a feature or bugfix. Use when starting work on a new task that touches both repos. Triggers on "create workspace", "new workspace", or a CU- task ID.
Navigate and manage Fabian's Obsidian vault "brain". Knows the folder structure, frontmatter schemas, templates, naming conventions, and where every type of content belongs. Use when creating, moving, or finding notes in Obsidian. Triggers on "obsidian", "vault", "note", "daily", "book", "knowledge base", "brain".
Query the anny production database to inspect live data for bug investigation. Use when a bug cannot be reproduced locally and you need to check actual resource/booking/service data on prod. Triggers on "check prod", "prod data", "query prod", "debug prod", "can't reproduce", or /skill:prod-debug.
Audit Vue and Nuxt applications for performance issues. Checks for hydration mismatches, missing lazy loading, reactivity overhead, bundle size problems, SSR anti-patterns, and Core Web Vitals regressions. Use when user says "check performance", "audit performance", "vue performance", "nuxt performance", "hydration issues", "slow page", "optimize vue", "optimize nuxt", or invokes /vue-nuxt-performance.
| name | anny-workspace |
| description | Create a paired git worktree workspace for bookings-api (backend) and anny-ui (frontend) for a feature or bugfix. Use when starting work on a new task that touches both repos. Triggers on "create workspace", "new workspace", or a CU- task ID. |
Create a paired git worktree session for bookings-api (backend) and anny-ui (frontend), then open them in a VS Code workspace.
~/bin/create-workspace.sh <slug>
Format: CU-<taskId>_<feature-name> or just <feature-name>
Examples:
CU-1234_booking-flow-fixdark-mode-toggleCU-5678_payment-integration --dry-run~/code/anny/worktrees/<slug>/.code-workspace file linking both reposIf the workspace already exists, it reopens it.
~/code/anny/bookings-api~/code/anny/anny-ui~/code/anny/worktrees/<slug>/Follow the ClickUp convention: feature/CU-<taskId>-<slug> or bugfix/CU-<taskId>-<slug>