@haposoft/cafekit 0.11.0 → 0.11.3

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.
Files changed (54) hide show
  1. package/bin/lib/context.js +8 -3
  2. package/bin/lib/i18n.js +2 -1
  3. package/bin/phases/post-install.js +12 -6
  4. package/bin/phases/select-platform.js +24 -7
  5. package/package.json +1 -1
  6. package/src/claude/CLAUDE.md +5 -7
  7. package/src/claude/agents/brainstormer.md +5 -5
  8. package/src/claude/agents/code-auditor.md +2 -2
  9. package/src/claude/agents/debugger.md +4 -4
  10. package/src/claude/agents/deployer.md +2 -2
  11. package/src/claude/agents/docs-keeper.md +4 -4
  12. package/src/claude/agents/git-ops.md +2 -2
  13. package/src/claude/agents/god-developer.md +2 -2
  14. package/src/claude/agents/inspector.md +1 -1
  15. package/src/claude/agents/project-manager.md +1 -1
  16. package/src/claude/agents/spec-maker.md +8 -8
  17. package/src/claude/agents/test-runner.md +1 -1
  18. package/src/claude/agents/ui-ux-designer.md +2 -2
  19. package/src/claude/gitignore +1 -0
  20. package/src/claude/hooks/session.cjs +96 -4
  21. package/src/claude/references/debugger/frontend-verification.md +2 -2
  22. package/src/claude/rules/manage-docs.md +1 -1
  23. package/src/claude/rules/state-sync.md +1 -1
  24. package/src/claude/rules/workflow.md +2 -2
  25. package/src/claude/skills/agent-browser/SKILL.md +4 -1
  26. package/src/claude/skills/ai-multimodal/SKILL.md +7 -6
  27. package/src/claude/skills/backend-development/SKILL.md +7 -2
  28. package/src/claude/skills/brainstorm/SKILL.md +7 -2
  29. package/src/claude/skills/chrome-devtools/SKILL.md +7 -2
  30. package/src/claude/skills/code-review/SKILL.md +7 -2
  31. package/src/claude/skills/debug/SKILL.md +7 -2
  32. package/src/claude/skills/develop/SKILL.md +7 -1
  33. package/src/claude/skills/devops/SKILL.md +7 -2
  34. package/src/claude/skills/docs/SKILL.md +7 -2
  35. package/src/claude/skills/docx/SKILL.md +4 -1
  36. package/src/claude/skills/frontend-design/SKILL.md +7 -2
  37. package/src/claude/skills/frontend-development/SKILL.md +7 -2
  38. package/src/claude/skills/generate-graph/SKILL.md +7 -5
  39. package/src/claude/skills/git/SKILL.md +7 -2
  40. package/src/claude/skills/hotfix/SKILL.md +7 -2
  41. package/src/claude/skills/impact-analysis/SKILL.md +8 -3
  42. package/src/claude/skills/inspect/SKILL.md +7 -2
  43. package/src/claude/skills/mobile-development/SKILL.md +7 -2
  44. package/src/claude/skills/pdf/SKILL.md +4 -1
  45. package/src/claude/skills/pptx/SKILL.md +4 -1
  46. package/src/claude/skills/question/SKILL.md +7 -2
  47. package/src/claude/skills/react-best-practices/SKILL.md +7 -2
  48. package/src/claude/skills/research/SKILL.md +7 -2
  49. package/src/claude/skills/specs/SKILL.md +7 -2
  50. package/src/claude/skills/sync/SKILL.md +7 -2
  51. package/src/claude/skills/test/SKILL.md +7 -2
  52. package/src/claude/skills/ui-ux-pro-max/SKILL.md +7 -2
  53. package/src/claude/skills/web-testing/SKILL.md +7 -2
  54. package/src/claude/skills/xlsx/SKILL.md +4 -1
@@ -8,11 +8,11 @@ Use the CafeKit loop: **Understand -> Plan -> Execute -> Verify -> Sync**.
8
8
  - Read the active spec/task file when one exists.
