howone 0.1.23 → 0.1.26

package/templates/vite/.howone/skills/howone-sdk/04-ai/03-ai-sdk-handoff.md

@@ -1,80 +0,0 @@
-# AI SDK Handoff
-
-Use this reference after AI capability artifacts have been synced and app code needs to call the
-workflow.
-
-## Binding Source
-
-Generate `src/lib/sdk.ts` from `.howone/ai/manifest.json`. Do not write AI bindings from memory or
-from the original user prompt.
-
-For each manifest capability:
-
-1. Read `name`.
-2. Read `workflowId`.
-3. Read `inputSchema`.
-4. Read `outputSchema`.
-5. Generate zod input and output schemas from the JSON Schema fields.
-6. Bind with `defineAiAction(name, { workflowId, inputSchema, outputSchema })`.
-
-`workflowId` is mandatory. Without it, the SDK falls back to the action name as the execution URL
-segment, which is not a workflow UUID.
-
-## Output Handling
-
-For a typed action with `outputSchema`, `.run()` returns the validated workflow output payload.
-The SDK unwraps the EAX execution envelope and validates `finalResult` internally.
-
-Use this pattern:
-
-```ts
-const output = await howone.ai.generateSummary.run(input)
-// output is GenerateSummaryOutput when outputSchema is configured.
-```
-
-Do not read `raw.finalResult`, `raw.result`, or `raw.data.result` from a typed action result. Those
-paths are execution/SSE internals. App code should use the value returned by `.run()` directly.
-
-Do not make every output field `.optional()` or add `.passthrough()` to hide validation errors.
-Required fields in the manifest must stay required in Zod. If validation fails, inspect
-`AiSchemaValidationError.issues` and fix the capability contract or workflow output mapping.
-
-## UI State
-
-AI calls should run in event handlers, effects, or explicit async actions. Never call
-`howone.ai.*.run()` inside JSX render.
-
-Recommended UI states:
-
-- idle
-- running
-- succeeded
-- failed
-- cancelled when using streaming
-
-For streaming, keep the `AiSession` in a ref and call `cancel()` from the UI.
-
-## Persistence Handoff
-
-If the app stores generated output:
-
-1. Run the AI workflow.
-2. Use the typed output returned by `.run()`.
-3. Write the resulting data through `howone.entities.*`.
-
-Do not ask the workflow to write to the database. Do not pass owner fields for authenticated
-user-owned entities; HowOne derives ownership from the JWT.
-
-## Workflow Edit Handoff
-
-When editing an external workflow implementation later, use `external-ai-capability` with:
-
-- `mode: "update"`
-- `capabilityName`
-- `workflowConfigID`
-- `updatePrompt`
-
-`workflowConfigID` is not `workflowId`. It comes from a confirmed workflow status result:
-`payload.workflow_details.new_workflow_config_id`.
-
-If the schema changed, update and sync the capability contract before submitting the workflow edit.

package/templates/vite/.howone/skills/howone-sdk/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "HowOne App Architecture"
-  short_description: "Design HowOne app schema, SDK bindings, and auth/data integration."
-  default_prompt: "Use this skill to choose the HowOne app architecture track, then implement schema, SDK bindings, or frontend SDK calls correctly."