Developer tools & Mac readiness

UTILITY 01

Task prompt builder

Generated specification

LIVE PREVIEW / REVIEW BEFORE USE

Improve the project navigation on small screens.
Inspect the current header, styles, scripts and applicable AGENTS.md first.
Requirements: usable at 375–1920 CSS px, keyboard operable, visible focus,
Escape closes the menu, focus returns to the opener, no page overflow.
Preserve existing routes, search and desktop behavior. Add no dependencies.
Identify affected files and propose bounded steps before implementing.
Verify the controls in a browser and report viewport coverage and failures.

UTILITY 02

AGENTS.md generator & download

Provide real repository commands. The starter example describes a static site; replace it for other stacks. The file guides an agent and does not enforce filesystem permissions.

AGENTS.md preview

LIVE PREVIEW / ADAPT TO YOUR REPOSITORY

# AGENTS.md — Project engineering agreements

## Context and scope
This example is for a static website with HTML, CSS and JavaScript.
Inspect README.md, applicable instructions and existing files before editing.
Keep the site deployable as static files. Do not add a backend or framework.
Preserve existing routes, accessible controls and public behavior.
Use directory instructions for specialized modules. Identify conflicts.

## macOS development
Use UTF-8 and LF; quote paths with spaces. Keep filenames case-consistent.
Use portable shell syntax or explicitly declare zsh-specific scripts.
Do not assume GNU utilities or a particular Homebrew prefix.
Never use sudo to fix a project dependency installation without diagnosis.

## Build and test
No production build is required for this example static site.
Preview: python3 -m http.server 8765 --bind 127.0.0.1
Check JavaScript: node --check assets/js/app.js
Test all changed interactions, keyboard access and mobile layouts.
Check links, assets and browser console. Replace example paths if different.
Run repository-defined checks; report actual commands, exit codes and scope.

## Security and completion
Never commit .env files, credentials or diagnostic logs containing secrets.
Do not disable Gatekeeper, change global permissions or deploy without scope.
Review git diff and git diff --staged. Preserve unrelated user work.
Report files changed, verification evidence and remaining limitations.

Production completion checklist

Manual review record. Mark an item after checking its evidence. These selections do not run tests or certify readiness; record any inapplicable checks and reasons separately.

Recorded checks0 of 15 recorded

Requested behavior meets the acceptance criteria.Existing behavior has been checked for regressions.No unfinished placeholders or fake implementations remain.Invalid inputs, empty states and error paths were exercised.Formatting follows repository conventions.Applicable lint checks passed or a justified exception is recorded.Applicable type/compiler checks passed.Relevant automated tests were actually executed.The production build or static deployment check succeeded.Secrets, input handling and permission changes were reviewed.Keyboard, focus, contrast and responsive behavior were checked.Working-tree and staged diffs were reviewed.Target-platform manual tests and their limits are recorded.Setup, architecture and usage documentation are current.Known limitations and deployment/recovery steps are recorded.

UTILITY 04

Git command safety helper

Choose a command by its effect. Review the current state before modifying it. A clean tree does not prove tests passed, and an ignored file can still contain a valuable secret that needs a separate backup policy.

Inspect current work

Unstaged and staged diffs cover different snapshots. Inspect untracked files separately.

SAFE / INSPECTION

git status
git diff
git diff --staged
git log --oneline -5

Initialize a new project

Use only for a project that is not already a repository. This does not create a remote or a backup.

PROJECT MODIFICATION

git init -b main

Create a reviewed checkpoint

Substitute reviewed files. Inspect secrets and unrelated changes before committing.

PROJECT MODIFICATION / EXAMPLE PATHS

git add -- index.html assets/css/app.css
git diff --staged
git commit -m "checkpoint: before navigation changes"

Isolate the next change

Creates a branch but does not snapshot dirty files. For concurrent work, use separate worktrees.

PROJECT MODIFICATION

git switch -c feat/navigation