9
9
  - Read and activate any CafeKit skill that likely applies before taking action.
10
10
  - Inspect only the code needed to understand the affected area.
11
- - Use `hapo:inspect` or focused search when structure is unclear.
11
+ - Use `inspect` or focused search when structure is unclear.
12
12
 
13
13
  ## 2. Plan
14
14
 
15
- - For non-trivial features, use `/hapo:specs` to create or validate the spec.
15
+ - For non-trivial features, use `/specs` to create or validate the spec.
16
16
  - For approved specs, work one task file at a time.
17
17
  - Extract from the active task:
18
18
  - `Context`
@@ -2,12 +2,15 @@
2
2
  name: hapo:agent-browser
3
3
  description: AI-optimized browser automation CLI with context-efficient snapshots. Use for long autonomous sessions, self-verifying workflows, video recording, and cloud browser testing (Browserbase).
4
4
  license: Apache-2.0
5
+ user-invocable: true
6
+ when_to_use: "Invoke to drive a real browser for navigation, screenshots, or DOM actions."
7
+ category: dev-tools
8
+ keywords: [browser, automation, screenshot, navigation]
5
9
  argument-hint: "[url or task]"
6
10
  metadata:
7
11
  author: haposoft
8
12
  version: "1.0.0"
9
13
  ---
10
-
11
14
  # agent-browser Skill
12
15
 
13
16
  Browser automation CLI designed for AI agents. Uses "snapshot + refs" paradigm for 93% less context than Playwright MCP.
@@ -2,14 +2,15 @@
2
2
  name: hapo:ai-multimodal
3
3
  description: Analyze images/audio/video/documentation with Gemini API. Use for vision analysis, transcription, OCR, design extraction, and deep multimodal understanding.
4
4
  license: MIT
5
- allowed-tools:
6
- - Bash
7
- - Read
8
- - Write
9
- - Edit
5
+ user-invocable: true
6
+ when_to_use: "Invoke to analyze or generate images, audio, or mixed-media content."
7
+ category: utilities
8
+ keywords: [multimodal, image, audio, vision]
10
9
  argument-hint: "[file-path] [prompt]"
10
+ metadata:
11
+ author: haposoft
12
+ version: "1.0.0"
11
13
  ---
12
-
13
14
  # AI Multimodal
14
15
 
15
16
  Process audio, images, videos, documents using Gemini. Purely focused on robust analysis, transcription, and contextual extraction.
@@ -2,10 +2,15 @@
2
2
  name: hapo:backend-development
3
3
  description: Build backends with Node.js, Python, Go (NestJS, FastAPI, Django). Use for REST/GraphQL/gRPC APIs, auth (OAuth, JWT), databases, microservices, security (OWASP), Docker/K8s.
4
4
  license: MIT
5
+ user-invocable: true
6
+ when_to_use: "Invoke to build or modify server APIs, services, and data layers."
7
+ category: backend
8
+ keywords: [backend, api, server, database]
5
9
  argument-hint: "[framework] [task]"
6
- version: "1.0.0"
10
+ metadata:
11
+ author: haposoft
12
+ version: "1.0.0"
7
13
  ---
8
-
9
14
  # Backend Development Skill
10
15
 
11
16
  Production-ready backend development with modern technologies, best practices, and proven patterns.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:brainstorm
3
3
  description: "Scout-first brainstorming for unclear ideas, architectural choices, scope gates, and translating raw intent into a spec-ready design."
4
+ user-invocable: true
5
+ when_to_use: "Invoke before choosing among unclear technical options or scope."
6
+ category: utilities
7
+ keywords: [ideation, tradeoffs, decisions, scope]
4
8
  argument-hint: "<idea_or_problem>"
5
- version: 2.1.0
9
+ metadata:
10
+ author: haposoft
11
+ version: "2.1.0"
6
12
  ---
