@soederpop/luca 0.0.22 → 0.0.23

package/docs/prompts/check-for-undocumented-features.md

@@ -0,0 +1,27 @@
+---
+agentOptions:
+    permissionMode: bypassPermissions
+---
+
+# Check for undocumented features
+
+The luca introspection and luca cli's describe command is powered by the JSDoc comments in the code base, and the values passed to the describe methods in the zod schema.  This documentation is what is fed to AI Coding assistants to be able to understand how to use the individual features
+
+Please scan the following paths:
+
+```ts
+const fm = await container.feature('fileManager').start()
+const results = fm.match(['src/node/features/*.ts', 'src/agi/features/*.ts', 'src/web/features/*.ts'])
+console.log(results.join("\n"))
+```
+
+Please ensure every feature has accurate and valid JSDoc documentation for the class definitions, methods, and getters.
+
+Validate the output of `bun run src/cli/cli.ts describe whatever` for each item you're working on, that it displays properly, is easy to understand, accurate, in terms of how your comments display there.  You may need to run `bun run src/cli/cli.ts introspect` to generate the build time data.
+
+You can pass `--platform=web` to see web specific output.
+
+## Quality not just Quantity
+
+- The presence of documentation isn't sufficient.  Is it good documentation? Is it not overly verbose? Does it not explain stuff that doesn't matter? Is it accurate? If there are examples, do they work?
+- The main consumer of `luca describe` will be an LLM so token budget matters.  Every word has to be doing work.  It should still be nice to look at for human coders too.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@soederpop/luca",
-  "version": "0.0.22",
+  "version": "0.0.23",
   "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/prompt.ts

@@ -837,7 +837,10 @@ export default async function prompt(options: z.infer<typeof argsSchema>, contex
 		const candidate = paths.resolve(target)
 		if (fs.exists(candidate)) {
 			allPaths.push(target)
-			target = 'claude'
+			// this gives a way for you to say on a per project basis what you want the default coding assistant to be for the prompt command	
+			// TODO need to document this somewhere
+			const { codingAssistant } = (container.manifest.luca || {})
+			target = codingAssistant || 'claude'
 		}
 	}