@schalkneethling/calavera-skill-calavera 0.2.0 → 0.2.2

package/calavera-artifact.json

@@ -6,6 +6,6 @@
   "displayName": "Calavera",
   "payload": "payload/calavera",
   "compatibility": {
-    "calavera": ">=2.2.0 <3"
+    "calavera": ">=2.2.0"
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@schalkneethling/calavera-skill-calavera",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "Calavera artifact for Calavera.",
   "license": "MIT",
   "repository": {

package/payload/calavera/SKILL.md

@@ -11,11 +11,11 @@ Use Calavera to compose and apply project tooling through its MCP tools whenever
 
 1. Confirm whether Calavera MCP tools are available. Look for tools named `inspect_project`, `list_profiles`, `list_integrations`, `list_ai_artifacts`, `compose_recipe`, `validate_recipe`, `explain_recipe`, `dry_run_apply`, and `apply_recipe`.
 2. If the Calavera MCP tools are not available, stop and help the user register or repair the MCP server before composing or applying anything. Do not inspect npm cache internals or import Calavera source files from package cache paths as a substitute for MCP setup.
-3. Call `inspect_project` when available, or inspect the project manually only when the MCP server cannot be registered and the user chooses a fallback flow. Check files such as `package.json`, `calavera.config.json`, `.editorconfig`, `eslint.config.js`, `oxlint.json`, `.prettierrc.json`, `.stylelintrc.json`, and `tsconfig.json`.
+3. Call `inspect_project` when available, or inspect the project manually only when the MCP server cannot be registered and the user chooses a fallback flow. Check files such as `package.json`, `calavera.config.json`, `.editorconfig`, and `.stylelintrc.json`.
    If likely conflicts exist, pause before applying changes. List each conflict as a hard stop or a migration decision the user can approve, and use `dry_run_apply` to show concrete impact when adoption still looks possible.
 4. Use AskUserTool or the agent client's equivalent when available to clarify profile preferences, framework needs, conflict decisions, and apply approval. If no such tool exists, ask the user directly.
 5. List choices with `list_profiles`, `list_integrations`, and `list_ai_artifacts`. Use `describe_integration` when the user asks for more information or when you need to compare options.
-6. Choose either Oxfmt or Prettier for formatting, never both.
+6. Calavera does not scaffold a JavaScript or TypeScript formatter; in a `vp`-managed project, formatting comes from `vp fmt`.
 7. Once the profile and requirements are clear, compose the recipe with `compose_recipe`.
 8. Validate and explain it with `validate_recipe` and `explain_recipe`.
 9. Present `dry_run_apply` output to the user before changing files, including inspection findings, omitted script explanations, ownership notes, and planned file changes.