7
-
8
13
  # Brainstorming Skill
9
14
 
10
15
  You execute CafeKit's pre-spec design workflow. Your job is to turn a raw idea into a validated, spec-ready design without writing code or starting implementation.
@@ -2,10 +2,15 @@
2
2
  name: hapo:chrome-devtools
3
3
  description: Automate browsers with Puppeteer CLI scripts and persistent sessions. Use for screenshots, performance analysis, network monitoring, web scraping, form automation, JavaScript debugging.
4
4
  license: Apache-2.0
5
+ user-invocable: true
6
+ when_to_use: "Invoke to inspect, debug, or profile a page via Chrome DevTools."
7
+ category: dev-tools
8
+ keywords: [devtools, chrome, debug, profiling]
5
9
  argument-hint: "[url or task]"
6
- version: "1.1.0"
10
+ metadata:
11
+ author: haposoft
12
+ version: "1.1.0"
7
13
  ---
8
-
9
14
  # Chrome DevTools Agent Skill
10
15
 
11
16
  Browser automation via Puppeteer scripts with persistent sessions. All scripts output JSON.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:code-review
3
3
  description: "Adversarial code review with technical rigor. Supports 3-Stage Protocol with ai-multimodal injection for multimodal spec compliance. Red-team analysis finds security holes, logic gaps, and architecture violations."
4
+ user-invocable: true
5
+ when_to_use: "Invoke to review a diff for correctness and quality before merge."
6
+ category: dev-tools
7
+ keywords: [review, diff, quality, correctness]
4
8
  argument-hint: "[#PR | COMMIT | --pending | scope]"
5
- version: 1.0.0
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Code Review
9
14
 
10
15
  Adversarial code review with technical rigor, evidence-based claims, and visual/document intelligence via the `hapo:ai-multimodal` Hub.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:debug
3
3
  description: "Use before fixing any bug, failing test, CI/CD failure, production incident, performance issue, UI regression, flaky test, or unexpected behavior. Diagnostic-only root-cause workflow with evidence, hypotheses, blast-radius mapping, and verification plan."
4
+ user-invocable: true
5
+ when_to_use: "Invoke for evidence-first root-cause diagnosis before any fix."
6
+ category: dev-tools
7
+ keywords: [debug, diagnosis, root-cause, evidence]
4
8
  argument-hint: "[issue] --quick|--ci|--frontend|--perf"
5
- version: "1.0.0"
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Debug - Evidence-First Root Cause Analysis
9
14
 
10
15
  Debugging is diagnosis, not repair. Find the source of the failure before changing product code.
@@ -1,9 +1,15 @@
1
1
  ---
2
2
  name: hapo:develop
3
3
  description: "Code execution engine: Reads specs and implements code end-to-end with automatic code review, self-healing, and visual implementation notes."
4
+ user-invocable: true
5
+ when_to_use: "Invoke to implement specs and tasks end-to-end after scope is clear."
6
+ category: utilities
7
+ keywords: [implementation, specs, build, orchestration]
4
8
  argument-hint: "[feature-name|specs-directory-path] [task-file] [--flash] [--no-notes]"
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
5
12
  ---
6
-
7
13
  # Develop — Feature Implementation (Task-Orchestrated Build)
8
14
 
9
15
  Reads the project specification (`hapo:specs`) and implements code through a disciplined task loop. In specific-task mode it behaves like a surgical executor. In full-spec mode it behaves like a sequential orchestrator, processing one unblocked task at a time and syncing state after every verified task.
@@ -2,10 +2,15 @@
2
2
  name: hapo:devops
3
3
  description: Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.
4
4
  license: MIT
5
+ user-invocable: true
6
+ when_to_use: "Invoke to deploy, containerize, or set up CI/CD and infra."
7
+ category: devops
8
+ keywords: [deploy, docker, ci-cd, kubernetes]
5
9
  argument-hint: "[platform] [task]"
