From lexic
Load context from Lexic's knowledge base for a feature or topic before starting work
How this command is triggered — by the user, by Claude, or both
Slash command
/lexic:context feature name or topicThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Load Context Assemble everything Lexic knows about a topic before you start working on it. ## Steps 1. Call `dev_get_feature_context` with feature set to `$ARGUMENTS`. 2. Call `knowledge_get_context` with topic set to `$ARGUMENTS` and depth set to `comprehensive`. 3. Synthesize the results into a briefing: - **Decisions made**: List architectural and technical decisions with their rationale. Flag any that have `revisit_if` conditions that may now be relevant. - **Key knowledge**: Summarize the most important findings, patterns, and gotchas. - **Recent learnings**: Highlight in...
Assemble everything Lexic knows about a topic before you start working on it.
dev_get_feature_context with feature set to $ARGUMENTS.knowledge_get_context with topic set to $ARGUMENTS and depth set to comprehensive.revisit_if conditions that may now be relevant.npx claudepluginhub lexic-io/lexic.io-plugin --plugin lexic/contextSearches project and global memories by keyword with smart expansion to related terms (e.g., auth→JWT/OAuth, db→Prisma/PostgreSQL), displaying matching key-value entries.
/contextGathers pre-implementation context from GitHub issues, prior review findings, and bug patterns before code changes, producing a structured briefing.
/contextDisplays full project context including tasks with status/priority/blockers, learnings/insights, and decisions/reasoning. Outputs JSON (default) or YAML via --format.
/contextActivates a project phase context from the contexts/ directory and aligns agents, commands, priorities, and escalation rules to that phase.
/contextSurfaces rules, decisions, specs, and patterns for a specific file, directory, topic, or recent git changes, providing contextual knowledge of the codebase.