Dominicduan Design Skill

The 6-Step Fully Automated Workflow

CRITICAL RULE 1: TREE-STRUCTURED DOCUMENTATION MATRIX Every file and folder for this project MUST reside inside a single top-level master folder named after the user's defined theme. From Step 2 onwards, you MUST loop over each branch deduced in Step 1, executing deep reasoning and generating specific outputs documents INSIDE each respective [ThemeName]/schemes/branch_{X}/ folder. This creates a massive, divergent matrix of research files inside the master theme envelope. Ensure absolutely no empty folders remain at the end of the project. Do not pause execution unless requiring human fallback.

CRITICAL RULE 2: MANDATORY LANGUAGE PROTOCOL All final markdown outputs, deductions, and technical documentation MUST be generated exclusively in Chinese. However, all proper nouns, specialized academic/philosophical concepts, and technical terminologies MUST be annotated with their original English terms in parentheses (e.g., 后人类主义 (Posthumanism), 无器官身体 (Body without Organs)).

Step 1: The Dual-State Brainstorming Matrix (双态头脑风暴大矩阵)

• State A (Free Divergence): Conduct a completely free, unconstrained brainstorm based purely on the raw abstract theme. Deduce exactly 5 independent "Free-State" scheme branches.
• Academic Grounding: Pause divergence. First, check if a root _research_pdfs/ or [ThemeName]/_research_pdfs/ contains user-provided PDFs/book lists to ingest them. Crucially, even if user-provided references are present, you MUST still use browser_subagent to actively hunt and download massive amounts of additional foundational literature and new academic papers to [ThemeName]/_research_pdfs/. Read these dense PDF texts thoroughly to grasp strict academic limits. Do NOT attempt to extract images from PDFs.
• State B (Constrained Divergence): Conduct a second, completely independent brainstorm strictly bound by the academic limits you just digested. Deduce exactly 5 separate "Constrained-State" scheme branches.
• Consolidation: Do NOT overwrite State A. Treat the Free-State and Constrained-State branches as parallel universes. Organize and combine them, merging only obviously overlapping concepts. You will proceed with up to 10 distinct, parallel scheme branches encompassing both pure freedom and rigorous constraint.
• Structure: Execute python scripts/build_project_tree.py "[ThemeName]" "[Free_Branch1]" "[Constrained_Branch1]" ... substituting the sanitized theme name and all your consolidated dual-state branch names. This scaffolds the massive [ThemeName]/schemes/branch_X/ architecture.
• Document: Output 01_dual_state_brainstorming.md at the [ThemeName]/ root directory.

Step 2: Branch-Specific Multimodal Analysis (分支特定沉浸解析)

• Branch-Specific Reading: Now that the tree is structurally built, loop over EVERY final branch. Use view_file to extensively re-read the global PDF texts precisely through the theoretical lens of that specific branch.
• Document: Output 02_branch_literature_analysis.md INSIDE each respective branch's folder (e.g., [ThemeName]/schemes/branch_1_A/02_branch_literature_analysis.md).

Step 3: Branch-Specific Deep Philosophical Deduction & System Architecture

• Deep Thinking: Provide extensive <thinking> reasoning for each branch independently.
• Deduction: Establish the rigorous Philosophical Deduction, Research Methodology, and Research Purpose specifically tailored to the divergent bounds of each branch.
• Document: Output 03_philosophical_deduction_and_methodology.md INSIDE each [ThemeName]/schemes/branch_... folder.

Step 4: Branch-Specific Visual Research & Artist Critique

• Action: For each branch, investigate existing related art projects.
• Multimodal Critique: Download shared inspiration to [ThemeName]/_inspiration_images/. Critique them (view_file) based on the specific branch's philosophical angle.
• Visual Translation: Deduce a unique Visual Translation Language (视觉转化语言) for each branch individually.
• Document: Output 04_artist_case_studies_and_visual_language.md INSIDE each branch's folder.

Step 5: Branch-Specific Translation Boundaries & Technical Implementation

• Action: Synthesize the visual/textual understanding for each branch. NO AIGC allowed.
• Technical Mapping: Translate each branch into exact, actionable technical architectures, systemic rulesets, and physical/3D logic separately.
• Iteration Paths: Provide detailed iterative implementation loops specific to each branch's logic.
• Document: Output 05_technical_implementation_paths.md INSIDE each branch's folder.

Step 6: Master Reorganization & Root Finalization

• Action: Look backward across the fully populated tree matrix ([ThemeName]/schemes/).
• Organization: Ensure NO empty folders were created. If any directory lacks documents, populate them.
• Synthesis: Compare the branches and synthesize everything into a singular master narrative describing the holistic divergent logic of the project.
• Document: Output 06_master_process_reorganization.md at the [ThemeName]/ root directory.

Red Flags & Common Rationalizations (Avoid These)

• 🚩 "I should stop after Step X and ask the user to review." -> NO. Execute all 6 steps automatically.
• 🚩 "The user provided some PDFs, so I don't need to search" -> NO. You MUST execute massively extended research and download new papers into [ThemeName]/_research_pdfs/ regardless of provided files.
• 🚩 "I am stuck downloading the PDF." -> SOLUTION: Attempt browser bypass; if fully blocked, list PDFs and politely halt for the human user to provide them to [ThemeName]/_research_pdfs/.
• 🚩 "I can just generate an AI image for Step 5." -> NO. AIGC is totally forbidden. Use hardcore textual technical translation.