markmdev/meridian

markmdev/meridian

Agent

Reviews architecture — either existing code or proposed plans. Use during planning to validate approach, or after changes to check structural health.

markmdev/meridian

Agent

Finds dead code, pattern drift, over-engineering, and refactoring opportunities. Use after completing large tasks, at the end of feature work, or when code has gone through many iterations.

markmdev/meridian

Agent

Deep code review that finds real bugs — logic errors, data flow issues, pattern inconsistencies. Returns structured findings to the calling agent.

markmdev/meridian

Agent

Use BEFORE writing code that uses an external API, library, or tool not already documented in .meridian/api-docs/. Researches via web scraping and builds comprehensive knowledge docs with current versions, API operations, limits, and gotchas.

markmdev/meridian

Agent

Use for broad codebase research when you don't know where to look, need to understand "how does X work?", or want comprehensive findings across many files. Returns file paths, line numbers, code snippets, and negative results. Read-only — cannot modify files.

markmdev/meridian

Agent

Use when you have a detailed, unambiguous implementation spec (e.g., "add export for function X in file Y"). Executes the spec, runs typecheck/tests, reports results. Spawn multiple in parallel for independent tasks. Does NOT ask questions — reports ambiguity and stops.

markmdev/meridian

Agent

Documents planned work in Pebble before implementation. Creates appropriate structure (epic, task, or bug fix) based on scope.

markmdev/meridian

Agent

Validate a plan before implementation. Use before exiting Plan mode. Pass the plan file path and any additional context files. Returns JSON with findings and score (must reach 9+ to proceed).