6
- version: "2.0.0"
10
+ metadata:
11
+ author: haposoft
12
+ version: "2.0.0"
7
13
  ---
8
-
9
14
  # DevOps Skill
10
15
 
11
16
  Deploy and manage cloud infrastructure across Cloudflare, Docker, Google Cloud, and Kubernetes.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:docs
3
3
  description: "Create, update, summarize, or reconstruct project/system documentation from source code. Use reconstruct mode for as-is documentation of existing or legacy systems with evidence and uncertainty tracking."
4
- version: 1.0.0
4
+ user-invocable: true
5
+ when_to_use: "Invoke to create, update, or reconstruct project documentation from source."
6
+ category: document-skills
7
+ keywords: [docs, reconstruct, documentation, evidence]
5
8
  argument-hint: "[--init|--update|--summarize|--reconstruct] [scope]"
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Docs
9
14
 
10
15
  Project documentation workflow for CafeKit.
@@ -2,11 +2,14 @@
2
2
  name: hapo:docx
3
3
  description: Create, edit, analyze .docx Word documents. Use for document creation, tracked changes, comments, formatting preservation, text extraction, template modification.
4
4
  license: Proprietary. LICENSE.txt has complete terms
5
+ user-invocable: true
6
+ when_to_use: "Invoke to read, create, or edit Word .docx documents."
7
+ category: document-skills
8
+ keywords: [docx, word, document, office]
5
9
  metadata:
6
10
  author: haposoft
7
11
  version: "1.0.0"
8
12
  ---
9
-
10
13
  # DOCX creation, editing, and analysis
11
14
 
12
15
  ## Overview
@@ -2,9 +2,14 @@
2
2
  name: hapo:frontend-design
3
3
  description: Create polished frontend interfaces from designs/screenshots/videos. Use for web components, 3D experiences, replicating UI designs, quick prototypes, immersive interfaces, avoiding AI slop.
4
4
  license: Complete terms in LICENSE.txt
5
- version: "1.0.0"
5
+ user-invocable: true
6
+ when_to_use: "Invoke to translate mockups or screenshots into UI implementation."
7
+ category: frontend
8
+ keywords: [design, mockup, ui, replication]
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  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.
9
14
 
10
15
  **IMPORTANT**: MUST follow Design Thinking, Frontend Aesthetics Guidelines, Asset & Analysis References, and Anti-Patterns (AI Slop) sections below. DO NOT skip these rules.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:frontend-development
3
3
  description: Build React/TypeScript frontends with modern patterns. Use for components, Suspense, lazy loading, useSuspenseQuery, MUI v7 styling, TanStack Router, performance optimization.
4
+ user-invocable: true
5
+ when_to_use: "Invoke to build React/TS components with best practices."
6
+ category: frontend
7
+ keywords: [frontend, react, typescript, components]
4
8
  argument-hint: "[component or feature]"
5
- version: "1.0.0"
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Frontend Development Guidelines
9
14
 
10
15
  ## Purpose
@@ -1,12 +1,14 @@
1
1
  ---
2
2
  name: hapo:generate-graph
3
3
  description: >-
4
- Use when the user wants to create any technical diagram - architecture, data
5
- flow, flowchart, sequence, agent/memory, or concept map - and export as
6
- SVG+PNG. Trigger on: "generate diagram" "draw diagram" "visualize" or any
7
- system/flow description the user wants illustrated.
4
+ user-invocable: true
5
+ when_to_use: "Invoke to build a queryable graph or diagram from code or data."
6
+ category: utilities
7
+ keywords: [graph, visualization, diagram, analysis]
8
+ metadata:
9
+ author: haposoft
10
+ version: "1.0.0"
8
11
  ---
9
-
10
12
  # Generate Graph
11
13
 
12
14
  Generate production-quality SVG technical diagrams exported as PNG via `rsvg-convert`.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:git
3
3
  description: "Hapo Native Git Operations & Worktree Management. Handles safe commits, conventional split, branch finish choices, secret scanning, and sibling-branch worktrees locally."
