feat: add LexAI status bar and suggestion panel
Some checks failed
CI — Test & Build / Test & Build (push) Has been cancelled
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:
12
.cursor/skills/self-model-audit/SKILL.md
Normal file
12
.cursor/skills/self-model-audit/SKILL.md
Normal file
@@ -0,0 +1,12 @@
|
||||
---
|
||||
name: self-model-audit
|
||||
description: Compare what the harness believes about the operator and project (docs/SELF_MODEL.md, AGENTS.md, agent prompts) against what recent work and corrections actually reveal, and propose edits that close the gap. Use periodically or after repeated "that's not what I meant" signals.
|
||||
---
|
||||
|
||||
Find where the harness is modeling a stale, aspirational, or simply wrong version of the operator or the project — then propose the smallest edits that make the model match reality. Read-only: propose changes, don't apply them without approval.
|
||||
|
||||
1. **Read the belief set.** `docs/SELF_MODEL.md`, `docs/PROJECT_BRIEF.md`, the operator/project instructions in `AGENTS.md`, active `## Lessons`, and any role notes in `docs/MEMORY.md`. Note every claim the system holds about who the operator is, what they want, and how they work.
|
||||
2. **Read the evidence.** Recent handoffs (`docs/HANDOFF.md`), recorded decisions (`docs/DECISIONS.md`), corrections captured in `LESSONS_LEARNED.md`, and the shape of recent tasks. Infer what the operator's actual behavior and choices reveal.
|
||||
3. **Find the gaps.** Flag each place the stated model conflicts with revealed behavior: preferences that changed, aspirational goals the system optimizes for but recent work contradicts, assumptions never re-confirmed, and voice/style drift. Distinguish "genuinely stale" from "reasonable disagreement" — do not pathologize a deliberate choice.
|
||||
4. **Propose edits.** For each gap, give the exact `SELF_MODEL.md` (or `AGENTS.md` instruction) change that closes it, tied to the evidence that justifies it. Prefer removing an over-specific belief over adding more.
|
||||
5. **Return** the gap list (belief → contradicting evidence → proposed edit), and route any accepted change through the operator or `system-steward`. Never infer a sensitive attribute, and never store credentials, financial/health data, or anything the operator hasn't agreed to persist.
|
||||
Reference in New Issue
Block a user