← ClaudeAtlas

advise-project-approachlisted

Research and advise on the best way to approach a software project, including architecture, tech stack, implementation strategy, benchmark research, and comparisons with similar real-world projects. Use before building, mid-build, or after completion when the user asks for project strategy, optimal approach, research comparables, similar projects, stack selection, repo analysis, architecture critique, implementation feedback, or a prioritized improvement plan. Avoid for narrow single-bug debugging or isolated file edits unless the user asks for broader project direction.
AaravKashyap12/advise-project-approach · ★ 30 · Code & Development · score 82
Install: claude install-skill AaravKashyap12/advise-project-approach
# Advise Project Approach Help the user decide, validate, or improve how a project should be built. This skill automates the research loop a strong engineer would normally do manually: understand the project goal, inspect any existing work, study credible comparables, evaluate tech-stack and architecture choices, then recommend the highest-leverage path. ## Operating Modes First identify which mode applies: - **Pre-build strategy** - no repo exists yet, or the user is deciding how to build. Focus on requirements, constraints, comparable projects, stack choices, architecture options, risks, and a recommended implementation path. - **Mid-build course correction** - a repo or partial implementation exists. Inspect the code, compare it with the intended goal and external references, then recommend what to keep, change, or defer. - **Post-build review** - the project is mostly complete. Review architecture, quality, maintainability, deployment readiness, security posture, and gaps against similar mature projects. Mode selection rule: - No repo, folder, code, or URL means default to **pre-build strategy**. - Any repo, folder, code excerpt, GitHub URL, or "I am building..." language means default to **mid-build course correction** unless the user says the project is finished, deployed, or ready for final review. - Finished, deployed, production, launch-ready, or "review this completed project" language means default to **post-build review**. If a mid-build or post-build reque