mmacy

Pair programming with Claude and Codex

You are going to do some pair programming with your colleague, Codex. You will communicate with Codex via file-based chat, in which you read and then write to @PAIR.md in the root of the repo. If PAIR.md does not yet exist, you are to create it.

The way this pair programming session works is that you are given a task to perform, you describe your implementation and reasoning behind it by appending a message to PAIR.md, and then Codex will read it, review your changes, and respond by appending a message to PAIR.md. Their response might only be a message in PAIR.md, or it might also include code changes.

When you edit PAIR.md, you should append a new message to it rather than modify an existing message. Every response in PAIR.md is a new message added to the end of the file below all other existing content in the file.

I am the facilitator and will notify you when Codex has responded, after which you continue the loop with your response in PAIR.md

mmacy

<!-- The project name MUST be a level-one heading. -->
# PROJECT_NAME

<!--
- You MUST accurately describe the project's primary function with a short, one-sentence description.
- You MUST NOT use subjective or marketing-oriented language in this sentence or any other content in this README (e.g. use "A web application for..." not "A simple and powerful web application for...").
-->
PROJECT_DESCRIPTION_SHORT

mmacy

#!/usr/bin/env python3
# /// script
# requires-python = ">=3.12"
# dependencies = [
#     "click",
#     "rich",
#     "py-zerox",
# ]
# ///

mmacy

Prompts

Python Helper

Python 3.11, Pythonic, Google Python Style Guide, type hints, docstrings. Prefix prompt with "TOOL:" (without the quotes) for a single-file script with inline script metadata.

You are a professional Python developer. You help the user who is a seasoned developer design, write, and improve Python code.

The Python code you write and review should:

mmacy

Static site generator comparison matrix

Feature	Jekyll	Docusaurus	Sphinx	Hugo	MkDocs Material
License	MIT (jekyll/LICENSE at master - GitHub)	MIT (Popular open-source tools documentation systems using code - DevOpsSchool.com)	BSD (2‑Clause) (Overview — Sphinx 1.1.3 documentation)	Apache 2.0 ([Popular open-source tools documentation systems using code - DevOpsSchool.com](

mmacy

Current AutoRest output

This is the current code generated by AutoRest for the AdminUserName property:

/// <summary>
/// Gets or sets specifies the name of the administrator account.
/// &amp;lt;br&amp;gt;&amp;lt;br&amp;gt; **Windows-only restriction:**
/// Cannot end in "." &amp;lt;br&amp;gt;&amp;lt;br&amp;gt; **Disallowed
/// values:** "administrator", "admin", "user", "user1", "test",

mmacy

{
  "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {},
  "variables": {},
  "resources": [
    {
      "name": "mycontainergroup",
      "type": "Microsoft.ContainerInstance/containerGroups",
      "apiVersion": "2017-10-01-preview",

mmacy

#!/bin/bash
# create_acr_service_principal.sh
# This script demonstrates how to create a service principal for use with
# Azure Container Registry (ACR) individual or service ("headless") login.
# You can use the service principal credentials to authenticate to the ACR
# instance via 'docker login', or from an unattended service or application.

# Modify for your environment. The ACR_NAME is the name of your Azure Container
# Registry, and the SERVICE_PRINCIPAL_NAME can be any unique name within your
# subscription (you can use the default below).

mmacy

{
    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
      "storageaccountname": {
        "type": "string"
      },
      "storageaccountkey": {
        "type": "securestring"
      }