howone 0.2.0 → 0.2.2

package/templates/vite/.howone/skills/howone/03-ai-capabilities/05-ai-feature-playbooks.md

@@ -138,30 +138,6 @@ Rules:
 - output descriptions must specify language;
 - if user asks for latest/current, this workflow must retrieve data internally.
 
-## Playbook: RSS Digest
-
-Use when the user provides or asks for a specific RSS feed URL and wants feed items, summaries, or
-a digest.
-
-Inputs:
-
-- `rss_url`;
-- optional `item_limit`;
-- optional `language`;
-- optional `summary_instruction`.
-
-Outputs:
-
-- `items` with title, URL, published date, and optional summary;
-- optional `digest` when the product needs a synthesized overview.
-
-Rules:
-
-- use RSS feed fetching only for explicit RSS URLs;
-- use web search/crawling for general latest news without an RSS URL;
-- do not treat RSS as arbitrary third-party API integration;
-- if users need saved feed history, persist items or digests through entities.
-
 ## Playbook: Stock Analysis
 
 Use for historical price analysis.
@@ -245,7 +221,7 @@ Output:
 Rules:
 
 - single speaker per call;
-- dialogue should generate multiple clips and concatenate audio files;
+- dialogue should generate multiple clips and merge;
 - persist audio URL through entity if user needs library/history.
 
 ## Playbook: Video Generator
@@ -269,46 +245,6 @@ Rules:
 - for longer output, compose multiple clips and concatenate;
 - first-frame image helps consistency.
 
-## Playbook: Video Frame Utility
-
-Use when the product needs a first frame and last frame from a video URL.
-
-Inputs:
-
-- `source_video_url`.
-
-Outputs:
-
-- `first_frame_image_url`;
-- `last_frame_image_url`.
-
-Rules:
-
-- use this only for first/last-frame extraction;
-- do not promise arbitrary frame-by-frame analysis or video editing;
-- persist extracted image URLs through entities if the app needs history.
-
-## Playbook: File Creator / Modifier
-
-Use when the product needs to create or modify a supported file: text, PDF, DOCX, PPTX, or XLSX.
-
-Inputs:
-
-- `file_type`: txt, md, pdf, docx, pptx, or xlsx;
-- `content_or_instruction`;
-- optional `source_file_url` for modification.
-
-Output:
-
-- `file_url`.
-
-Rules:
-
-- create/modify supported file types only;
-- app uploads source files first and passes URLs;
-- do not use generated files as a database;
-- persist file URLs through entities if users need history, folders, sharing, or review.
-
 ## RAG Playbook
 
 Use only when app needs question answering over user/project documents.
@@ -334,7 +270,6 @@ Rules:
 - Verify capability exists in `03-service-capability-catalog.md`.
 - Use URL inputs for files/media.
 - Keep outputs minimal and product-facing.
-- Do not design streaming/realtime AI output.
 - Decide persistence separately.
 - Generate SDK bindings only after manifest sync and external workflow submit.
 - Use app-owned UI for progress/errors.

package/templates/vite/.howone/skills/howone/SKILL.md

@@ -17,7 +17,7 @@ Load only the track needed for the user's request. Do not read SDK files while d
 
 Use this skill before work when any condition is true:
 
-- You need to decide whether HowOne can satisfy the user's request, whether it is app-owned, or whether the request needs clarification before handoff.
+- You need to decide whether HowOne can satisfy the user's request, whether an explicit user-owned integration is outside platform contracts, or whether the request needs clarification before handoff.
 - The user asks for persisted app data, backend schema, entity fields, access, indexes, public pages, private history, or Mongo-backed records.
 - The user asks for HowOne AI behavior, capability contracts, workflow generation/update/status, or `external-ai`.
 - The work reads or writes `.howone/database/*`, `.howone/ai/*`, `src/lib/sdk.ts`, or app code using `@howone/sdk` / `howone.*`.
@@ -37,7 +37,7 @@ Classify the request before tool writes:
 | Add/change HowOne AI behavior | AI | `ai-capability-design`, `sync_ai_artifacts`, `external-ai-capability`, `03-ai-capabilities/*` |
 | Call HowOne from generated app code | SDK | `src/lib/sdk.ts`, synced manifests, `04-app-sdk/*` |
 | UI only, no HowOne data or AI | None | edit app code only |
-| User-owned external services | App-owned | integrate in app code/config; do not fake platform contracts |
+| Explicit user-owned integrations | App-owned | only when the user explicitly asks to connect something outside HowOne; do not reclassify ordinary AI/data/auth app requests |
 
 If multiple tracks apply, process them in dependency order:
 
@@ -72,7 +72,8 @@ get_current_schema -> apply_schema_patch -> sync_schema_artifacts -> read .howon
 AI contract:
 
 ```text
-get_current_ai_capabilities -> apply_capability_patch -> sync_ai_artifacts -> external-ai-capability -> read .howone/ai/manifest.json
+get_current_ai_capabilities -> apply_capability_patch -> sync_ai_artifacts -> external-ai-capability
+-> wait for terminal result -> sync_ai_artifacts -> read .howone/ai/manifest.json
 ```
 
 No contract dry-run step. Normal generation applies one well-formed patch directly. For destructive,
@@ -144,5 +145,5 @@ read synced manifests -> update src/lib/sdk.ts -> implement UI/server code using
 - Backend and AI design references must not include SDK implementation work.
 - SDK references must not invent backend or AI contracts; they consume synced manifests.
 - AI workflows must not perform database CRUD; persistence is app code through entities.
-- User-owned infrastructure is app code, not a platform gap.
+- Explicit user-owned integrations are app code, not a platform gap.
 - Platform gap means missing HowOne contract/tool/catalog support, not an unsupported technology name.