PlatNexus Interpreter Review

Prompt file imported from houyuwen/PlatNexus (.github/prompts/patterns/platnexus-interpreter-review.prompt.md). Copyright stays with the author.

Use ../../skills/platnexus-pattern-interpreter/SKILL.md as the primary pattern reference. Use ../../pattern-context/pattern_relationship_map.md to cross-check adjacent pattern pairings before finalizing the answer.

Also obey these PlatNexus rule sources:

• ../../copilot-instructions.md
• ../../instructions/platnexus-development.instructions.md
• ../../instructions/platnexus-directory-decoupling.instructions.md
• ../../instructions/platnexus-identifier-naming.instructions.md
• ../../skills/platnexus-pattern-principles/SKILL.md
• ../../pattern-context/pattern_relationship_map.md
• ../../../docs/嵌入式跨平台架构设计.md
• ../../../docs/架构设计目录树.md

Response style (统一输出风格)

• Keep output concise, engineering-focused, and layer-aware.
• Use these sections in order:
  1. Pattern decision
  2. Why this pattern here
  3. Design-principles matrix (SRP/OCP/LSP/ISP/DIP/LoD)
  4. Graph-informed pattern collaboration notes
  5. Files/layers to touch
  6. Minimal implementation/review/refactor steps

Mission

Review the provided code, API, or design as a Interpreter implementation.

Focus

• Judge whether the current structure really matches Interpreter
• Check whether the intended layer belongs to: services, platform/net
• Flag combo opportunities or misuse around: protocol-pipeline
• Run a quick SRP/OCP/LSP/ISP/DIP/LoD sanity check before issuing verdicts.
• Graph link: may use flyweight for shared terminal symbols and visitor for extra semantic operations.

Expected output

• Findings by severity
• Design-principles matrix (SRP/OCP/LSP/ISP/DIP/LoD)
• Graph-informed neighbor-pattern notes (upgrade/downgrade paths)
• Boundary and layering risks
• Pattern fit verdict
• Smallest credible repair direction