Use Claude Code: start your first task in a practice folder

Claude Code can read and edit code in a working folder and run commands. It can also handle non-coding work such as organizing documents and converting files, and accepts requests in Korean.

Capabilities depend on available tools and permissions. This guide uses a terminal; consult the official instructions for installation and supported environments.

Consult the official documentation for the installation method and account for your operating system. If a terminal is new to you, first learn where to enter commands and how to move into the working folder.

Copy a few non-sensitive files into a practice folder. Check that you are in that folder before starting, and try changes to important originals on copies first.

Start with a read-only request such as “List the files in this folder and explain their purposes. Do not change any files.” Check which files the AI says it inspected.

Next ask it to create one new document, then open it yourself. Before modifying existing files, keep a copy or version history and compare the before and after.

“Combine the CSVs in this folder and save result.csv” defines the scope more clearly than “organize my data.” Include files it must not change and conditions to verify.

If the result is wrong, identify a specific fix, such as “Format the date column as YYYY-MM-DD.” Divide large tasks into stages whose intermediate results you can inspect.

If a file is missing, check the current folder and requested path. If an important instruction was not followed, inspect which document was read and its scope.

Do not rely on a completion message alone; open the generated file. When asked for permission, read what command will affect which files or external services before proceeding.

New drafts and file organization are relatively easy to inspect and correct. Sending email, public posting, payment and deletion need a review of their targets and results.

If you repeatedly explain the same boundaries, write them in CLAUDE.md for future tasks. An instruction file helps, but important execution results still need to be checked.

If you repeat the same prerequisites and steps, record them in SKILL.md: when to use the skill, the input, the desired output and how to check it.

Put the skill folder in a supported location and actually invoke it. When sharing with a team, include required programs and example inputs so a new user can follow along.