TRAINING
Hands-on AI-Assisted Development
Mechanical and Electrical track
Prepared for TechnoPro, Inc. / Givery, Inc.
3 days, 8 hours each. Most of the time is hands-on.
This course goes beyond having generative AI do the work and stopping there. It covers checking what comes out yourself before you use it. The aim over the 3 days is that you can build something that works by giving instructions in English, and verify the result with your own eyes.
Each day's goals and how the time is used. Each day is [480min], plus the lunch break. The sessions are about 1 week apart.
| [110min] | Environment setup + creating a GitHub account + Copilot invitation and check (setup slot on the day) |
| [10min] | Break |
| [60min] | Generative AI basics (what it is, how it works, strengths and weaknesses, when to use it and when not, examples in Japan) |
| [70min] | Risk, literacy and governance + handling confidential information (client environments, information leaks, 4 rules for hiding information) |
| [10min] | Break |
| [40min] | How to use VS Code (screen layout, files, basic operations) |
| [100min] | GitHub Copilot basics: 5 short hands-on exercises (one per feature, model switching only introduced) |
| [40min] | Review + guidance on next week's vibe coding theme |
| [40min] | Day 1 recap + environment recheck (there is a gap of about 1 week) |
| [130min] | Vibe coding intro exercise (a theme you thought of beforehand, a game is also fine; get used to coming up with ideas and operating the tools) |
| [10min] | Break |
| [60min] | Prompt basics |
| [40min] | Prompt exercise |
| [10min] | Break |
| [80min] | Data preparation (have the AI read a CSV and clean it up: blank cells, merged cells, multiple sheets) |
| [70min] | Working with tabular data using generative AI (processed in the browser with JS) |
| [30min] | Putting your work theme into words (hide confidential details, organize it for yourself and submit it; no presentation) |
| [10min] | Day 2 closing |
| [22min] | Today's goals |
| [60min] | AGENTS.md and narrowing down the one machine to stop |
| [10min] | Break |
| [45min] | Turning a prompt into a command |
| [87min] | Moving procedures into skills |
| [54min] | Combining the field records into one |
| [10min] | Break |
| [60min] | Turning procedures that worked into reusable assets |
| [18min] | Subagents and model assignment |
| [10min] | Break |
| [104min] | Report on the one machine to stop |
There are only 3, and each has a clear role.
| Tool | Role |
|---|---|
| VSCode | This is where you write code and text. Version 1.116 or later comes with Copilot Chat built in, so Copilot Chat is there from the start. |
| GitHub Copilot | A partner you can consult inside VS Code. You can make your requests in English. |
| Browser (such as Edge) | This is where you run what you built and check it. To load data, drag the file onto the page and drop it. |
The only thing to do before the day is to get your GitHub account ready.
Slides and handouts for each session are gathered here.
You get VS Code and GitHub Copilot working, and learn what generative AI is good and bad at and how to handle information. You try Copilot in 5 small exercises.
You experience how to build something that works by telling the AI what you want in English. In the afternoon, you have the AI clean up messy Excel data.
You decide the one machine to stop from the Plant 2 equipment data and the field records, and write it up as a report. The prompts you use along the way are saved in a folder in a form you can reuse next month.
There is one ZIP per session. Extracting it creates a folder named tpro-work. Put the folder on your desktop.
| Session | For Windows | For Mac |
|---|---|---|
| Session 1 | ME_Day1_handouts.zip | ZIP for Mac |
| Session 2 | ME_Day2_handouts.zip | ZIP for Mac |
| Session 3 | ME_Day3_handouts.zip | ZIP for Mac |
| Session 3 sample | ME_Day3_sample-harness.zip | ZIP for Mac |
| Harness Cheat Sheet | Harness Cheat Sheet (PDF, one A4 landscape page) | |
As participants, you handle information from your client sites. In the exercises, assume the following.
No. The course works with only VS Code and a browser. Data aggregation and charts both run in the browser, using the libraries bundled in the handouts.
The Mechanical and Electrical track is designed for people who are using VS Code for the first time. We go through how to read the screen together.
Yes. The files you create stay on your own device. However, there are limits on what you can submit. See the next item.
Session 2 has no submission or presentation. We will explain how to submit on the day.
Raise your hand. Each exercise has an "If you're stuck" section. You do not have to finish within the time. Finishing everything is not the goal.
Whether you can use it, and to what extent, depends on the agreements with your own company and with the client site where you work. We cannot give a definite answer during the course, so please check through your company's procedures. Here is only how the cost works. GitHub Copilot has a free plan, but it has a usage limit and is not enough for everyday work. Paid plans for individuals start at $10 per month, and the Business plan for organizations is $19 per seat per month. In June 2026, the billing method changed to GitHub AI Credits, which are used up according to the model and the amount of tokens you use. Inline suggestions are not billed, so credits hardly decrease if you mainly use them. (Source: GitHub Docs, checked on September 9, 2026)
This question came from the Session 1 survey. If a file name is merely listed in the Explorer, nothing is sent. Sending starts when you open the file in the editor or select text in it. VS Code attaches the open file and your selection to the conversation even if you do not specify them.
Take care with how .gitignore works. Even if a file is listed as excluded, opening that file bypasses the exclusion. "It is safe because I listed it as excluded" does not hold.
Files are also sent for a question such as "What does this project do?" VS Code keeps an index of the workspace and automatically picks up related files according to what the conversation is about. The official documentation says that content matched by a search is included in the conversation even if the AI does not open the file.
The sure way is not to open a folder that contains confidential files in VS Code. If you have to open it, deal with it in this order: first move the confidential files to another folder so that the workspace does not include them, then use files.exclude to hide them from the Explorer so that you do not open them by accident. (Source: VS Code Docs, checked on September 9, 2026)
These are the terms you will meet during the course. If one is unclear, check it here before you move on.