8bc529ef2d
- 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.
2.9 KiB
name, description
| name | description |
|---|---|
| project-init | First initialization of a project using this kit — bind the model lanes to real models, then turn the first request into a testable project brief and an orchestration record. Use once, on a fresh copy of the kit, before any work is delegated. |
Run these in order. Do not skip step 1: every later step routes work through lanes that are not yet bound to real models, and an unbound kit runs every "cheap" specialist on the lead's model.
1. Bind the models (always first)
Follow the model-routing skill. Ask which models fill the lead, strong, mid, and fast lanes, confirm the IDs against Cursor's model picker, then write them into docs/MODEL_ROUTING.md and the model: line of every .cursor/agents/*.md. Run its verification checks, including the live scout dispatch, before continuing.
If nobody is here to answer — a Cloud Agent run, a headless invocation — leave the routing unbound, park the question in docs/PROGRESS.md → Waiting on you, and carry on with step 2. Never invent a model ID.
2. Confirm the kit is actually wired
Cheap, mechanical, and it catches an incomplete copy before it wastes a session:
.cursor/agents/lists the roster and.cursor/skills/lists the skills — if a/-command for a skill in that directory does not autocomplete in chat, the copy is incomplete or Cursor has not rescanned..cursor/hooks.jsonexists andnode --versionworks, or the hooks will fail open and you will silently lose the session-context report. Say so rather than leaving it unmentioned.AGENTS.mdand the.cursor/rules/*.mdcfiles are present.
3. Read the control plane and frame the request
Read AGENTS.md and the [PLACEHOLDER] fields in docs/PROJECT_BRIEF.md. Inspect only the files this first request actually needs.
Fill docs/PROJECT_BRIEF.md with the measurable outcome, non-goals, acceptance tests, constraints, and unknowns. If quality here is judged against something concrete — a competitor, a reference implementation, real screenshots — fill docs/REFERENCE_BAR.md too, and set the Reference bar row in the contract; no gauntlet round starts without it. Ask only the questions whose answers materially change scope, risk, or cost — everything else gets a stated assumption, written down. Fill the project contract table at the top of AGENTS.md from the brief so the always-loaded file stops describing a template.
4. Return an orchestration record
The smallest plan, which lane each unit runs on and why, the verification commands, and the stop condition. Do not implement or delegate until the task contract is unambiguous enough to test.
Return
Routing (the four lanes, or "unbound + parked") · Wiring check (agents, skills, hooks, rules — each present or missing) · Brief (path, and which placeholders are still open) · Reference bar (filled, or n/a with the reason) · Orchestration record · Next action.