4
+ user-invocable: true
5
+ when_to_use: "Invoke for commits, PRs, branch hygiene, or worktree management."
6
+ category: dev-tools
7
+ keywords: [git, commits, pr, worktree]
4
8
  argument-hint: "commit | push | pr | finish | worktree <feature-desc>"
5
- version: "1.0.0"
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Git Operations & Worktree
9
14
 
10
15
  This skill merges Version Control Systems (VSC) capabilities and parallel Worktree management into a single, clean-room execution engine utilizing pure Bash commands rather than proprietary Node scripts.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:hotfix
3
3
  description: "ALWAYS activate this skill when you are asked to FIX a bug, error, test failure, CI/CD issue, type error, lint error, log error, UI issue, or code problem. Uses hapo:debug for evidence-first diagnosis before any code change."
4
+ user-invocable: true
5
+ when_to_use: "Invoke to fix a bug or failure with scout-first diagnosis before change."
6
+ category: dev-tools
7
+ keywords: [hotfix, fix, bug, diagnosis]
4
8
  argument-hint: "[issue] --quick|--parallel|--from-debug"
5
- version: "1.0.0"
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Hotfix - Structured Bug Elimination
9
14
 
10
15
  Kill bugs systematically. No guessing. Evidence first, fix second.
@@ -1,10 +1,15 @@
1
1
  ---
2
- name: impact-analysis
2
+ name: hapo:impact-analysis
3
3
  description: "Analyze code change impacts and generate test scenarios. Use after code changes, before commit, or when checking for regressions. Automatically detects affected files, dependencies, and edge cases."
4
+ user-invocable: true
5
+ when_to_use: "Invoke after code changes to map regression impact and test scenarios."
6
+ category: dev-tools
7
+ keywords: [impact, regression, dependencies, testing]
4
8
  argument-hint: "[files] OR auto"
5
- version: 1.0.0
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Impact Analysis - Impact Analysis & Test Guidance
9
14
 
10
15
  Analyze the impact of code changes and provide detailed test guidance to prevent regression bugs.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:inspect
3
3
  description: "Fast codebase discovery using parallel agents. Use for file discovery, task context gathering, quick searches across directories. Supports internal (Explore) and external (Gemini) agents."
4
- version: 2.0.0
4
+ user-invocable: true
5
+ when_to_use: "Invoke for fast parallel codebase discovery and file location."
6
+ category: discovery
7
+ keywords: [discovery, search, explore, context]
5
8
  argument-hint: "[search-target] [ext]"
9
+ metadata:
10
+ author: haposoft
11
+ version: "2.0.0"
6
12
  ---
7
-
8
13
  # Inspect
9
14
 
10
15
  Fast, token-efficient codebase discovery using parallel agents to find files needed for tasks.
@@ -2,10 +2,15 @@
2
2
  name: hapo:mobile-development
3
3
  description: Build mobile apps with React Native, Flutter, Swift/SwiftUI, Kotlin/Jetpack Compose. Use for iOS/Android, mobile UX, performance optimization, offline-first, app store deployment.
4
4
  license: MIT
5
+ user-invocable: true
6
+ when_to_use: "Invoke to build or modify mobile app features and UI."
7
+ category: frontend
8
+ keywords: [mobile, app, ios, android]
5
9
  argument-hint: "[platform] [feature]"
6
- version: "1.0.0"
10
+ metadata:
11
+ author: haposoft
12
+ version: "1.0.0"
7
13
  ---
8
-
9
14
  # Mobile Development Skill
10
15
 
11
16
  Production-ready mobile development with modern frameworks, best practices, and mobile-first thinking patterns.
@@ -2,11 +2,14 @@
2
2
  name: hapo:pdf
3
3
  description: Extract text/tables, create, merge, split PDFs. Fill PDF forms programmatically. Use for PDF processing, generation, form filling, document analysis, batch operations.