Inspect cleanup candidates

Lists untracked cleanup candidates. The force variant deletes them and bypasses Trash. Do not treat all untracked files as disposable.

SAFE / DRY RUN ONLY

git clean -nd

Destructive Git operations: understand the consequence

git restore on a working-tree path overwrites unstaged edits from the chosen source. git reset --hard discards tracked working changes and can remove obstructing untracked paths. git clean -fd deletes untracked files and directories. None is a routine “undo AI” button. Preserve user changes and use a reviewed, path-specific recovery plan. For an already-shared commit, evaluate a corrective commit or git revert with the team.

Project readiness review

Manual review record. Mark an item after checking its evidence. These selections do not run tests or certify readiness; record any inapplicable checks and reasons separately.

Recorded checks0 of 15 recorded

Required The project directory and Git working tree are understood.Required A selective checkpoint or preservation strategy exists.Required README setup and acceptance criteria are usable.Required Applicable AGENTS.md instructions have been reviewed.Required Required build and test commands are identified.Recommended Lockfiles and runtime versions are documented.Recommended A secret-free .env.example describes configuration.Recommended Ignored files include generated output and local secrets.Recommended Architecture and ownership boundaries are documented.Recommended At least one meaningful regression check is available.Recommended Deployment and recovery are documented.Optional SSH is configured if the remote uses SSH.Optional Apple Silicon testing exists if targeting arm64.Optional Intel testing exists if supporting x86_64.Optional Signing and notarization are planned if distributing Mac apps.

UTILITY 06

Mac readiness diagnostic

This page cannot see your macOS version, installed software or filesystem. Download and inspect the script, run it locally from your intended project, then paste its output. The script prints a small allowlisted report without collecting secrets, file contents or personal paths. Read the code before running any downloaded script.

Download diagnostic script

LOCAL INSPECTION / READ SCRIPT FIRST

# From your intended project, use the actual downloaded file path
sh "$HOME/Downloads/codac-diagnostic.sh"

Inspect the full diagnostic script

SCRIPT SOURCE / AVAILABILITY ONLY

#!/bin/sh
# Codac diagnostic v1: prints availability only. No installs, network, credentials,
# file contents or paths are collected. Run in the intended project directory.
# command -v checks resolution, not tool health, version compatibility or login.
printf 'CODAC_DIAGNOSTIC_V1\n'
if [ "$(uname -s)" = Darwin ]; then
  printf 'os=macOS\n'
  printf 'version=%s\n' "$(sw_vers -productVersion)"
  printf 'arch=%s\n' "$(uname -m)"
  translated=$(sysctl -in sysctl.proc_translated 2>/dev/null)
  case "$translated" in 1) printf 'translated=yes\n';; 0) printf 'translated=no\n';; *) printf 'translated=unknown\n';; esac
  if xcode-select -p >/dev/null 2>&1; then printf 'clt=available\n'; else printf 'clt=missing\n'; fi
else
  printf 'os=other\nversion=unknown\narch=unknown\ntranslated=unknown\nclt=unknown\n'
fi
for tool in git brew node npm python3 rustc cargo codex ssh; do
  if command -v "$tool" >/dev/null 2>&1; then
    printf '%s=available\n' "$tool"
  else
    printf '%s=missing\n' "$tool"
  fi
done
printf 'project=available\n'
# Only invoke Apple's known Git after a developer-directory check on macOS.
# GIT_OPTIONAL_LOCKS avoids optional index refresh writes.
if [ "$(uname -s)" = Darwin ] && xcode-select -p >/dev/null 2>&1; then
  if GIT_OPTIONAL_LOCKS=0 /usr/bin/git rev-parse --is-inside-work-tree 2>/dev/null | grep -qx true; then
    printf 'repository=available\n'
  else printf 'repository=missing\n'; fi
else printf 'repository=unknown\n'; fi
printf 'END_CODAC_DIAGNOSTIC\n'

Practical tools. Your data stays here.