diff options
| author | Agando <roduccomm@gmail.com> | 2026-06-22 18:00:43 +0200 |
|---|---|---|
| committer | Agando <roduccomm@gmail.com> | 2026-06-22 18:00:43 +0200 |
| commit | 6f6161562c5f1028256f3163083b665719741646 (patch) | |
| tree | ccc9ab59e8433555557b6db8b6c1d4940b8652a4 /skills/suggestion-engine.json | |
| parent | 82270d6f2685d84d5c9b4a454ae7260de75d34cf (diff) | |
auto: 2026-06-22_18:00 changes
Diffstat (limited to 'skills/suggestion-engine.json')
| -rw-r--r-- | skills/suggestion-engine.json | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/skills/suggestion-engine.json b/skills/suggestion-engine.json new file mode 100644 index 0000000..e3a06f8 --- /dev/null +++ b/skills/suggestion-engine.json @@ -0,0 +1,9 @@ +{ + "name": "suggestion-engine", + "description": "", + "tags": [], + "category": "system", + "created": "2026-06-18T01:22:19.666Z", + "updated": "2026-06-18T01:22:19.666Z", + "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 |