Name: build_and_publish_yaac
Author: withyaac

Prompt file imported from withyaac/yaac (.cursor/commands/build_and_publish_yaac.md). Copyright stays with the author.

Build and Publish yaac Package

Instruction

You are helping to build and publish the yaac package to PyPI. Follow the steps in yaac/publish/PUBLISHING.md step-by-step. Do not skip steps or proceed if you encounter errors.

Key Principles

Reference the documentation: The full publishing guide is in yaac/publish/PUBLISHING.md. Read it first and follow it. Do not duplicate information from that doc here.
Go step-by-step: Complete each step fully before moving to the next. Verify each step succeeded before proceeding.
Stop on errors: If you encounter any error, warning, or unexpected output:
- STOP immediately
- Report the error clearly to the user
- Ask the user how they want to proceed
- Do NOT attempt to fix errors without user approval (unless it's a trivial issue you're certain about)
Verify at each stage: After each major step (build, upload, install), verify it worked correctly before continuing.

Workflow

1. Pre-flight Checks

Before starting:

Read yaac/publish/PUBLISHING.md to understand the full process
Check current version in pyproject.toml and yaac/__init__.py (they should match)
Verify you're in the correct directory (/home/phil/code/yaac)
Check if build tools are available (uv or python -m build)

2. Building the Package

Follow the "Building the Package" section in PUBLISHING.md:

Clean previous builds
Build using uv build (recommended) or python -m build
Verify the build created both .tar.gz and .whl files in dist/
If build fails: Stop and ask the user. Check the troubleshooting section in PUBLISHING.md.

3. Testing on TestPyPI (Optional)

If the user wants to test on TestPyPI:

Follow the "Testing on TestPyPI" section in PUBLISHING.md
Upload to TestPyPI
Create a fresh test environment and install from TestPyPI
Verify the installation works
If upload fails with "400 Bad Request": Check if version already exists. Stop and ask user if they want to use a post/dev suffix or skip TestPyPI.

4. Publishing to Production PyPI

Follow the "Publishing to Production PyPI" section in PUBLISHING.md:

Upload to production PyPI
Verify the publication (check package page, test installation)
If upload fails: Stop and ask the user. Check the troubleshooting section.

Error Handling

When you encounter an error:

Stop immediately - do not proceed
Read the error message carefully - check if it's covered in PUBLISHING.md troubleshooting
Report to user - explain what happened and what step failed
Suggest solutions - reference PUBLISHING.md troubleshooting or ask user for guidance
Wait for user approval - do not attempt fixes without user confirmation

Updating Documentation

Only update yaac/publish/PUBLISHING.md or this command file if:

You discover a critical issue that would affect future runs
You find a better approach that significantly improves the process
The documentation is missing essential information that caused a failure

Do NOT update documentation for:

One-off issues specific to the current run
Minor clarifications that don't affect the process
Personal preferences or style changes

If you do update documentation, explain clearly what changed and why.

User Communication

Be clear about what you're doing: State which step you're on
Report progress: Confirm when steps complete successfully
Ask before proceeding: If a step requires user input (like confirming upload), ask first
Summarize at the end: After successful publication, summarize what was done

Example Flow

1. "Reading PUBLISHING.md to understand the process..."
2. "Checking current version in pyproject.toml and __init__.py..."
3. "Cleaning previous builds..."
4. "Building package with uv build..."
5. "Build successful! Created dist/yaac-X.X.X.tar.gz and dist/yaac-X.X.X-py3-none-any.whl"
6. "Would you like to test on TestPyPI first, or proceed directly to production PyPI?"
7. [After user choice, proceed with upload and verification]
8. "Publication complete! Package is available at https://pypi.org/project/yaac/"

