Does it support specific tech stacks?

Yes, it allows you to define and justify specific technologies like Next.js, PostgreSQL, or Supabase based on your project's unique requirements.

Does it write the actual application code?

No, this skill creates the structural blueprint and documentation required so that you or Claude can write the code more effectively and with fewer errors later.

Can it generate visual diagrams?

It creates high-level system architecture diagrams using ASCII format directly within your ARCHITECTURE.md file for easy version control and readability.

What input does the Architecture skill require?

It primarily reads from docs/PRD.md. If this file doesn't exist, the skill will prompt you to provide requirements or suggest using a product-design skill first.

How does it prevent over-engineering?

The skill includes a dedicated section for 'What NOT to Over-Engineer,' specifically calling out areas to keep simple for the MVP to prevent scope creep.

Technical Architecture Architect

Name: Technical Architecture Architect
Author: Porkbutts

byPorkbutts

•

Productivity & Workflow

Transforms product requirement documents into implementation-ready technical architecture specifications with clear system design and tech stack rationales.

About

The Architecture skill bridges the gap between product vision and implementation by analyzing a PRD and generating a comprehensive technical design. It systematically identifies technical gaps, confirms infrastructure decisions with the user, and produces a structured ARCHITECTURE.md file complete with ASCII diagrams, tech stack justifications, and directory layouts. This ensures developers have a clear, buildable roadmap that avoids over-engineering while maintaining focus on MVP delivery and future scalability.

Key Features

ASCII-based high-level system component diagrams
Structured tech stack decision tracking and rationale
1 GitHub stars
Automated PRD-to-Architecture transformation workflow
Interactive technical gap analysis and clarification
Pre-defined directory structure mapping for new projects

Use Cases

Establishing technical constraints and stack choices for a new MVP
Translating high-level product requirements into a buildable developer roadmap
Documenting system design and data flow for team alignment before coding begins

About

Key Features

ASCII-based high-level system component diagrams
Structured tech stack decision tracking and rationale
1 GitHub stars
Automated PRD-to-Architecture transformation workflow
Interactive technical gap analysis and clarification
Pre-defined directory structure mapping for new projects

Use Cases

Establishing technical constraints and stack choices for a new MVP
Translating high-level product requirements into a buildable developer roadmap
Documenting system design and data flow for team alignment before coding begins