@mindstudio-ai/remy 0.1.53 → 0.1.54
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/automatedActions/reviseSelectedText.md +0 -0
- package/dist/compaction/conversation.md +7 -0
- package/dist/compaction/subagent.md +7 -0
- package/dist/headless.js +455 -69
- package/dist/index.js +462 -59
- package/dist/prompt/compiled/design.md +1 -1
- package/dist/prompt/static/team.md +1 -3
- package/dist/subagents/designExpert/prompts/components.md +4 -0
- package/dist/subagents/designExpert/prompts/identity.md +4 -0
- package/dist/subagents/productVision/prompt.md +4 -0
- package/package.json +1 -1
|
File without changes
|
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
You are summarizing a conversation between a user and an AI coding agent called Remy that builds MindStudio apps. Your summary will replace the conversation history — the agent will only see your summary plus any new messages, so it must capture everything needed to continue working.
|
|
2
|
+
|
|
3
|
+
Summarize what happened during each conversation turn. What did the user request? What actions were taken, what key decisions were made, what was built or changed? Were there errors, was there work not done, were there lessons to be learned (e.g., when fixing bugs or disambiguating user intent)? What was the overall tone of the conversation? Were there specific phrases or ideas the user used when describing things that feel important or informative to preserve?
|
|
4
|
+
|
|
5
|
+
Do not include full file contents, tool call details (just what was called and what happened), or other overly-verbose content. Preserve concrete values (e.g., URLs, hex codes, font names) exactly.
|
|
6
|
+
|
|
7
|
+
Write in concise, factual prose. Use bullet points. Be thorough and comprehensive. Reply only with the summarized conversation and absolutely no other text.
|
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
You are summarizing a conversation between a develoepr and one of its specialists. Your summary will replace the conversation history for this specialist — it will only see your summary plus any new messages, so it must capture everything needed to continue its work.
|
|
2
|
+
|
|
3
|
+
Summarize what happened during each conversation turn. What did the developer request? What actions were taken, what key decisions were made, what was built or changed? Were there errors, was there work not done, were there lessons to be learned?
|
|
4
|
+
|
|
5
|
+
Do not include full file contents, tool call details (just what was called and what happened), or other overly-verbose content. Preserve concrete values (e.g., URLs, hex codes, font names) exactly.
|
|
6
|
+
|
|
7
|
+
Write in concise, factual prose. Use bullet points. Be thorough and comprehensive. Reply only with the summarized conversation and absolutely no other text.
|