From ctx
Records coding conventions in CONVENTIONS.md to standardize repeated patterns like naming, formatting, or structure after 2-3 uses.
npx claudepluginhub activememory/ctx --plugin ctxThis skill is limited to using the following tools:
Record a coding convention in CONVENTIONS.md.
Guides creation of .claude/rules/ files for path-scoped project conventions using TDD workflow: RED (test gaps), GREEN (write rule), REFACTOR (optimize). Triggers on 'add rule', 'create convention', 'scope guideline'.
Guides authoring rule files in .claude/rules/ for project conventions including formatting, testing, commits, architecture, and referencing from CLAUDE.md.
Guides effective maintenance of CLAUDE.md files: adding lessons learned, updating conventions, restructuring instructions. Covers when to update/remove rules, structure templates, hierarchy, and size limits.
Share bugs, ideas, or general feedback.
Record a coding convention in CONVENTIONS.md.
/ctx-add-decision)/ctx-add-learning)Conventions are simpler than decisions or learnings. You need:
If the user provides only a description, infer the section from the topic. Check existing sections in CONVENTIONS.md first to place it correctly: don't create a new section if an existing one fits.
If the convention overlaps with an existing one, mention it: "There's already a naming convention for functions. Want me to add this alongside it or update the existing one?"
ctx add convention "Use kebab-case for all CLI flag names" --section "Naming"
ctx add convention "Use cmd.Printf/cmd.Println for CLI output, never fmt.Printf/fmt.Println" --section "Output"
ctx add convention "Colocate test files with implementation (*_test.go next to *.go)" --section "Testing"
If no --section is provided, the convention is appended to the end
of the file. Prefer specifying a section for organization.
Before recording, verify:
Confirm the convention was added.