Vikokoro Current Spec
Read docs/CURRENT_SPEC.md first, then execute work without drifting from it.
Workflow
- •Read
docs/CURRENT_SPEC.mdbefore making plans, code changes, or recommendations. - •Extract constraints relevant to the request (keyboard behavior, mode rules, persistence, themes, search/palette behavior).
- •Implement changes that preserve existing behavior unless the user explicitly requests a spec change.
- •If the request conflicts with
docs/CURRENT_SPEC.md, ask which should be the new source of truth before implementing. - •When behavior changes, update
docs/CURRENT_SPEC.mdin the same change set.
Guardrails
- •Do not change key bindings silently. Reflect shortcut changes in help text and docs.
- •Keep tree-edit invariants: root deletion protection, subtree-preserving reparent behavior, and undo/redo consistency.
- •Treat
docs/CURRENT_SPEC.mdas canonical for current behavior anddocs/milestones/*.mdas historical context.
Output Checklist
Before finishing a task:
- •Verify implementation matches the current spec or explicitly records a spec change.
- •Verify user-facing docs are updated when shortcuts/themes/behavior changed.
- •Verify build/type-check still pass when code was changed.