engineering-context

Plugin engineering-context in fernandoxavier02/engineering-context. Commands read from the repo's manifest — 1 month ago.

Skills (6)

• detect-stack

  This skill should be used when the user asks to 'detect project stack', 'identify tech stack', 'what language is this project', 'analyze project technology', or 'what framework does this use'. Auto-detects language, framework, test framework, build tools, and architecture style from project files.

• generate-rules

  This skill should be used when the user asks to 'generate engineering rules', 'create architecture contract', 'write engineering principles', 'set up testing strategy', or 'create anti-pattern rules'. Generates 4 mandatory always-loaded engineering rules and vault cards adapted to the project's stac

• map-architecture

  This skill should be used when the user asks to 'map architecture', 'identify layers', 'map dependencies', 'architecture mapping', 'dependency rules', or 'understand project structure'. Maps architecture layers, dependencies, and boundary rules from directory structure.

• mine-anti-patterns

  This skill should be used when the user asks to 'scan for anti-patterns', 'find code smells', 'detect anti-patterns', 'mine anti-patterns', or 'check for common errors'. Scans the codebase for anti-patterns and generates a catalog of real issues found.

• setup

  This skill should be used when the user asks to 'set up engineering context', 'create engineering rules', 'configure engineering best practices', 'generate architecture contract', 'initialize context system', or 'set up engineering for this project'. Orchestrates the full 5-phase pipeline to create

• validate-context

  This skill should be used when the user asks to 'validate context', 'check engineering rules', 'verify context system', 'test context setup', or 'run context validation'. Generates and runs validation tests for the engineering context system.

Slash commands (6)

• /engineering-context:detect-stack

  Auto-detect language, framework, test framework, build tools and architecture style of the current project.

• /engineering-context:generate-rules

  Generate the 4 mandatory always-loaded rules (.claude/rules/50–53) plus vault cards, adapted to the project.

• /engineering-context:map-architecture

  Map project architecture — identify layers, dependency rules, mandatory flows. Requires detect-stack first (or runs it).

• /engineering-context:mine-anti-patterns

  Scan the codebase for anti-patterns (duplicated constants, silenced exceptions, venue leaks, etc.) and produce a catalog.

• /engineering-context:setup

  Run the full 5-phase engineering context setup pipeline (detect stack → map architecture → mine anti-patterns → generate rules → validate).

• /engineering-context:validate-context

  Generate and run validation tests for the engineering context system (rules exist, frontmatter correct, vault cards present).

Similar plugins