Install build_and_publish_yaac and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Build and Publish yaac Package ## Instruction You are helping to build and publish the `yaac` package to PyPI. **Follow the steps in `yaac/publish/PUBLISHING.md` step-by-step**. Do not skip steps or proceed if you encounter errors. ## Key Principles 1. **Reference the documentation**: The full publishing guide is in `yaac/publish/PUBLISHING.md`. Read it first and follow it. Do not duplicate information from that doc here. 2. **Go step-by-step**: Complete each step fully before moving to the next. Verify each step succeeded before proceeding. 3. **Stop on errors**: If you encounter any error, warning, or unexpected output: - **STOP immediately** - Report the error clearly to the user - Ask the user how they want to proceed - Do NOT attempt to fix errors without user approval (unless it's a trivial issue you're certain about) 4. **Verify at each stage**: After each major step (build, upload, install), verify it worked correctly before continuing. ## Workflow ### 1. Pre-flight Checks Before starting: - Read `yaac/publish/PUBLISHING.md` to understand the full process - Check current version in `pyproject.toml` and `yaac/__init__.py` (they should match) - Verify you're in the correct directory (`/home/phil/code/yaac`) - Check if build tools are available (`uv` or `python -m build`) ### 2. Building the Package Follow the "Building the Package" section in PUBLISHING.md: - Clean previous builds - Build using `uv build` (recommended) or `python -m build` - Verify the build created both `.tar.gz` and `.whl` files in `dist/` - **If build fails**: Stop and ask the user. Check the troubleshooting section in PUBLISHING.md. ### 3. Testing on TestPyPI (Optional) If the user wants to test on TestPyPI: - Follow the "Testing on TestPyPI" section in PUBLISHING.md - Upload to TestPyPI - Create a fresh test environment and install from TestPyPI - Verify the installation works - **If upload fails with "400 Bad Request"**: Check if version already exists. Stop and ask user if they want to use a post/dev suffix or skip TestPyPI. ### 4. Publishing to Production PyPI Follow the "Publishing to Production PyPI" section in PUBLISHING.md: - Upload to production PyPI - Verify the publication (check package page, test installation) - **If upload fails**: Stop and ask the user. Check the troubleshooting section. ## Error Handling When you encounter an error: 1. **Stop immediately** - do not proceed 2. **Read the error message carefully** - check if it's covered in PUBLISHING.md troubleshooting 3. **Report to user** - explain what happened and what step failed 4. **Suggest solutions** - reference PUBLISHING.md troubleshooting or ask user for guidance 5. **Wait for user approval** - do not attempt fixes without user confirmation ## Updating Documentation Only update `yaac/publish/PUBLISHING.md` or this command file if: - You discover a **critical issue** that would affect future runs - You find a **better approach** that significantly improves the process - The documentation is **missing essential information** that caused a failure Do NOT update documentation for: - One-off issues specific to the current run - Minor clarifications that don't affect the process - Personal preferences or style changes If you do update documentation, explain clearly what changed and why. ## User Communication - **Be clear about what you're doing**: State which step you're on - **Report progress**: Confirm when steps complete successfully - **Ask before proceeding**: If a step requires user input (like confirming upload), ask first - **Summarize at the end**: After successful publication, summarize what was done ## Example Flow ``` 1. "Reading PUBLISHING.md to understand the process..." 2. "Checking current version in pyproject.toml and __init__.py..." 3. "Cleaning previous builds..." 4. "Building package with uv build..." 5. "Build successful! Created dist/yaac-X.X.X.tar.gz and dist/yaac-X.X.X-py3-none-any.whl" 6. "Would you like to test on TestPyPI first, or proceed directly to production PyPI?" 7. [After user choice, proceed with upload and verification] 8. "Publication complete! Package is available at https://pypi.org/project/yaac/" ```

