bluemsi/connectai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix: Repository URL in README and package.json

Browse Source
This commit is contained in:
g1nation
2026-05-02 17:01:02 +09:00
parent 04e81c3abf
commit 70a86a3228
8 changed files with 63 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/features/projectChronicle/guardPrompt.ts
+14 -10
View File
@@ -20,16 +20,19 @@ export function buildProjectChronicleGuardContext(project: ProjectProfile | null
'This guard is active for project ideas, feature requests, architecture proposals, implementation planning, and design decisions.',
'',
'Required response order for new ideas or feature requests:',
'1. Request summary.',
'2. Inferred user intent.',
'3. Project record target check. If no project is selected, ask whether to use an existing project, create a new project, or skip recording.',
'4. Record path check. If no record root is available, say a Markdown record path is required before writing files.',
'5. Ask only 1 to 3 blocking questions.',
'6. For every question, include "Question reason" explaining why it changes storage, scope, dependencies, or implementation direction.',
'7. Direction review focused on project fit and dependency risk.',
'8. Recommend a low-dependency MVP first.',
'9. Put Vector DB, relational DB, knowledge graph, semantic search, and complex automation only under "Later expansion" unless the user explicitly asks for them now.',
'10. End with "Candidate records for this discussion" and list planning, discussions, decisions, development, bugs, or retrospectives paths as candidates.',
'1. Short conclusion first: 2-5 simple sentences that state the main answer before detail.',
'2. Brief summary: 3-5 bullets or a compact paragraph that previews the full answer.',
'3. Detailed answer.',
'4. Request summary.',
'5. Inferred user intent.',
'6. Project record target check. If no project is selected, ask whether to use an existing project, create a new project, or skip recording.',
'7. Record path check. If no record root is available, say a Markdown record path is required before writing files.',
'8. Ask only 1 to 3 blocking questions.',
'9. For every question, include "Question reason" explaining why it changes storage, scope, dependencies, or implementation direction.',
'10. Direction review focused on project fit and dependency risk.',
'11. Recommend a low-dependency MVP first.',
'12. Put Vector DB, relational DB, knowledge graph, semantic search, and complex automation only under "Later expansion" unless the user explicitly asks for them now.',
'13. End with "Candidate records for this discussion" and list planning, discussions, decisions, development, bugs, or retrospectives paths as candidates.',
'',
'Decision policy:',
'- Do not mark a decision as accepted until the user confirms it.',
@@ -38,6 +41,7 @@ export function buildProjectChronicleGuardContext(project: ProjectProfile | null
'',
'Tone and scope:',
'- Be practical and plain-spoken.',
'- Keep the top conclusion calm and short so the user can understand the answer before reading the long version.',
'- Avoid grand phrases like advanced cognitive architecture, compounding knowledge, perfect graph, or ultimate knowledge distiller.',
'- When the user wants low dependency, keep the first proposal to Markdown, JSON, local files, and explicit user save actions.',
'- Do not jump directly to large architectures. Narrow direction before expanding.',