Cod-e-Codes

Implements marchat terminal client TUI, commands, keystore, and WebSocket client behavior. Use when editing client/, Bubble Tea models, :commands, themes, notifications, or client configuration paths.

Implements marchat server hub, WebSocket handlers, admin web, health, and startup validation. Use when editing server/, cmd/server/, hub routing, admin panel, or server configuration.

Writes and runs marchat tests with race detection, coverage, and dialect smoke patterns. Use when adding tests, fixing test failures, measuring coverage, or when the user mentions go test, -race, TESTING.md, or CI database smoke.

Changes marchat SQL schema and queries across SQLite, PostgreSQL, and MySQL using dialect helpers. Use when editing server/db.go, db_dialect.go, schema migrations, MARCHAT_DB_PATH, or multi-database behavior.

Implements and refactors marchat Go code with project toolchain and quality gates. Use when adding features, fixing bugs, touching client/server/plugin code, or when the user asks to develop, build, or validate marchat changes.

Develops and maintains marchat plugins: SDK, host IPC, manager install path, store downloads, and Ed25519 licenses. Use when editing plugin/, plugin commands, or plugin_state.json behavior.

Updates marchat documentation and changelogs to match code and release practice. Use when editing CHANGELOG.md, README.md, ARCHITECTURE.md, PROTOCOL.md, TESTING.md, or other project markdown.

Drafts conventional commit messages and pull request bodies for marchat without committing or pushing unless explicitly requested. Use when the user asks for a commit message, PR description, or git workflow help; also read at the end of every substantive implementation task.

Implements or debugs astvcs structural diff, merge, edit intents, and graph mutations. Use when editing src/diff, src/merge, src/intent, src/graph, or unparser.rs, or when the user mentions alignment, LCS, EditPayload, merge conflicts, edit intents, or three-way merge.

Builds, tests, and validates the astvcs Rust CLI. Use when changing astvcs source, fixing CI, running cargo test or clippy, or when the user asks about project layout, build requirements, or release binaries.

Writes or extends astvcs integration tests and CLI fixtures. Use when editing tests/integration.rs, examples/, or when the user asks for end-to-end tests, fixture walkthroughs, merge scenarios, or CLI regression coverage.

Keeps astvcs CLI and diff viewer output focused, actionable, accessible, and compatible. Use when changing command output, errors, conflict reports, --details, -v, --json, or src/diff/view.

Adds or extends tree-sitter language support in astvcs. Use when adding a file extension, wiring a tree-sitter grammar, editing src/frontend, or when the user mentions a new language, parser, or AST translation for a source file type.

Write new Ion programs and .ion source files using only verified language features from ION_SPEC.md, examples/, tests/, and stdlib/. Guides ownership, no-escape borrows, channels, and stdlib imports. Use when the user asks to write Ion code, create an Ion program, script, example, or application, or implement logic in .ion files. Do not invent syntax or APIs from Rust, C, Go, or other languages.

Systematically find and reproduce bugs in the ion-lang compiler, runtime, and tests. Use when debugging failures, hunting regressions, investigating wrong codegen, type-check mistakes, test_runner failures, clippy warnings, or when the user asks to find bugs, triage issues, or review changes for defects. Also use before filing GitHub issues or after a feature change breaks tests.

Author new Cursor Agent Skills for the ion-lang repository. Use when creating or editing skills in .cursor/skills/, writing SKILL.md frontmatter, adding references/ or scripts/, or asking how to structure project skills for Ion. Do not use for personal skills in ~/.cursor/skills/.

Find and summarize academic programming language research (PhD theses, POPL, PLDI, ICFP, OOPSLA papers) relevant to Ion design and implementation. Use when the user asks for PL research, papers on ownership, borrow checking, linear types, channels, Send traits, transpilation, or evidence for language or compiler decisions in ion-lang.