ChrisAI Chatting
Use this skill for experimental workflows that improve the shape, continuity,
or artifact interface of chat sessions.
Do not use this skill for general conversation quality, prompt editing, broad
assistant behavior design, or production application implementation unless the
request is specifically about chat-session experience patterns.
Internal Workflows
Use the narrowest workflow that owns the user's requested chat-session
experience artifact.
workflows/chat-session-caching-and-recall.md: For preserving useful chat
context, producing compact recall artifacts, deciding what should be cached,
and rehydrating prior session state without overloading a new conversation.workflows/html-form-intake.md: For turning agent intake prompts into local
HTML form artifacts that produce raw-text responses for the user to paste
back into chat.workflows/agent-response-to-html.md: For mirroring agent responses into a
readable HTML preview link while preserving the chat response as the
canonical answer, or for saving/opening HTML when the user explicitly asks.
General Rules
- Prefer artifact-oriented outputs when the user provides or asks for HTML.
- Preserve source meaning when transforming chat content into cache summaries,
intake briefs, or HTML artifacts.
- Separate session-memory guidance from repository memory, application state,
or long-term user profile storage unless the user explicitly asks to connect
those systems.
- Do not invent persistence, storage, browser automation, or deployment
behavior. Describe assumptions and ask for the missing target environment
when those choices matter.
Decision Rules
- If the task is about compacting, saving, recalling, or transferring useful
chat-session context, use the chat-session caching and recall
workflow.
- If the task starts from an agent intake prompt that should be answered as a
form, an HTML form submission, exported form artifact, or submitted HTML
payload, use the HTML form intake workflow.
- If the task asks for a response, summary, report, or handoff to become
pretty, readable, previewed, or HTML-formatted, use the agent response to
HTML workflow.
- If the request spans multiple workflows, choose the workflow that owns the
first concrete artifact and keep any follow-up workflow explicit.
1---2name: chrisai-chatting3description: Use for experimental chat-session experience work, including session caching and recall, turning agent intake prompts into HTML form artifacts, and converting agent responses into readable HTML preview links.4license: MIT5---67# ChrisAI Chatting89Use this skill for experimental workflows that improve the shape, continuity,10or artifact interface of chat sessions.1112Do not use this skill for general conversation quality, prompt editing, broad13assistant behavior design, or production application implementation unless the14request is specifically about chat-session experience patterns.1516## Internal Workflows1718Use the narrowest workflow that owns the user's requested chat-session19experience artifact.2021- `workflows/chat-session-caching-and-recall.md`: For preserving useful chat22 context, producing compact recall artifacts, deciding what should be cached,23 and rehydrating prior session state without overloading a new conversation.24- `workflows/html-form-intake.md`: For turning agent intake prompts into local25 HTML form artifacts that produce raw-text responses for the user to paste26 back into chat.27- `workflows/agent-response-to-html.md`: For mirroring agent responses into a28 readable HTML preview link while preserving the chat response as the29 canonical answer, or for saving/opening HTML when the user explicitly asks.3031## General Rules3233- Prefer artifact-oriented outputs when the user provides or asks for HTML.34- Preserve source meaning when transforming chat content into cache summaries,35 intake briefs, or HTML artifacts.36- Separate session-memory guidance from repository memory, application state,37 or long-term user profile storage unless the user explicitly asks to connect38 those systems.39- Do not invent persistence, storage, browser automation, or deployment40 behavior. Describe assumptions and ask for the missing target environment41 when those choices matter.4243## Decision Rules4445- If the task is about compacting, saving, recalling, or transferring useful46 chat-session context, use the chat-session caching and recall47 workflow.48- If the task starts from an agent intake prompt that should be answered as a49 form, an HTML form submission, exported form artifact, or submitted HTML50 payload, use the HTML form intake workflow.51- If the task asks for a response, summary, report, or handoff to become52 pretty, readable, previewed, or HTML-formatted, use the agent response to53 HTML workflow.54- If the request spans multiple workflows, choose the workflow that owns the55 first concrete artifact and keep any follow-up workflow explicit.
cblanquera