iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The most reliable Claude Code instruction set is short, concrete, and scoped to the work it actually governs. Keep durable project facts and recurring team conventions in a root CLAUDE.md, move path-specific rules into .claude/rules/, and put task procedures in skills. Write every rule as an observable action with a command, path, format, or expected result.
This arrangement gives Claude useful context without burying important guidance in a large, contradictory file. It also makes maintenance predictable: review instruction files for stale rules, keep each CLAUDE.md below the 200-line target, and use a PreToolUse hook when an action must be blocked rather than merely discouraged.
What concise Claude Code instructions should accomplish
An instruction file is context that Claude Code reads while working; it is not an enforcement layer. Its job is to give a new session the small set of facts and decisions needed to act consistently. The Claude Code documentation puts the principle plainly: “The more specific and concise your instructions, the more consistently Claude follows them.”
Free tools Windows power users keep installed
One-click scans. No signup required.
A useful rule answers four questions without requiring interpretation:
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
- What action is required? State the behavior, not a general aspiration.
- Where does it apply? Identify the project, directory, file pattern, user scope, or task.
- How can it be checked? Name a command, output format, path, or review condition.
- When is it needed? Keep every-session guidance separate from occasional procedures.
For example, “Test your changes” leaves the test command and scope open. “Run npm test before committing” gives Claude and the developer an action that can be verified. “Use 2-space indentation” is similarly more useful than “format code properly.”
Decide where each instruction belongs
Claude Code supports several places for guidance. Choose by scope, frequency, and purpose rather than by file size alone.
| Location or mechanism | Scope | Best use | Loading or behavior note |
|---|---|---|---|
Root CLAUDE.md |
Project-wide | Build and test commands, key directories, coding conventions, architecture decisions, and recurring workflows | Keep durable facts that a new teammate needs in most sessions |
| User-level instructions | Personal, across projects | Individual working preferences that should not become team policy | Separate personal preferences from source-controlled project conventions |
| Managed instructions | Organization-wide | Standards that an organization wants carried across projects | Use for shared organizational guidance, not repository-specific details |
.claude/rules/ |
Path-specific or modular project areas | Rules for a particular language, package, directory, or file pattern | Path frontmatter can limit a rule to matching files |
| Skills | Task-specific | Multi-step procedures needed only for a particular kind of task | Keep procedural detail out of the always-loaded project brief |
| Auto memory | Accumulated learnings and patterns | Observations Claude has retained over time | Complementary to written instructions; its first 200 lines or 25KB are loaded |
PreToolUse hook |
Tool-action enforcement | Rules that must prevent an action regardless of Claude’s choice | Use this when documentation alone is not a sufficient control |
Project instructions belong in source control when they represent team standards. User-level instructions should remain personal. Auto memory records learnings and patterns, while CLAUDE.md is where people deliberately write instructions and rules. Do not treat memory as a replacement for a clear project contract.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBuild a small, durable root CLAUDE.md
Start with the information that is both stable and frequently needed. A root file should orient Claude quickly, not document every possible workflow.
1. Record the project map
Name the directories that matter and describe their roles in one line each. Include the application entry point, test location, generated-output directory, and any area that should not be edited directly. Avoid cataloging every file; the purpose is to help Claude navigate.
2. Add the commands people actually run
List the commands for installing dependencies, starting development, running focused tests, running the full suite, linting, formatting, and building. Include the expected scope when a command is easy to misuse. For example:
## Verification
- Run `npm test` before committing.
- Run `npm run lint` for JavaScript and TypeScript changes.
- Run `npm run build` when changing build configuration or production bundles.If a command requires a particular directory, environment variable, or service, state that alongside the command. A command without its prerequisite can create avoidable failures.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
3. Capture conventions that recur
Document naming, formatting, error-handling, test placement, and API conventions only when they are genuine project standards. A short rule such as “Use 2-space indentation” is stronger than a paragraph about readable formatting. If a convention applies only to one directory, move it to a path-scoped rule instead.
4. Preserve architectural decisions
Include decisions that explain why the code is organized as it is: boundaries between services, ownership of generated files, approved integration points, or a migration constraint that a new contributor would otherwise miss. Keep the explanation brief and link the decision to a concrete directory or command when possible.
5. Describe the recurring workflow
State the sequence Claude should follow for ordinary changes, such as inspect the relevant files, edit the smallest necessary surface, run focused tests, then run the broader verification command. If the sequence is long or applies only to one task type, make it a skill instead of expanding the root file.
Turn vague preferences into verifiable rules
Specificity is the fastest way to improve adherence. Replace subjective verbs with actions and observable checks.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match| Weak instruction | Specific replacement | Why the replacement works |
|---|---|---|
| Test your changes | Run npm test before committing and report the failing test name if it does not pass. |
It names the command, timing, and failure information. |
| Keep the code clean | Use the existing formatter; run npm run lint on changed JavaScript and TypeScript files. |
It identifies the tool and the files in scope. |
| Organize imports properly | Place standard-library imports first, third-party imports second, and relative imports last; preserve the formatter’s ordering. | It defines an order that can be checked. |
| Update documentation when needed | When a command, configuration key, or public API changes, update the README section that documents it in the same change. | It defines the trigger and the expected artifact. |
| Be careful with generated files | Do not edit dist/ directly; change the source and regenerate it with the project build command. |
It identifies both the forbidden path and the correct alternative. |
Use numbered steps or bullets when sequence or completeness matters. Anthropic’s broader prompting guidance also recommends spelling out the desired output format and constraints, and consulting model-specific guidance because behavior recommendations can differ by model.
Keep path-specific rules in .claude/rules/
A root file becomes noisy when it contains instructions for unrelated parts of a repository. Put specialized guidance in descriptive Markdown files under .claude/rules/. A rule can include path frontmatter so it applies only to matching files.
Example path-scoped rule
---
paths:
- 'src/api/**/*.ts'
---
# API rules
- Validate request data at the route boundary.
- Return the project’s standard error shape.
- Add or update an endpoint test in `test/api/` for every route change.The exact pattern should describe the files that need the rule, not the whole repository. Keep the file name descriptive, such as api.md, frontend.md, or database-migrations.md. If a rule applies to several related paths, list those paths together; if it applies to almost everything, it probably belongs in the root file.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Split by responsibility, not by sentence
Good modules group decisions that change together. A frontend rule can cover component structure and browser tests; a database rule can cover migration ordering and rollback checks. Do not create one file per tiny preference. Too many fragments make it difficult to discover which instruction controls a change.
Resolve overlap deliberately
When a root rule and a path rule cover the same behavior, make the relationship explicit. Put the default in the root and the exception in the scoped file, or move the entire topic into the narrower file. Contradictory instructions are worse than missing instructions because Claude must choose between them.
Use skills for procedures, not permanent policy
A multi-step procedure can consume a large portion of the project brief even when it is needed only occasionally. Skills are a better home for workflows such as preparing a release, adding a database migration, or investigating a production incident.
A skill should state prerequisites, the ordered actions, the commands to run, expected outputs, and recovery branches. The root CLAUDE.md can point to the procedure without reproducing every step. This keeps everyday context small while preserving a repeatable method for the task that needs it.
What belongs in a skill
- A sequence that must be followed in order.
- Temporary files, environment setup, or task-specific tools.
- Checks that apply to one operation, such as a release or migration.
- Failure handling and rollback instructions that would distract from normal development.
What does not belong in a skill
- A project-wide coding convention used in nearly every session.
- A personal preference that should not affect teammates.
- A security control that must block an action; use an enforcement hook for that.
Keep instruction files below the 200-line target
Claude Code guidance recommends keeping each CLAUDE.md under 200 lines as a target. Longer files consume more context and can reduce adherence. The target is a maintenance signal, not a license to compress a necessary rule into ambiguous shorthand.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What to remove first
- Duplicated rules stated in several sections.
- Background explanations that do not change an action.
- Commands that no longer exist or are superseded by another command.
- Instructions for a directory that now has a scoped rule.
- Personal preferences that belong in user-level guidance.
- Procedures that can move to a skill.
Use a quarterly or change-triggered audit
Review the root file and every nested instruction file when the build system changes, a recurring review comment appears, a directory moves, or a teammate repeatedly makes the same avoidable mistake. During the review:
- Run every command listed in the file and remove commands that are no longer valid.
- Check every path, package name, and file pattern against the current repository layout.
- Mark rules that describe behavior no longer used by the project.
- Search for contradictions between root instructions, scoped rules, and skills.
- Merge duplicate guidance and move specialized material to the narrowest useful scope.
- Ask whether a new teammate could verify each remaining instruction without guessing.
Prefer a short rule with a check over a long explanation
“Run npm test before committing” is more maintainable than a paragraph explaining why tests matter. Keep rationale when it preserves an architectural decision or prevents a dangerous misunderstanding; remove rationale that merely repeats the rule.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Understand imports and context loading
Imports can make a long file easier to navigate, but they still load at launch, so they do not save context by themselves. Use imports for organization and discoverability, not as a strategy for hiding a large instruction set.
The same principle applies to auto memory. Its first 200 lines or 25KB are loaded, so accumulated notes should remain focused and useful. Memory is complementary to deliberate project instructions: move a repeatedly confirmed project convention into CLAUDE.md, while leaving transient learnings and patterns in memory.
Recommended Free Tools
Separate guidance from enforcement
Documentation can tell Claude what to do, but it cannot guarantee that Claude will never choose an unsafe action. The Claude Code documentation describes instruction files as context rather than enforced configuration. If an action must be blocked regardless of Claude’s judgment, use a PreToolUse hook.
Use instructions when
- The goal is consistent style, workflow, or decision-making.
- A human can review the result and correct a deviation.
- The rule is advisory or has a reasonable exception.
Use a PreToolUse hook when
- A tool call must be rejected under a defined condition.
- A path, command, or operation is prohibited without exception.
- Compliance must not depend on the model remembering a paragraph of context.
Keep the explanatory rule in the appropriate instruction file so people understand the policy, and implement the blocking behavior in the hook. Do not describe a hook as if it were merely a suggestion.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A practical layout for a maintainable repository
A small project might use this structure:
CLAUDE.md
.claude/
rules/
api.md
frontend.md
skills/
release.md
migration.mdThe root file can contain the project map, common commands, universal conventions, architectural boundaries, and the normal change workflow. api.md and frontend.md hold path-specific rules. The release and migration skills hold ordered procedures that most sessions do not need.
Example root content
# Project overview
- `src/` contains application code.
- `test/` contains automated tests.
- `dist/` is generated; do not edit it directly.
# Verification
- Run `npm test` before committing.
- Run `npm run lint` for JavaScript and TypeScript changes.
# Conventions
- Use 2-space indentation.
- Match existing naming and error-handling patterns.
# Workflow
1. Inspect the relevant source and tests.
2. Make the smallest change that satisfies the request.
3. Run focused tests, then the required broader checks.
4. Report commands run and any failures.This example is intentionally compact. A real project should replace the illustrative paths and commands with its own verified values rather than copying them unchanged.
Diagnose common instruction problems
Claude ignores an important rule
Check whether the rule is buried under unrelated detail, stated vaguely, or contradicted elsewhere. Move a durable project rule nearer the top of the root file, rewrite it as an observable action, and remove competing wording. If it applies only to a path, place it in a scoped rule instead of repeating it globally.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
The root file keeps growing
Classify each section by scope and frequency. Move path-specific material to .claude/rules/, occasional procedures to skills, and personal preferences to user-level instructions. Delete historical explanations that no longer affect a decision. Recheck the line count after every move.
Rules conflict after a refactor
Compare the root file, nested instruction files, rules, and skills against the new directory layout and commands. Choose one authoritative location for each behavior. Put the general default in the broad scope and the exception in the narrow scope, then remove obsolete wording.
A command in the instructions fails
Run it in the directory and environment implied by the file. If the command has changed, update the instruction and state any prerequisite service, variable, or package manager. A stale command should be corrected immediately because it trains future sessions toward a known failure.
A prohibited operation still occurs
Do not add more prose and assume the problem is solved. If the action must be prevented, implement a PreToolUse hook and retain a concise explanatory rule for human readers.
A decision framework for every new instruction
Before adding a sentence, classify it with these questions:
- Is it durable? If it changes frequently, keep it in a task procedure or current project documentation instead of the root brief.
- Is it shared? Team standards belong in source control; personal preferences belong at user scope.
- Is it universal? If it applies to one path or file type, use
.claude/rules/. - Is it procedural? If it requires several ordered actions, use a skill.
- Can someone verify it? Add a command, path, format, expected output, or explicit review condition.
- Must it be enforced? If yes, pair the policy with a
PreToolUsehook.
This test prevents the root file from becoming a miscellaneous notebook. It also makes future edits safer: each instruction has an obvious home, audience, and maintenance trigger.
Quick Recap
Final maintenance checklist
- Every recurring command has its exact command name and scope.
- Every path-specific convention is outside the global file unless it truly applies everywhere.
- Every multi-step workflow is in a skill with prerequisites and checks.
- Personal preferences are separate from team policy.
- Rules use concrete verbs and observable outcomes.
- Imports organize files but are not used to conceal excessive context.
- Auto memory remains useful within its first 200 lines or 25KB.
- Each
CLAUDE.mdstays below the 200-line target unless a documented reason justifies an exception. - Commands, paths, and file patterns are audited after project changes.
- Contradictions are removed rather than left for Claude to resolve.
- Actions that must be blocked are enforced with a
PreToolUsehook.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
