Socratic Architect - 苏格拉底式架构师

Guide software design analysis through five hierarchical questioning layers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/TeamFlint-Dev/vibe-coding-cn --skill socratic-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Socratic Architect - 苏格拉底式架构师
Source: https://github.com/TeamFlint-Dev/vibe-coding-cn/tree/main/workUnits/verseLogicLab/skills/socratic-architect
Command: npx skills add https://github.com/TeamFlint-Dev/vibe-coding-cn --skill socratic-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users avoid flawed designs and hidden problems by systematically questioning requirements, assumptions, and proposed solutions, ensuring a more robust and well-thought-out approach before implementation.

Core Features & Use Cases

  • Requirement Clarification: Challenges the necessity and true purpose of features.
  • Assumption Validation: Identifies and tests underlying beliefs about the problem or solution.
  • Alternative Exploration: Prompts for simpler or more effective approaches.
  • Use Case: Before coding a new game mechanic, use this Skill to deeply question its purpose, explore if simpler mechanics suffice, and identify potential edge cases or conflicts with existing systems.

Quick Start

Engage the Socratic Architect to question the core purpose of implementing a new caching mechanism.

Frequently Asked Questions about Socratic Architect - 苏格拉底式架构师

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

FAQPage Schema
How do I validate assumptions and clarify requirements before software implementation?

Requirements clarification validates the necessity and true purpose of features by posing probing questions across five hierarchical layers: Essence, Assumptions, Simplicity, Consistency, and Boundaries. This prevents design flaws and technical debt.

What is the Socratic method for architecture review and critical thinking?

The Socratic method for architecture review is a deep-thinking process that guides you to critically analyze requirements, challenge implicit assumptions, and ensure architectural alignment. It systematically uncovers hidden problems before development begins.

How do I identify edge cases and explore simpler design alternatives?

You identify edge cases and explore simpler alternatives by applying design questioning across defined boundaries. This process prompts for more effective approaches and tests underlying beliefs about the proposed solution.

When do I need to challenge implicit assumptions in software design?

You need to challenge implicit assumptions when proposing new solutions or mechanics. Deep questioning tests underlying beliefs about the problem, ensuring a robust approach and preventing flawed designs before coding starts.

Does this requirements analysis approach work for evaluating new game mechanics?

Yes, requirements analysis works for evaluating new game mechanics by deeply questioning the mechanic's purpose, exploring if simpler mechanics suffice, and identifying potential conflicts with existing systems.

What's the best way to prevent technical debt during software architecture design?

The best way to prevent technical debt is systematically questioning requirements and proposed solutions across essence, assumptions, simplicity, consistency, and boundaries. This ensures a well-thought-out approach before implementation.