Personal hub of global Claude Code customizations — umbrella CLAUDE.md, skills, agents, hooks — that apply to every project on the machine via a plugin + a few symlinks.
File one structured report when the MAINFRAME harness itself causes concrete reproducible friction in Claude Code development mode. Use after resolving the immediate block for hook false positives, permission friction, unclear instructions, or a missing harness capability; not for project defects or praise.
Ask the separately installed Codex CLI for one bounded independent review of a consequential decision or completed implementation. Use only at an explicit MAINFRAME review checkpoint; never use it for implementation, ordinary second opinions, or when the Codex peer integration was not installed.
Build and run bounded HTTP(S) requests with curl while preserving request authority, credential safety, explicit timeouts, correct status handling, and safe retry and redirect behavior.
Implements, debugs, reviews, tests, and visually refines client-facing React web applications and established web frontend layers, including UI, UX, accessibility, responsive behavior, component reuse, and focused frontend tests.
Operate and maintain a project's deployment and infrastructure from the primary session: environment topology, Docker and Compose, CI/CD, Dokploy, domains and TLS, observability, and the operational layer of PostgreSQL or Redis. Uses a project-owned infrastructure map and verifies live state before consequential…
Prevent accidental duplicate native development servers and choose the least disruptive correct action for an existing Docker Compose project. Identifies the exact process or Compose project before start, restart, or stop operations.
Run MAINFRAME's project-scoped Pi digital business analyst on a requirements statement or document package explicitly handed over for review. Use when the user asks to review that supplied requirements input. Do not use for ordinary discussion, planning, code research, or implementation.
Delegate one agreed, bounded implementation block to MAINFRAME's project-scoped Pi engineer after the result, boundaries, acceptance criteria, and allowed checks are clear. Use new for a new block and resume for corrections to the active block. Do not use for requirements discovery, architecture decisions, open-ended…
Guides version-aware implementation, debugging, review, and planning for server-side Python services, including FastAPI, Django, Flask, data access, integrations, and focused backend tests.
Safely discover and consume credentials already registered on this machine without reading, echoing, logging, copying, or persisting their values. Uses the repository-owned credentials index for names and the secret helper or a native credential-aware tool for value delivery.
Designs or audits a cross-cutting testing strategy when test levels, suite cost, infrastructure boundaries, or regression coverage need a deliberate decision. Not for routine focused tests already governed by a profile's testing guidance.
Records a concrete problem outside the active task's assigned result or agreed definition of done without expanding scope. Use when work reveals an incidental observation worth preserving or an explicitly assigned investigation confirms a problem with evidence. Does not replace unfinished in-scope work, profile scope…
Prepare a goal that searches a repository or named scope broadly for plausible new problems and records deduplicated observations without fixing or confirming them.
Prepare a goal that implements explicitly autonomous ready tickets one at a time, obtains red evidence where useful, validates each result, and queues it for independent verification.
Prepare a goal that verifies, scopes, splits, and consolidates open ticket observations, routing each result to technical work, a user decision, or rejection.
Prepare a goal that independently checks implemented tickets, archives proven fixes, and returns failed work to the correct open queue without repairing it inline.
Guides version-aware implementation, debugging, review, and planning for server-side TypeScript in Node.js, NestJS, Express, Fastify, and established Next.js server routes, including focused backend tests.
Build and run bounded HTTP(S) requests with curl while preserving request authority, credential safety, explicit timeouts, correct status handling, and safe retry and redirect behavior. Use when checking or driving an endpoint from the terminal, verifying an API handler, uploading or downloading by URL, diagnosing a…
Independently challenge a consequential proposed decision, design, architecture, or approach before acceptance. Use for non-obvious tradeoffs or a high cost of being wrong; do not use for routine low-risk choices, implementation, or general defect discovery in existing code.
Implement, debug, review, test, or visually refine client-facing React web applications and established web frontend layers. Use for pages, components, forms, browser data, accessibility, responsive layouts, UI and UX, shadcn component reuse, PWA or offline behavior, realtime interfaces, rich content, visualizations…