From cf7461ffeb4f53f3f50c9c692a2e4fdcecf17e82 Mon Sep 17 00:00:00 2001 From: Agando Date: Thu, 9 Jul 2026 06:00:32 +0200 Subject: auto: 2026-07-09_06:00 changes --- skills/suggestion-engine.json | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'skills/suggestion-engine.json') diff --git a/skills/suggestion-engine.json b/skills/suggestion-engine.json index e3a06f8..da4ffb4 100644 --- a/skills/suggestion-engine.json +++ b/skills/suggestion-engine.json @@ -1,9 +1,14 @@ { "name": "suggestion-engine", - "description": "", - "tags": [], - "category": "system", + "description": "A systematic process for recording, analyzing, and implementing user suggestions for system improvement.", + "tags": [ + "optimization", + "feedback", + "roadmap", + "dev" + ], + "category": "general", "created": "2026-06-18T01:22:19.666Z", - "updated": "2026-06-18T01:22:19.666Z", + "updated": "2026-06-24T21:58:03.530Z", "content": "---\nname: suggestion-engine\ndescription: A systematic process for recording, analyzing, and implementing user suggestions for system improvement.\ntags: [optimization, feedback, roadmap, dev]\n---\n\n# Suggestion Engine Workflow\n\nThis skill provides a structured framework to ensure user ideas are not lost and are implemented with architectural integrity.\n\n## 📋 1. Recording Process\nEvery suggestion must be logged into the `suggestion_log.json` with the following schema:\n- **ID**: Unique incremental ID.\n- **Timestamp**: ISO date.\n- **Category**: (UI/UX, Performance, Security, Feature, Logic).\n- **Description**: Detailed user request.\n- **Status**: `proposed` | `analyzing` | `implementing` | `completed` | `rejected`.\n- **Priority**: `low` | `medium` | `high` | `critical`.\n\n## ⚙️ 2. Analysis Framework\nBefore implementing a suggestion, the AI must perform a \"Impact Analysis\":\n1. **Dependency Check**: Which modules are affected?\n2. **Security Audit**: Does this introduce a new attack vector?\n3. **Performance Cost**: Will this increase latency or memory bloat?\n4. **UI Consistency**: Does this align with the existing design language?\n\n## 🚀 3. Implementation Cycle\n1. **Propose**: Define the technical approach.\n2. **Draft**: Modify the module code (using `edit_module`).\n3. **Test**: Run `test_module` to verify correctness.\n4. **Verify**: User confirmation of the improvement.\n5. **Archive**: Update status to `completed` and document the change.\n\n## 🛠️ Commands Reference\n- `suggestion-log` -> List all current suggestions.\n- `suggestion-add [text]` -> Append new idea to log.\n- `suggestion-promote [id]` -> Move from proposed to analyzing.\n" } \ No newline at end of file -- cgit v1.2.3