architecture-planner

Creates architectural designs with component diagrams, data flows, and API contracts for engineering teams.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/psdjungpulzze/smartstudy --skill architecture-planner-psdjungpulzze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-planner
Source: https://github.com/psdjungpulzze/smartstudy/tree/main/.claude/skills/setup/architecture-planner
Command: npx skills add https://github.com/psdjungpulzze/smartstudy --skill architecture-planner-psdjungpulzze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture planning and documentation are often ad-hoc, leading to inconsistent decisions and brittle systems. This skill provides a structured approach to defining goals, constraints, and architectural decisions to ensure cohesive design across teams.

Core Features & Use Cases

  • Architecture style selection with rationale to align technology choices with business goals.
  • Component design, data flow, API contracts, and infrastructure planning guidance.
  • Comprehensive documentation templates for scalable, maintainable systems and effective onboarding.

Quick Start

Begin by outlining the system goals, constraints, and high-level components to initiate architecture planning.

Frequently Asked Questions about architecture-planner

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

FAQPage Schema
How do I plan system architecture for a new software project?

Select an architecture style by aligning technology choices with business goals and documenting the rationale. This ensures architectural decisions are consistent, robust, and scalable rather than ad-hoc, preventing brittle systems during major feature planning.

What is the best way to document API contracts and data flows?

Document API contracts and data flows using comprehensive templates for scalable, maintainable systems. This provides clear component diagrams and infrastructure planning guidance to ensure effective team onboarding and cohesive design.

Can I use this for infrastructure and scalability planning during feature design?

Yes, you can use this during project initiation and major feature planning to guide technology choices, scalability, and integration points. It satisfies requirements for infrastructure planning, data architecture, and component design.

Why does ad-hoc architecture planning lead to brittle systems?

Ad-hoc architecture planning leads to brittle systems because it results in inconsistent decisions and lacks a structured approach. Without clear component diagrams and data architecture, teams fail to ensure cohesive design across integrations.