BUILD WITH X1 · FICTIONAL PRACTICE

One useful question. Your own project.

Build or extend the financial view you want. Start with the files you have; connect your authorized X1 record when finding, revisiting or carrying supported work forward helps.

The instructions below have no connection, executable script or permission grant. An assistant can make the local example while access to X1 is unavailable.

1. Try a complete practice prompt

• Property parties: who is named, in which role?
• Bookkeeping: right entity and right month?
• Insurance: what do these dated sources establish?
• Your proposed Friday: what question comes first?

These exercises work without X1. They do not establish a current owner, reconciliation, current coverage or a completed four-day-workweek plan.

2. Give your assistant the builder instructions

Copy the instructions and recipes as task context, then ask for the change you want in your existing project. For a native local skill, download the two-file skill folder and inspect any existing folder before copying.

Claude Code project: .claude/skills/build-with-x1/, invoked with /build-with-x1. Codex project: .agents/skills/build-with-x1/, invoked with $build-with-x1. These loading paths were checked in Claude's docs and OpenAI's docs on October 11, 2026; Claude Code 2.1.296 registered this project command in a bounded read-only fictional test. Restricted-mode runs did not register it; supply the instruction files as task context when the host suppresses local skills. Codex CLI 0.162.1 discovered the project skill and returned a useful answer from supplied fictional text. Its reference-file read failed at sandbox startup; full runtime loading was not verified. Connected record execution has not been tested in either host.

Chat or another host: use its supported attachment/paste path, or its actual native skill setup if available. A pasted file does not install a skill or import an MCP connection.

Copy builder instructions

3. Connect only the path you can verify

Use the supported X1 setup for your host, then inspect mounted tools and account eligibility. Keep credentials out of browser code. A chat's MCP connection does not automatically connect its generated UI.

Start read-only. Keep source/page, actual source date and unknown fields visible. Refresh must read again. A saved change needs the available operation, requested effect and its actual approval/completion contract; a pending request is not saved.

Keep private sources and copied data in your chosen private environment. This resource makes no data request, stores no inputs and calls no model. No connected rehearsal, independent builder result or public release is claimed.