pdd-cli 0.0.60__py3-none-any.whl → 0.0.61__py3-none-any.whl

pdd/__init__.py

@@ -1,6 +1,6 @@
 """PDD - Prompt Driven Development"""
 
-__version__ = "0.0.60"
+__version__ = "0.0.61"
 
 # Strength parameter used for LLM extraction across the codebase
 # Used in postprocessing, XML tagging, code generation, and other extraction

pdd/cli.py

@@ -348,14 +348,26 @@ def process_commands(ctx: click.Context, results: List[Optional[Tuple[Any, float
                     invoked_subcommands = ctx.obj.get('invoked_subcommands', []) or []
             except Exception:
                 invoked_subcommands = []
-    results = results or []
+    # Normalize results: Click may pass a single return value (e.g., a 3-tuple)
+    # rather than a list of results. Wrap single 3-tuples so we treat them as
+    # one step in the summary instead of three separate items.
+    if results is None:
+        normalized_results: List[Any] = []
+    elif isinstance(results, list):
+        normalized_results = results
+    elif isinstance(results, tuple) and len(results) == 3:
+        normalized_results = [results]
+    else:
+        # Fallback: wrap any other scalar/iterable as a single result
+        normalized_results = [results]
+
     num_commands = len(invoked_subcommands)
-    num_results = len(results) # Number of results actually received
+    num_results = len(normalized_results)  # Number of results actually received
 
     if not ctx.obj.get("quiet"):
         console.print("\n[info]--- Command Execution Summary ---[/info]")
 
-    for i, result_tuple in enumerate(results):
+    for i, result_tuple in enumerate(normalized_results):
         # Use the retrieved subcommand name (might be "Unknown Command X" in tests)
         command_name = invoked_subcommands[i] if i < num_commands else f"Unknown Command {i+1}"
 
@@ -395,7 +407,7 @@ def process_commands(ctx: click.Context, results: List[Optional[Tuple[Any, float
 
     if not ctx.obj.get("quiet"):
         # Only print total cost if at least one command potentially contributed cost
-        if any(res is not None and isinstance(res, tuple) and len(res) == 3 for res in results):
+        if any(res is not None and isinstance(res, tuple) and len(res) == 3 for res in normalized_results):
             console.print(f"[info]Total Estimated Cost:[/info] ${total_cost:.6f}")
         # Indicate if the chain might have been incomplete due to errors
         if num_results < num_commands and not all(res is None for res in results): # Avoid printing if all failed

pdd/templates/generic/generate_prompt.prompt

@@ -0,0 +1,142 @@
+---
+name: generic/generate_prompt
+description: Generate a module prompt (.prompt) for any stack (backend, frontend, CLI, jobs) using project docs and context
+version: 1.0.0
+tags: [template, prompt, generic]
+language: prompt
+output: prompts/${MODULE}_${LANG_OR_FRAMEWORK}.prompt
+variables:
+  MODULE:
+    required: true
+    type: string
+    description: Module/component basename to generate a prompt for.
+    examples: [orders, auth, users]
+  LANG_OR_FRAMEWORK:
+    required: false
+    type: string
+    description: Target language or framework suffix used in prompt naming (matches your stack conventions).
+    examples: [Python, TypeScriptReact, Go, Java, Ruby]
+    default: Python
+  LAYER:
+    required: false
+    type: string
+    description: System layer or interface type for context.
+    examples: [backend, frontend, api, graphql, cli, job, message, config, module, component, page]
+  README_FILE:
+    required: false
+    type: path
+    description: Project README to provide overall context.
+    example_paths: [README.md, docs/README.md]
+  API_DOC_FILE:
+    required: false
+    type: path
+    description: API documentation describing endpoints and conventions.
+    example_paths: [docs/api-documentation.md, docs/api.md]
+  DB_SCHEMA_FILE:
+    required: false
+    type: path
+    description: Database schema or ERD for backend data models.
+    example_paths: [context/database-schema.md, docs/db/schema.md]
+  BACKEND_FILES_CSV:
+    required: false
+    type: path
+    description: CSV listing backend Python files/modules (for context/reference).
+    example_paths: [prompts/backend/python_architecture.csv]
+  IO_DEPENDENCIES_CSV:
+    required: false
+    type: path
+    description: CSV of function inputs/outputs and dependencies for backend modules.
+    example_paths: [prompts/backend/io_dependencies.csv]
+  ARCHITECTURE_FILE:
+    required: false
+    type: path
+    description: Architecture JSON (from architecture/architecture_json) to drive module scope, dependencies, and interface.
+    example_paths: [architecture.json]
+  TECH_STACK_FILE:
+    required: false
+    type: path
+    description: Tech stack overview (languages, frameworks, infrastructure, tools) for shaping conventions.
+    example_paths: [docs/tech_stack.md, docs/architecture/stack.md]
+  CODE_GENERATOR_PROMPT:
+    required: false
+    type: path
+    description: Reference code generator prompt to mirror style and expectations.
+    example_paths: [prompts/code_generator_python.prompt, prompts/code_generator_main_python.prompt]
+  EXISTING_PROMPTS:
+    required: false
+    type: list
+    description: Existing prompt files to use as reference (comma/newline-separated).
+    example_paths: [prompts/orders_python.prompt, prompts/auth_python.prompt]
+  DEP_EXAMPLE_EXT:
+    required: false
+    type: string
+    description: File extension for dependency examples under context/ (for non-Python stacks).
+    examples: [py, ts, tsx, go, java]
+    default: py
+usage:
+  generate:
+    - name: Minimal (module only)
+      command: pdd generate -e MODULE=orders -e LANG_OR_FRAMEWORK=Python --output 'prompts/${MODULE}_${LANG_OR_FRAMEWORK}.prompt' pdd/templates/generic/generate_prompt.prompt
+    - name: With project docs
+      command: pdd generate -e MODULE=orders -e LANG_OR_FRAMEWORK=Python -e README_FILE=README.md -e API_DOC_FILE=docs/api-documentation.md -e DB_SCHEMA_FILE=context/database-schema.md --output 'prompts/${MODULE}_${LANG_OR_FRAMEWORK}.prompt' pdd/templates/generic/generate_prompt.prompt
+    - name: With CSVs and references (backend/Python)
+      command: pdd generate -e MODULE=orders -e LANG_OR_FRAMEWORK=Python -e README_FILE=README.md -e API_DOC_FILE=docs/api-documentation.md -e DB_SCHEMA_FILE=context/database-schema.md -e BACKEND_FILES_CSV=prompts/backend/python_architecture.csv -e IO_DEPENDENCIES_CSV=prompts/backend/io_dependencies.csv -e CODE_GENERATOR_PROMPT=prompts/code_generator_python.prompt --output 'prompts/${MODULE}_${LANG_OR_FRAMEWORK}.prompt' pdd/templates/generic/generate_prompt.prompt
+    - name: Frontend (TypeScriptReact) variant
+      command: pdd generate -e MODULE=profile_page -e LANG_OR_FRAMEWORK=TypeScriptReact -e LAYER=frontend -e README_FILE=README.md --output 'prompts/${MODULE}_${LANG_OR_FRAMEWORK}.prompt' pdd/templates/generic/generate_prompt.prompt
+    - name: From architecture.json
+      command: pdd generate -e MODULE=orders_api -e LANG_OR_FRAMEWORK=Python -e LAYER=api -e ARCHITECTURE_FILE=architecture.json --output 'prompts/${MODULE}_${LANG_OR_FRAMEWORK}.prompt' pdd/templates/generic/generate_prompt.prompt
+
+discover:
+  enabled: false
+  max_per_pattern: 5
+  max_total: 10
+---
+
+% You are an expert prompt writer and software architect for PDD. Your goal is to write a high-quality prompt that will generate the code for the ${MODULE} module/component. The prompt you create will be used to produce a detailed implementation specification in a file named ${MODULE}_${LANG_OR_FRAMEWORK}.prompt, suitable for the specified stack and layer.
+
+% Project context (optional but recommended):
+<readme><include>${README_FILE}</include></readme>
+<api><include>${API_DOC_FILE}</include></api>
+<database><include>${DB_SCHEMA_FILE}</include></database>
+<backend_files_csv><include>${BACKEND_FILES_CSV}</include></backend_files_csv>
+<io_dependencies_csv><include>${IO_DEPENDENCIES_CSV}</include></io_dependencies_csv>
+<architecture><include>${ARCHITECTURE_FILE}</include></architecture>
+<tech_stack><include>${TECH_STACK_FILE}</include></tech_stack>
+<generate_code_cli_example><include>${CODE_GENERATOR_PROMPT}</include></generate_code_cli_example>
+
+% Existing prompt references (optional):
+<existing_backend_prompts><include-many>${EXISTING_PROMPTS}</include-many></existing_backend_prompts>
+
+% Do the following:
+- Explain concisely what you are going to do (create a prompt for the ${MODULE} module/component for the specified layer and stack).
+- Analyze any difficulties this prompt might encounter for ${MODULE} (e.g., data modeling, API or UI contracts, transactions, idempotency, auth, state management, error handling) and briefly state mitigation strategies tailored to the given LAYER and LANG_OR_FRAMEWORK.
+- If ARCHITECTURE_FILE is provided, identify the item that corresponds to this prompt by matching `filename` to `${MODULE}_${LANG_OR_FRAMEWORK}.prompt` (or best match by basename and layer). Use that item’s `reason`, `description`, `dependencies`, `interface`, and `tags` to shape the sections below.
+- Then create the prompt content for ${MODULE} inside XML tags named prompt, ensuring conventions fit the stack and layer.
+
+% The prompt you generate must follow this structure:
+1) First paragraph: describe the role and responsibility of the ${MODULE} module/component within the system (consider the LAYER if provided).
+2) A "Requirements" section with numbered points covering functionality, contracts, error handling, validation, logging, performance, and security.
+3) A "Dependencies" section using XML include tags for each dependency (see format below).
+4) An "Instructions" section with precise implementation guidance (clarify inputs/outputs, function/class responsibilities, edge cases, and testing notes).
+5) A clear "Deliverable" section describing the expected code artifacts and entry points.
+
+% Dependencies format and conventions:
+- Represent each dependency using an XML tag with the dependency name, and put the file path inside an <include> tag, e.g.:
+  <orders_service>
+    <include>context/orders_service_example.${DEP_EXAMPLE_EXT}</include>
+  </orders_service>
+- Prefer real example files available in the provided context (use <include-many> when listing multiple). If examples are not provided, assume dependency examples live under context/ using the pattern context/[dependency_name]_example.${DEP_EXAMPLE_EXT}.
+- Include all necessary dependencies for the module/component (based on the provided context and references).
+- When using ARCHITECTURE_FILE, its `dependencies` reference other prompt filenames. Convert each dependency prompt filename into a sensible dependency name (strip language suffix and `_prompt`), and map to context files with the `${DEP_EXAMPLE_EXT}` extension if present; otherwise, list the prompt filename explicitly in a "Prompt Dependencies" subsection.
+
+% Architecture awareness (when ARCHITECTURE_FILE provided):
+- Align the "Requirements" and "Instructions" with the selected item’s `interface.type` (e.g., page, component, module, api, graphql, cli, job, message, config).
+- For `api`, outline endpoints (method, path, auth) consistent with the architecture description; for `page`/`component`, describe route/props/data sources; for `job`, include trigger and retry policy; for `config`, list keys and sources.
+
+% Style and quality requirements:
+- The generated prompt must be detailed enough to yield production-ready code.
+- Match the style and patterns of existing *_${LANG_OR_FRAMEWORK}.prompt files when present.
+- Do not invent technologies or files; rely on the included context. If assumptions are necessary, state them explicitly and conservatively.
+
+% Output contract:
+- Return free-form text containing a single <prompt>...</prompt> XML section with the complete prompt content described above. Do not include additional commentary after the <prompt> block.

{pdd_cli-0.0.60.dist-info → pdd_cli-0.0.61.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pdd-cli
-Version: 0.0.60
+Version: 0.0.61
 Summary: PDD (Prompt-Driven Development) Command Line Interface
 Author: Greg Tanaka
 Author-email: glt@alumni.caltech.edu
@@ -53,7 +53,7 @@ Requires-Dist: build; extra == "dev"
 Requires-Dist: twine; extra == "dev"
 Dynamic: license-file
 
-.. image:: https://img.shields.io/badge/pdd--cli-v0.0.60-blue
+.. image:: https://img.shields.io/badge/pdd--cli-v0.0.61-blue
    :alt: PDD-CLI Version
 
 .. image:: https://img.shields.io/badge/Discord-join%20chat-7289DA.svg?logo=discord&logoColor=white&link=https://discord.gg/Yp4RTh8bG7
@@ -130,7 +130,7 @@ After installation, verify:
 
    pdd --version
 
-You'll see the current PDD version (e.g., 0.0.60).
+You'll see the current PDD version (e.g., 0.0.61).
 
 Getting Started with Examples
 -----------------------------

{pdd_cli-0.0.60.dist-info → pdd_cli-0.0.61.dist-info}/RECORD

@@ -1,4 +1,4 @@
-pdd/__init__.py,sha256=DkLNT664TDBz1q2bKJ1z7tY7zRdVTF6dTex1j5DokZU,633
+pdd/__init__.py,sha256=60zr1ZNOzlSl4emQ4nH962OEwIZiUFC4jsFk1CrMMHc,633
 pdd/auto_deps_main.py,sha256=cpP3bbzVL3jomrGinpzTxzIDIC8tmDDYOwUAC1TKRaw,3970
 pdd/auto_include.py,sha256=OJcdcwTwJNqHPHKG9P4m9Ij-PiLex0EbuwJP0uiQi_Y,7484
 pdd/auto_update.py,sha256=w6jzTnMiYRNpwQHQxWNiIAwQ0d6xh1iOB3xgDsabWtc,5236
@@ -6,7 +6,7 @@ pdd/bug_main.py,sha256=EtaGTuucQ7VgqOhyg4o6GFG7_QtTsDPTrRdGJWT648M,4841
 pdd/bug_to_unit_test.py,sha256=BoQqNyKQpBQDW8-JwBH_RX4RHRSiU8Kk3EplFrkECt0,6665
 pdd/change.py,sha256=Hg_x0pa370-e6oDiczaTgFAy3Am9ReCPkqFrvqv4U38,6114
 pdd/change_main.py,sha256=04VHiO_D-jlfeRn6rrVH7ZTA5agXPoJGm1StGI8--XY,27804
-pdd/cli.py,sha256=c5Gco_Ra1ZCZf1MtxrNZdySDhZqICHBQMSH5VBqVPEw,55162
+pdd/cli.py,sha256=phCEbNXjK-3Orjg7N-yhKb5DeXAhX9s1q7sWpqPlDps,55747
 pdd/cmd_test_main.py,sha256=M-i5x26ORXurt_pu8x1sgLAyVIItbuRThiux4wBg3Ls,7768
 pdd/code_generator.py,sha256=AxMRZKGIlLh9xWdn2FA6b3zSoZ-5TIZNIAzqjFboAQs,4718
 pdd/code_generator_main.py,sha256=UtoskalEPpMAvCO-zd6xmr1lbQqSWQ7BvYgNJCybqok,35151
@@ -111,9 +111,10 @@ pdd/prompts/unfinished_prompt_LLM.prompt,sha256=vud_G9PlVv9Ig64uBC-hPEVFRk5lwpc8
 pdd/prompts/update_prompt_LLM.prompt,sha256=prIc8uLp2jqnLTHt6JvWDZGanPZipivhhYeXe0lVaYw,1328
 pdd/prompts/xml_convertor_LLM.prompt,sha256=YGRGXJeg6EhM9690f-SKqQrKqSJjLFD51UrPOlO0Frg,2786
 pdd/templates/architecture/architecture_json.prompt,sha256=uSNSsKTL-cuMMhi5a4GSpC94DKkOFAlXh7R0CUlo-hg,8126
-pdd_cli-0.0.60.dist-info/licenses/LICENSE,sha256=kvTJnnxPVTYlGKSY4ZN1kzdmJ0lxRdNWxgupaB27zsU,1066
-pdd_cli-0.0.60.dist-info/METADATA,sha256=4vSMytmX5LPnADjAlOVkZPCSf--g5FWbATtu9zo7Qqs,12687
-pdd_cli-0.0.60.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
-pdd_cli-0.0.60.dist-info/entry_points.txt,sha256=Kr8HtNVb8uHZtQJNH4DnF8j7WNgWQbb7_Pw5hECSR-I,36
-pdd_cli-0.0.60.dist-info/top_level.txt,sha256=xjnhIACeMcMeDfVNREgQZl4EbTni2T11QkL5r7E-sbE,4
-pdd_cli-0.0.60.dist-info/RECORD,,
+pdd/templates/generic/generate_prompt.prompt,sha256=EIE4vCEauJglLxS8OxuMx1S4JnPexi-yXxEOpIwaRW4,9276
+pdd_cli-0.0.61.dist-info/licenses/LICENSE,sha256=kvTJnnxPVTYlGKSY4ZN1kzdmJ0lxRdNWxgupaB27zsU,1066
+pdd_cli-0.0.61.dist-info/METADATA,sha256=iS6Mds35DEHVnnWEfrKI0tDsInfBj7V49NUFd8UWhdI,12687
+pdd_cli-0.0.61.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+pdd_cli-0.0.61.dist-info/entry_points.txt,sha256=Kr8HtNVb8uHZtQJNH4DnF8j7WNgWQbb7_Pw5hECSR-I,36
+pdd_cli-0.0.61.dist-info/top_level.txt,sha256=xjnhIACeMcMeDfVNREgQZl4EbTni2T11QkL5r7E-sbE,4
+pdd_cli-0.0.61.dist-info/RECORD,,