4
4
  license: Proprietary. LICENSE.txt has complete terms
5
+ user-invocable: true
6
+ when_to_use: "Invoke to read, extract, or generate PDF documents."
7
+ category: document-skills
8
+ keywords: [pdf, extract, document, generate]
5
9
  metadata:
6
10
  author: haposoft
7
11
  version: "1.0.0"
8
12
  ---
9
-
10
13
  # PDF Processing Guide
11
14
 
12
15
  ## Overview
@@ -2,11 +2,14 @@
2
2
  name: hapo:pptx
3
3
  description: Create, edit, analyze .pptx PowerPoint files. Use for presentations, slides, layouts, speaker notes, template modification, content extraction, slide generation.
4
4
  license: Proprietary. LICENSE.txt has complete terms
5
+ user-invocable: true
6
+ when_to_use: "Invoke to read, create, or edit PowerPoint .pptx slides."
7
+ category: document-skills
8
+ keywords: [pptx, powerpoint, slides, office]
5
9
  metadata:
6
10
  author: haposoft
7
11
  version: "1.0.0"
8
12
  ---
9
-
10
13
  # PPTX creation, editing, and analysis
11
14
 
12
15
  ## Overview
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:question
3
3
  description: "Answer questions with evidence. Use when the user asks about project behavior, source code, specs, docs, configuration, dependencies, or external technical information; inspect the repo first, use internet/current docs when repo evidence is insufficient, and ask back only when the question cannot be answered safely."
4
+ user-invocable: true
5
+ when_to_use: "Invoke to answer project or technical questions with repo-first evidence."
6
+ category: utilities
7
+ keywords: [question, evidence, answer, research]
4
8
  argument-hint: "<question> [--repo|--web|--both|--brief|--deep]"
5
- version: 1.0.0
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Question Skill
9
14
 
10
15
  `hapo:question` is an evidence-backed question-answering skill. It answers user questions by checking the local project first, then external/current sources when the repository cannot answer the question.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:react-best-practices
3
3
  description: React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
4
+ user-invocable: true
5
+ when_to_use: "Invoke to apply React performance and architecture best practices."
6
+ category: frontend
7
+ keywords: [react, performance, patterns, hooks]
4
8
  argument-hint: "[component or pattern]"
5
- version: "1.0.0"
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Vercel React Best Practices
9
14
 
10
15
  Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:research
3
3
  description: "Research technical solutions and analyze architectures. Acts as a command facade to trigger the 'researcher' subagent for multi-source verification and deep report synthesis."
4
+ user-invocable: true
5
+ when_to_use: "Invoke for deep technical research and solution evaluation before building."
6
+ category: research
7
+ keywords: [research, evaluation, analysis, solutions]
4
8
  argument-hint: "<topic_or_question>"
5
- version: 2.0.0
9
+ metadata:
10
+ author: haposoft
11
+ version: "2.0.0"
6
12
  ---
7
-
8
13
  # Research (Delegation Facade)
9
14
 
10
15
  **Mantra:** YAGNI, KISS, DRY. Be brutal, straight to the point, and strictly authoritative.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:specs
3
3
  description: "Structured specification workflow — from vague idea to actionable task list. Includes init, requirements, design, task breakdown, review, and archiving."
4
- version: 2.0.0
4
+ user-invocable: true
5
+ when_to_use: "Invoke to turn a vague idea into an actionable, gated specification."
6
+ category: utilities
7
+ keywords: [specs, requirements, design, tasks]
5
8
  argument-hint: "<feature-description> | status | resume | --validate | archive"
9
+ metadata:
10
+ author: haposoft
11
+ version: "2.0.0"
6
12
  ---
7
-
8
13
  # Specs (SDD — Specification-Driven Development)
9
14
 
10
15
  > A structured specification system that turns vague ideas into actionable, implementable task lists.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:sync
