senior_dev_guide

Analyze codebases and project state files to provide actionable senior developer guidance.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/mgsystemsdev/POD --skill senior-dev-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior_dev_guide
Source: https://github.com/mgsystemsdev/POD/tree/main/agent-system-base/.claude/skills/senior_dev_guide
Command: npx skills add https://github.com/mgsystemsdev/POD --skill senior-dev-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides real, direct guidance from a senior developer who reads your codebase, understands the context, and helps you choose the best course—pushing back when needed and confirming when you're on the right track.

Core Features & Use Cases

  • Direct, opinionated analysis of the codebase and project state, not just a status update.
  • Anchors recommendations in real artifacts (code structure, routes/pages, memory and task state) and explains the rationale.
  • Proposes concrete next steps, highlights risks, and explains why a given path is preferable.
  • Works even when no explicit plan exists by reading the codebase and outlining a practical path forward.

Quick Start

Tell me what you’re about to work on and share the context, and I’ll respond with a direct, senior-dev verdict.

Frequently Asked Questions about senior_dev_guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get senior developer code analysis and decision support for my codebase?

Codebase analysis with senior developer decision support reads your project files, routes, and state documents to deliver direct, opinionated guidance and concrete next steps with clear rationale.

What's the best way to validate my project architecture before starting new development work?

Validating project architecture before development requires reading code structure, routes, and project state files like tasks.json and blueprint docs to anchor actionable recommendations and highlight risks.

Can I get concrete next steps for my codebase if I don't have an explicit project plan?

Codebases without explicit project plans can still be analyzed by reading existing code structure and outlining a practical, reasoned path forward based on the actual project state.

Why does senior dev mentorship push back on my codebase review decisions?

Senior dev mentorship pushes back during codebase reviews to provide honest, opinionated guidance that confirms correct paths and redirects suboptimal choices with clear justification.

Does code analysis guidance work with memory and decisions project state files?

Code analysis guidance works directly with memory and decisions project state files, reading these artifacts alongside codebase structure to anchor recommendations in real project context.

When should I not use automated codebase review instead of a senior developer guide?

Automated codebase review without senior developer guidance falls short when you need direct, opinionated decisions that explain why a specific path is preferable rather than just listing status updates.