Chapter 25 · CLI
Design, artifacts and moving work between canvas and code
Artifacts let you share session output as a standalone product: a page, document or demo. The flow between design work and project code turns quick experiments into real deliverables.
Video
Steps
- Ask for output as an artifact when you want something standalone to share, not another code change.
- Verify the artifact looks right before sharing: open and inspect it, especially visual output.
- When a demo succeeds, move the result into project code properly: file, test and commit.
- Use the relevant commands to share and manage artifacts, and clean up old ones you no longer need.
Common pitfall: A shared artifact is public to anyone with the link; check what it contains before distributing, especially real data.
Hands-on exercise: Create a small artifact (a simple landing page, for example), inspect it visually, then move one component from it into the project with a test.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
What do you check before sharing an artifact?
Recap
- Artifacts for standalone shareable output
- Visual check before distributing
- Move successes into code with tests