3
3
  description: "Dumb-proof status tracker and file synchronizer. Updates spec.json, task_registry, and tasks/*.md without breaking structural schemas. Includes Auto-Audit."
4
- version: 1.0.0
4
+ user-invocable: true
5
+ when_to_use: "Invoke to synchronize spec state, docs, or task tracking after changes."
6
+ category: utilities
7
+ keywords: [sync, state, tracking, consistency]
5
8
  argument-hint: "<feature_name> <task_id|task-file> <status> [blocker] | phase <feature_name> <next_phase> | audit <feature_name>"
9
+ metadata:
10
+ author: haposoft
11
+ version: "1.0.0"
6
12
  ---
7
-
8
13
  # Sync (State Tracking Protocol)
9
14
 
10
15
  This skill safely bridges the gap between active development state and physical documentation files (`spec.json` + `task_registry` + `tasks/task-R*.md`). Instead of relying on risky raw AI edits, this skill executes precise contextual replacements.
@@ -1,10 +1,15 @@
1
1
  ---
2
2
  name: hapo:test
3
3
  description: "Run and verify project tests across all scopes: unit, integration, e2e, and UI. Blast-radius scoping for speed, chrome-devtools for UI verification, structured verdicts for downstream automation."
4
+ user-invocable: true
5
+ when_to_use: "Invoke to run and verify unit, integration, e2e, and UI tests."
6
+ category: testing
7
+ keywords: [test, unit, integration, e2e]
4
8
  argument-hint: "[scope|--full|--ui <url>|--ui-auth <url>|--ui-flow <url>]"
5
- version: 2.0.0
9
+ metadata:
10
+ author: haposoft
11
+ version: "2.0.0"
6
12
  ---
7
-
8
13
  # Test — Verify Implementation Quality
9
14
 
10
15
  Run the project's test suite, analyze results, and return a structured verdict.
@@ -1,9 +1,14 @@
1
1
  ---
2
2
  name: hapo:ui-ux-pro-max
3
3
  description: "UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples."
4
- version: "1.1.0"
4
+ user-invocable: true
5
+ when_to_use: "Invoke to choose colors, fonts, layout, and design systems."
6
+ category: frontend
7
+ keywords: [ui, ux, design-system, layout]
8
+ metadata:
9
+ author: haposoft
10
+ version: "1.1.0"
5
11
  ---
6
-
7
12
  # UI/UX Pro Max - Design Intelligence
8
13
 
9
14
  Comprehensive design guide for web and mobile applications. Contains 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, and 25 chart types across 10 technology stacks. Searchable database with priority-based recommendations.
@@ -2,10 +2,15 @@
2
2
  name: hapo:web-testing
3
3
  description: Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
4
4
  license: Apache-2.0
5
+ user-invocable: true
6
+ when_to_use: "Invoke to test web flows in a real browser end-to-end."
7
+ category: testing
8
+ keywords: [web-testing, e2e, browser, validation]
5
9
  argument-hint: "[test-type] [target]"
6
- version: "3.0.0"
10
+ metadata:
11
+ author: haposoft
12
+ version: "3.0.0"
7
13
  ---
8
-
9
14
  # Web Testing Skill
10
15
 
11
16
  Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.
@@ -2,11 +2,14 @@
2
2
  name: hapo:xlsx
3
3
  description: Create, edit, analyze spreadsheets (.xlsx, .csv, .tsv). Use for Excel formulas, data analysis, visualization, formatting, pivot tables, charts, formula recalculation.
4
4
  license: Proprietary. LICENSE.txt has complete terms
5
+ user-invocable: true
6
+ when_to_use: "Invoke to read, create, or edit Excel .xlsx spreadsheets."
7
+ category: document-skills
8
+ keywords: [xlsx, excel, spreadsheet, office]
5
9
  metadata:
6
10
  author: haposoft
7
11
  version: "1.0.0"
8
12
  ---
9
-
10
13
  # Requirements for Outputs
11
14
 
12
15
  ## All Excel files