VELOR · EDITION 01
100items
Claude Field Guide to Mastering Claude
The Claude guide is VELOR's free AI education resource: 100 practical items on using Claude at work, written for seniors and mid-career professionals. One hundred items for putting Claude to work, across ten domains — setup, model choice, prompting, connectors, and governance. A person stays accountable for every output.
01
Cowork Setup
Set up the desktop app and folder structure everything runs on.
001
Download the desktop app. Not the browser.
002
Create a shared folder on your PC called 'COWORK' that you can access from your work phone.
003
Drop in your HR + org strategy, HR goals, and policy documents.
004
Add an "About Me" file: your role with clear responsibilities, your company, your HR stack.
005
3 subfolders: Projects, Templates, Outputs.
006
One template per deliverable: JD, policy, performance review, offer letter.
007
Name files by what they do, not what they are. "JD-senior-HRBP" beats "Document1-final-v3".
008
Point Claude at the COWORK folder once. It works from there.
009
Update the About Me file every quarter. Your role shifts. Claude needs to know.
010
Keep the folder lean. 20 great files beat 200 mediocre ones.
02
Pick the Right Model
Match the model and thinking depth to the task.
011
Opus 4.8 + Extended Thinking for complex (workforce) planning and policy drafting.
012
If the task has a right answer, use the smallest model that gets there.
013
If the task needs judgment, upgrade the model before you upgrade the prompt.
014
Switch models mid-chat. Ideate and draft with Opus, edit with Sonnet.
015
Keep Opus usage limits in mind.
016
Split complex tasks into smaller steps for better output.
017
Sonnet = job description edits. Haiku = scanning CVs and policies.
018
The model matters less than the prompt.
019
Extended Thinking for anything related to advanced policies.
020
Skip Extended Thinking for drafting emails and meeting notes. It will overcomplicate.
03
Prompting
Direct it in short, clear, single-task instructions.
021
Stop writing long prompts. Files > prompts.
022
Tell Claude who the output is for. "For the CHRO" and "for line managers" land differently.
023
Ask for the output format up front. Table, bullets, memo, Slack message.
024
If the first draft misses, don't start over. Tell it what's wrong.
025
"Be critical" beats "be helpful" when you're pressure-testing a decision.
026
Save your 10 best prompts. Reuse them. Upgrade them into skills. Don't reinvent.
027
One task per prompt. One. Not five.
028
Say "Does NOT sound like" to kill the corporate-AI voice in your comms.
029
Give the task, not the method. Let it figure out the approach.
030
Show an example of what "good" looks like. Tell > explain.
04
AskUserQuestion
Turn a vague brief into clickable questions.
031
Start every first prompt with "Start with AskUserQuestion."
032
Use it for policy writing. It asks about jurisdiction, audience, tone.
033
Claude builds you a clickable form. Click your answers.
034
Use it when a stakeholder hands you a vague brief. Let Claude narrow it.
035
It asks the right questions so you don't have to spec every detail.
036
Skip it for tasks you've done 50 times. You already know the spec.
037
If the direction is wrong, say so. It rebuilds instantly.
038
Works best with Opus. The questions are sharper.
039
Use it for JD drafting. It asks about level, scope, must-haves.
040
BUT a complete prompt always beats AskUserQuestion.
05
Connectors
Connect Claude to the systems your work lives in.
041
Settings → Connectors → Browse → Add.
042
Most enterprise connections are still being built — this will only get better.
043
Connect Gmail for drafting responses in your voice. It reads your sent folder.
044
Connect Notion if your people ops playbook lives there.
045
Disconnect what you don't use. Fewer surfaces, cleaner context.
046
Be deliberate about what Claude can see. Permissions matter in HR.
047
Start with Atlassian, SharePoint, or Drive. That's where your HR policies already live.
048
Connect Slack, Microsoft 365, Miro, Gmail.
049
Free on all plans. No extra cost.
050
Claude reads your actual files. No more exporting and re-uploading.
06
The HR Plugin
Standardize recurring HR work with plugins.
051
Cowork → Customize → Browse → Install.
052
Policy plugin: still get legal review. Plugins draft, you edit, lawyers approve.
053
JD plugin: feed it your leveling framework, competency framework, similar jobs.
054
Build an internal plugin for your competency model. Once. Reuse forever.
055
Read the detailed skills, most of the skills are a first draft, not production-ready.
056
Duplicate plugin skills to improve them and share them with the team.
057
Pick the HR plugin. Compensation benchmarking, policy drafting, job architecture.
058
Type "/hr" to trigger any plugin command instantly.
059
Customize to match your company voice and EVP.
060
Comp benchmarking plugin: verify the sources. More input = better benchmark.
07
Claude in Excel
Use it as an analyst that reads and checks spreadsheets.
061
Install "Claude by Anthropic" from the Microsoft Marketplace.
062
Ask it to explain what a predecessor built. Saves days of reverse-engineering.
063
Use it for attrition analysis. It spots patterns across tabs.
064
Never paste sensitive pay data into the web chat. Use a paid corporate account.
065
Always double-check the math on anything that changes a paycheck.
066
Treat it as a junior analyst. Fast, capable, still needs review.
067
It reads every tab. Explains headcount formulas in plain English.
068
Drop a PDF salary survey in. Claude extracts the tables for you.
069
No macros. Claude highlights every cell it touches.
070
Use it to audit comp bands. It'll flag outliers you missed.
08
Claude Skills
Turn repeat work into instructions you build once.
071
Skills are reusable instructions Claude loads on demand. Build once, trigger forever.
072
Put your leveling framework, tone rules, and must-include clauses inside the skill.
073
One skill per job. Don't build a mega-skill that does everything badly.
074
Test the trigger. Ask a fresh question and see if Claude picks the right skill unprompted.
075
Share skills across your HR team. Consistency beats individual cleverness.
076
Version your skills like policies. Date them. Review quarterly. Retire the stale ones.
077
Install from the skill library or write your own. No code required for most.
078
Name the skill for the job, not the tool. "comp-band-analysis" beats "my-skill-v2".
079
The description field is everything. It's how Claude knows when to trigger the skill.
080
Write skills for tasks you repeat weekly: JD drafting, inbox cleaning, policy reviews.
09
Artifacts
Build dashboards, calculators and one-pagers in chat.
081
Headcount dashboards, attrition trackers, comp models — inside the chat.
082
Build a quick interactive calculator when a stakeholder asks "what if."
083
They work automatically in Cowork.
084
Use them to visualize survey data before you write the exec summary.
085
Only share confidential Artifacts within your team plan. Never publicly.
086
Iterate inside the Artifact. Don't restart the conversation.
087
Save the best Artifacts as templates. Reuse beats rebuild.
088
Preview before you export. Edit it live. Then copy.
089
Share with non-Claude colleagues through the share button.
090
Use Artifacts for one-pagers to the CHRO. They land better than slides.
10
Advanced Mastery
The governance line: people stay accountable.
091
Keep your files under 200 lines. Shorter is better.
092
Don't let Claude make any decisions with consequences — you're in charge and responsible.
093
Always have a human in the loop for anything an employee or colleague will read.
094
Document your prompts like you document your processes. They're IP now.
095
If an output feels generic, it is. Rewrite the brief, not the output.
096
Teach your team to spot AI voice. It's the new plagiarism.
097
Avoid AI slop. Just… don't.
098
Review every output critically.
099
Claude does 80% of the busywork. You do the 20% that needs judgment.
100
Never let Claude make a termination, promotion, or hire decision. Ever.
Korean Resources
WeeklyCurated Korean creators, well-known sites, and official docs — with sources. Read the originals at each link.
001
황민호 · Kakao · GitHub·2025
Claude Code 마스터링 — 한국어 가이드북
A full Korean Claude Code guidebook by a Kakao engineer — from install to real workflows.
↗
002
위키북스 · brunch·2026
클로드 코드 제대로 쓰는 법 — 5가지 필수 설정
Five core Claude Code settings — CLAUDE.md, permissions, and more.
↗
003
skysoo · velog·2025
Claude Code 완벽 가이드 — 한글 요약본
A Korean summary of the popular 'Cooking with Claude Code' guide.
↗
All listed materials remain the copyright of their authors and publishers. This page links to sources with attribution and does not reproduce their content.
FAQ
QWhat is Claude best at?
Reading long documents and contracts, then summarizing the key points — and careful writing. Useful for reviewing reports and summarizing materials.
QIs Claude free to use?
A free plan covers everyday use; consider a paid plan for heavy use. This guide starts within the free tier.
QWhat should a first-time Claude user try?
Paste a long document and ask, in plain language, to 'summarize the three key points.' The 100-item guide walks you through it.
VELOR insights · career hub
Content connecting AI skills to senior careers.