@soederpop/luca 0.0.8 → 0.0.9

package/AGENTS.md

@@ -26,6 +26,7 @@ On the frontend the browser container is perfect for highly reactive, stateful w
 		- `luca describe diskCache`
 		- `luca describe` describe the container itself
 		- `luca describe servers` describe which servers are available
+		- `luca describe ui.banner` describe a specific method or getter on a helper
 		- the arguments to describe are pretty forgiving and permissive
 
 **IMPORTANT NOTE** When trying to investigate features, clients, servers, etc, see if these tools can help you first instead of searching for files and reading them that way.  If youw ant to understand what they do, vs how theyre actually implemented

package/CLAUDE.md

@@ -26,6 +26,7 @@ On the frontend the browser container is perfect for highly reactive, stateful w
 		- `luca describe diskCache`
 		- `luca describe` describe the container itself
 		- `luca describe servers` describe which servers are available
+		- `luca describe ui.banner` describe a specific method or getter on a helper
 		- the arguments to describe are pretty forgiving and permissive
 
 **IMPORTANT NOTE** When trying to investigate features, clients, servers, etc, see if these tools can help you first instead of searching for files and reading them that way.  If youw ant to understand what they do, vs how theyre actually implemented

package/docs/bootstrap/CLAUDE.md

@@ -15,6 +15,7 @@ The `luca` binary is available in the path. Key commands:
 - `luca` — list available commands (built-in + project commands)
 - `luca eval "expression"` — evaluate JS with the container in scope
 - `luca describe <name>` — full docs for any feature, client, or server (e.g. `luca describe fs`)
+- `luca describe <name>.<member>` — docs for a specific method or getter (e.g. `luca describe ui.banner`, `luca describe fs.readFile`)
 - `luca describe features` — index of all available features (also: `clients`, `servers`)
 - `luca serve` — start a local server using `endpoints/` folder
 - `luca run script.ts` — run a script with the container
@@ -28,7 +29,7 @@ The `luca` binary is available in the path. Key commands:
 
 ## Learning the Framework
 
-1. **Discover** — Run `luca describe features`, `luca describe clients`, `luca describe servers` to see what's available. Then `luca describe <name>` for full docs on any helper. This is your first move, always. (See `.claude/skills/luca-framework/SKILL.md` for the full mental model.)
+1. **Discover** — Run `luca describe features`, `luca describe clients`, `luca describe servers` to see what's available. Then `luca describe <name>` for full docs on any helper, or `luca describe <name>.<member>` to drill into a specific method or getter. This is your first move, always. (See `.claude/skills/luca-framework/SKILL.md` for the full mental model.)
 2. **Build** — Run `luca scaffold <type> --tutorial` before creating a new helper. It covers the full guide for that type.
 3. **Prototype** — Use `luca eval "expression"` to test container code before wiring up full handlers. Reach for eval when you're stuck — it gives you full runtime access.
 4. **Reference** — Browse `.claude/skills/luca-framework/references/api-docs/` for pre-generated API docs

package/docs/bootstrap/SKILL.md

@@ -36,6 +36,19 @@ luca describe express      # full docs for the express server
 luca describe git fs proc  # multiple helpers in one shot
 ```
 
+### Drill into a specific method or getter
+
+Use dot notation to get docs for a single method or getter on any helper:
+
+```shell
+luca describe ui.banner            # docs for the banner() method on ui
+luca describe fs.readFile          # docs for readFile() on fs
+luca describe ui.colors            # docs for the colors getter on ui
+luca describe git.branch           # docs for the branch getter on git
+```
+
+This shows the description, parameters, return type, and examples for just that member. If the member doesn't exist, it lists all available methods and getters on the helper.
+
 ### Get targeted documentation
 
 You can filter to only the sections you need:
@@ -63,7 +76,7 @@ luca describe --help       # full flag reference for describe
 luca help scaffold         # help for any command
 ```
 
-**Use `luca describe` liberally.** It is the fastest, safest way to understand what the container provides. Every feature, client, and server is self-describing — if you know a name, describe will tell you everything about it.
+**Use `luca describe` liberally.** It is the fastest, safest way to understand what the container provides. Every feature, client, and server is self-describing — if you know a name, describe will tell you everything about it. Use dot notation (`ui.banner`, `fs.readFile`) when you need docs on just one method or getter.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@soederpop/luca",
-  "version": "0.0.8",
+  "version": "0.0.9",
   "website": "https://luca.soederpop.com",
   "description": "lightweight universal conversational architecture AKA Le Ultimate Component Architecture AKA Last Universal Common Ancestor, part AI part Human",
   "author": "jon soeder aka the people's champ <jon@soederpop.com>",

package/src/commands/run.ts

@@ -173,7 +173,10 @@ async function runMarkdown(scriptPath: string, options: z.infer<typeof argsSchem
 				continue
 			}
 
-			if (meta && typeof meta === 'string' && meta.toLowerCase().includes('skip')) continue
+			if (meta && typeof meta === 'string' && meta.toLowerCase().includes('skip')) {
+				console.log(container.ui.markdown(['```' + lang, value, '```'].join('\n')))
+				continue
+			}
 
 			console.log(container.ui.markdown(['```' + lang, value, '```'].join('\n')))