{ "prompt": "# Build and Publish yaac Package\n\n## Instruction\n\nYou are helping to build and publish the `yaac` package to PyPI. **Follow the steps in `yaac/publish/PUBLISHING.md` step-by-step**. Do not skip steps or proceed if you encounter errors.\n\n## Key Principles\n\n1. **Reference the documentation**: The full publishing guide is in `yaac/publish/PUBLISHING.md`. Read it first and follow it. Do not duplicate information from that doc here.\n\n2. **Go step-by-step**: Complete each step fully before moving to the next. Verify each step succeeded before proceeding.\n\n3. **Stop on errors**: If you encounter any error, warning, or unexpected output:\n - **STOP immediately**\n - Report the error clearly to the user\n - Ask the user how they want to proceed\n - Do NOT attempt to fix errors without user approval (unless it's a trivial issue you're certain about)\n\n4. **Verify at each stage**: After each major step (build, upload, install), verify it worked correctly before continuing.\n\n## Workflow\n\n### 1. Pre-flight Checks\n\nBefore starting:\n- Read `yaac/publish/PUBLISHING.md` to understand the full process\n- Check current version in `pyproject.toml` and `yaac/__init__.py` (they should match)\n- Verify you're in the correct directory (`/home/phil/code/yaac`)\n- Check if build tools are available (`uv` or `python -m build`)\n\n### 2. Building the Package\n\nFollow the \"Building the Package\" section in PUBLISHING.md:\n- Clean previous builds\n- Build using `uv build` (recommended) or `python -m build`\n- Verify the build created both `.tar.gz` and `.whl` files in `dist/`\n- **If build fails**: Stop and ask the user. Check the troubleshooting section in PUBLISHING.md.\n\n### 3. Testing on TestPyPI (Optional)\n\nIf the user wants to test on TestPyPI:\n- Follow the \"Testing on TestPyPI\" section in PUBLISHING.md\n- Upload to TestPyPI\n- Create a fresh test environment and install from TestPyPI\n- Verify the installation works\n- **If upload fails with \"400 Bad Request\"**: Check if version already exists. Stop and ask user if they want to use a post/dev suffix or skip TestPyPI.\n\n### 4. Publishing to Production PyPI\n\nFollow the \"Publishing to Production PyPI\" section in PUBLISHING.md:\n- Upload to production PyPI\n- Verify the publication (check package page, test installation)\n- **If upload fails**: Stop and ask the user. Check the troubleshooting section.\n\n## Error Handling\n\nWhen you encounter an error:\n1. **Stop immediately** - do not proceed\n2. **Read the error message carefully** - check if it's covered in PUBLISHING.md troubleshooting\n3. **Report to user** - explain what happened and what step failed\n4. **Suggest solutions** - reference PUBLISHING.md troubleshooting or ask user for guidance\n5. **Wait for user approval** - do not attempt fixes without user confirmation\n\n## Updating Documentation\n\nOnly update `yaac/publish/PUBLISHING.md` or this command file if:\n- You discover a **critical issue** that would affect future runs\n- You find a **better approach** that significantly improves the process\n- The documentation is **missing essential information** that caused a failure\n\nDo NOT update documentation for:\n- One-off issues specific to the current run\n- Minor clarifications that don't affect the process\n- Personal preferences or style changes\n\nIf you do update documentation, explain clearly what changed and why.\n\n## User Communication\n\n- **Be clear about what you're doing**: State which step you're on\n- **Report progress**: Confirm when steps complete successfully\n- **Ask before proceeding**: If a step requires user input (like confirming upload), ask first\n- **Summarize at the end**: After successful publication, summarize what was done\n\n## Example Flow\n\n```\n1. \"Reading PUBLISHING.md to understand the process...\"\n2. \"Checking current version in pyproject.toml and __init__.py...\"\n3. \"Cleaning previous builds...\"\n4. \"Building package with uv build...\"\n5. \"Build successful! Created dist/yaac-X.X.X.tar.gz and dist/yaac-X.X.X-py3-none-any.whl\"\n6. \"Would you like to test on TestPyPI first, or proceed directly to production PyPI?\"\n7. [After user choice, proceed with upload and verification]\n8. \"Publication complete! Package is available at https://pypi.org/project/yaac/\"\n```", "variables": [], "notes": "You are helping to build and publish the `yaac` package to PyPI. **Follow the steps in `yaac/publish/PUBLISHING.md` step-by-step**. Do not skip steps or proceed if you encounter errors.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/withyaac/yaac", "path": ".cursor/commands/build_and_publish_yaac.md", "ref": "2f8c71727cbba2c9a050cb6559973ae10705a6c8", "url": "https://github.com/withyaac/yaac/blob/2f8c71727cbba2c9a050cb6559973ae10705a6c8/.cursor/commands/build_and_publish_yaac.md", "key": "withyaac/yaac/.cursor/commands/build_and_publish_yaac.md" } } }

build_and_publish_yaac

About