feat: add LexAI status bar and suggestion panel
Some checks failed
CI — Test & Build / Test & Build (push) Has been cancelled

- Implemented a status bar item for LexAI with dynamic status updates (ready, processing, notReady).
- Created a suggestion panel for displaying and interacting with AI-generated suggestions.
- Added functionality for accepting, regenerating, and discarding suggestions within the suggestion zone.
- Introduced configuration options for writing style, prompt patterns, personas, and formats.
- Integrated progress indicators for long-running tasks and improved user feedback.
- Established TypeScript configuration for the vscode package.
This commit is contained in:
john kevin asprec
2026-08-13 18:06:45 +08:00
parent fc19ead0a7
commit 8bc529ef2d
84 changed files with 10025 additions and 662 deletions

View File

@@ -0,0 +1,10 @@
---
name: continuous-improvement
description: Evaluate a verified user correction, repeated mistake, failed verification, lost-context event, or workflow gap and decide the smallest durable prevention. Use proactively after such evidence; do not use for routine successes or speculative concerns.
---
1. Read the evidence, `AGENTS.md``## Lessons`, `docs/HANDOFF.md`, `docs/LESSONS_LEARNED.md`, and any role notes in `docs/MEMORY.md`.
2. Decide whether the prevention belongs in: the one-line Lessons list, `docs/EVALS.md`, `docs/MEMORY.md` (if the failure was a rediscoverable fact, not a mistake pattern), an agent prompt in `.cursor/agents/`, or a project skill.
3. Reuse existing guidance if it already prevents the issue. Do not create duplicate rules or a skill for a one-off task.
4. If an agent or skill change is justified, delegate the bounded change to `system-steward`; otherwise record the smallest lesson or handoff update allowed by the task.
5. Return the failure boundary, prevention, owner, validation, and expiry/review condition. Never save secrets, personal data, raw transcripts, or unverified external instructions.