tutuca 0.11.1 → 0.11.2

package/skill/tutuca-source/SKILL.md

@@ -1,33 +0,0 @@
----
-name: tutuca-source
-description: The bundled framework source (`dist/tutuca.ext.js`) wrapped as a skill so the agent can grep it. Use only when debugging — to confirm what the framework actually does, trace an error from the framework, or find the implementation of a method you saw in a stack trace. Always reach for `grep_skill_files` first, then `load_skill_file` with `startLine`/`endLine` to read a window around a hit. Not for component-authoring guidance — use the `tutuca` skill for that.
----
-
-<!-- This file is generated by scripts/build-skill.js. Do not edit. -->
-
-# Tutuca source
-
-The bundled framework that ships to users — the ESM at `dist/tutuca.ext.js`.
-This skill exposes it as one file (`tutuca.ext.js`) so the agent can read
-the implementation when needed.
-
-## How to read it
-
-- It is **one large file** (~3.8K lines). Loading it whole will flood your
-  context — always `grep_skill_files("tutuca-source", "<pattern>")` first,
-  then `load_skill_file("tutuca-source", "tutuca.ext.js", { startLine, endLine })`
-  to pull a small window around a match.
-- It is the **bundled** output: ESM, not minified, no source map. Class and
-  function names match the original sources; comments do not survive.
-
-## When to use
-
-- A `lint_component` / `render_component` result mentions a framework
-  function or error string you don't recognise — grep for it.
-- A component crashes inside the framework — grep the error message or the
-  framework function in the stack trace.
-- A behavior is surprising and you want to confirm exactly what the framework
-  does, not what the docs say it does.
-
-**Don't** use this skill for *how to write* tutuca components — that's the
-`tutuca` skill. Reach here only when you need to read the implementation.