Our AI resources and what a client should know

01The tools are part of the work

Nicholas uses Claude Code and Codex. Product design starts with Claude /design. Claude Code is generally the implementation tool; Codex is generally the review tool and is also used for images, logo directions, landing pages, and websites. Some work uses both.

That is a workflow preference, not a promise that one vendor or model is always better. Model versions, account access, and tool capabilities change. The model guide is a dated reference, while a project should record the versions and tools actually used.

• Tool and model selection guide
• Community reports and their limitations

02Separate the workbench, model, tools, and project services

The workbench is Claude Code or Codex. A selected language model handles reasoning and code generation. An image tool may use a different model. Connected tools can add repository access, browser actions, design assets, or other services. Those are separate access and cost decisions.

This site itself uses Next.js, React, TypeScript, and Vercel integrations, with Resend for configured contact delivery. A technology used by the portfolio is not automatically required for your product. Reuse the systems that fit the engagement.

03What the commercial terms should make explicit

Ask the written scope to state whether subscriptions and usage are included, billed separately, or supplied through client-owned accounts. It should identify any pass-through charges or markup, spending limits, who approves extra usage, and who owns the accounts afterward.

This page does not set a universal usage allowance, subscription reimbursement policy, or markup. Those terms need to be confirmed for the engagement. Provider pricing and included limits can change, so compare the current plan and expected workload before setting a budget.

04Agree on access before supplying private information

Identify which code, documents, assets, and data can be shared with each tool and which integrations are permitted. Confirm the account and provider settings that apply to the work. Do not assume every plan has identical data handling.

Use representative or redacted examples when possible. Keep credentials in approved secret storage, grant only the access the task needs, and plan to remove temporary access after handoff. If a task requires production data or a production action, make that requirement explicit before the task starts.

05The useful deliverable is inspectable work

A client should be able to see what changed, why it changed, what was checked, and what remains uncertain. A handoff can record the models and tools used alongside the revision, design references, tests, and operating instructions.

Model agreement, hours of agent activity, or a large token count are not evidence of business value. Judge the work against the outcome, acceptance criteria, and responsibilities agreed for the project.

• AI-assisted delivery workflow
• Review and handoff prompts