Recommended Free Tools
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
A good CLAUDE.md is a short, maintained briefing for Claude Code: the project map, commands, conventions, and completion checks you would otherwise repeat in every session. Put shared rules in the repository, keep personal preferences in user-level or local files, move path-specific guidance into .claude/rules/, and verify the result with /context or /memory.
The file supplies context rather than enforcing permissions. Anthropic’s documentation describes it plainly: “Claude treats them as context, not enforced configuration.” Write instructions that are specific and testable, keep the always-loaded file focused, and use hooks or other controls when an action must be blocked.
What a CLAUDE.md file is—and what it is not
Claude Code reads applicable memory and instruction files as it works in a repository. A project CLAUDE.md can explain architecture that is difficult to infer, the commands that maintainers actually run, naming and formatting conventions, and the checks that define a finished change. Its purpose is to prevent repeated corrections and make a new session start with the same durable project facts as an experienced contributor.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →It is not a schema that Claude Code validates, a policy engine, or a security boundary. Instructions can improve consistency, but they cannot guarantee that a prohibited tool call will never be attempted. Anthropic’s current Claude Code documentation recommends a PreToolUse hook when an operation must be blocked regardless of Claude’s decision. Treat CLAUDE.md as project context and pair it with permissions, hooks, CI, and repository protections where enforcement matters.
#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.
Choose the right location before writing rules
Place each instruction where its intended audience can maintain it. Claude Code loads applicable files in the directory hierarchy above the working directory when it starts, and files in subdirectories become relevant when work reaches those directories. That lets a repository have broad guidance plus narrower instructions without putting every detail into one global document.
| Location | Audience and scope | Typical contents | Version-control treatment |
|---|---|---|---|
./CLAUDE.md or ./.claude/CLAUDE.md |
Everyone working on the repository | Project map, architecture decisions, shared commands, conventions, and definition of done | Normally commit to source control |
~/.claude/CLAUDE.md |
One developer across projects | Personal preferences that should apply broadly | Keep in the developer’s home configuration |
./CLAUDE.local.md |
One developer in one project | Private, project-specific reminders or local environment details | Keep out of source control |
.claude/rules/ |
Teams that need modular or path-specific guidance | Testing, API design, frontend conventions, or rules selected by file paths | Commit shared rule files; exclude private ones as appropriate |
Use the repository file for facts that another contributor should see. Do not put credentials, tokens, or machine-specific secrets in any instruction file. A local file is useful for personal setup notes, but it should not become the only place a required team workflow is documented.
Start from the repository, not from guesses
Every instruction should describe a real characteristic of the codebase. Before editing the file, inspect the top-level directories, package or build manifests, test configuration, CI workflows, and existing contributor documentation. Record only conventions that the repository actually follows. A speculative rule is worse than no rule because it can steer an otherwise correct change in the wrong direction.
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 matchClaude Code’s /init command can generate a starting CLAUDE.md by analyzing the codebase. Its output may include build commands, test instructions, and conventions it discovers. Treat that output as a draft: check every command, remove assumptions, and add details Claude cannot reliably discover, such as a deployment constraint, a compatibility promise, or the reason behind an unusual directory.
/initA practical first pass is to write down the answers to these questions:
- What does this product or service do, and which directories contain its major parts?
- Which command builds it, which command runs the test suite, and which command runs linting or type checks?
- Where do API handlers, database migrations, UI components, background jobs, and shared libraries live?
- Which naming, formatting, error-handling, and dependency patterns are consistently used?
- What checks must pass before a change is considered complete?
- Which decisions are intentional but difficult to infer from the source?
Use a compact structure that agents can scan
Headings and bullets make rules easy to locate. A maintainable starting file can look like this:
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
# Project instructions
## Project map
- [Short description of the product]
- [Important directories and architecture decisions]
## Commands
- Build: `[actual build command]`
- Test: `[actual test command]`
- Lint: `[actual lint command]`
## Conventions
- [Specific naming and formatting rules]
- [Patterns this codebase consistently uses]
## Workflow
- [Checks required before a change is complete]
- [Review, migration, or release steps]Replace every bracketed item with a repository fact; do not leave template markers in the committed file. Keep related requirements together under short headings. A rule should answer what to do, where to do it, or how to verify it. For example, an API section might identify the handler directory, the response type used for validation failures, and the test command for that layer.
Turn vague preferences into instructions that can be checked
Claude Code follows a rule more consistently when the rule names an action and a scope. Anthropic’s documentation says, “The more specific and concise your instructions, the more consistently Claude follows them.” The following transformations illustrate the difference:
| Weak wording | Actionable wording | Why the second works better |
|---|---|---|
| Format code properly. | Use 2-space indentation in JavaScript and TypeScript files. | It names the action, language, and measurable style. |
| Keep files organized. | API handlers live in src/api/handlers/. |
It identifies the expected location. |
| Test your changes. | Run npm test before committing. |
It supplies an exact command and a point in the workflow. |
| Use the usual error handling. | Return the repository’s typed error response from API handlers; do not throw raw strings. | It describes the established pattern and a concrete prohibition. |
Use the real command and path names for your repository. If a check is expensive, state when it is required and whether a narrower command is acceptable during iteration. If a migration must precede application tests, put those steps in order rather than assuming Claude will infer the dependency.
Document architecture that source code cannot explain quickly
Include a short map of major components and the boundaries between them. Explain an intentional constraint such as “the worker reads from the queue but never writes to the primary database,” or “shared DTOs are generated and must not be edited by hand.” These statements prevent an agent from applying a locally plausible change that violates a system-wide design.
Document conventions with examples of locations
Say where a new file belongs, which existing pattern it should copy, and which layer owns a decision. “Put React components in src/components and co-locate their tests” is more useful than “follow frontend conventions.” Keep examples short; the instruction should remain true as the codebase grows.
Define completion as a sequence
List the checks in the order maintainers expect: generate code if required, run focused tests, run the full suite, run lint or type checks, and update a migration or documentation file when applicable. This turns “done” into a repeatable workflow rather than an aspiration.
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.
Keep the always-loaded file short
Anthropic recommends targeting fewer than 200 lines per CLAUDE.md file. This is product guidance, not a measured study result. Concise instructions leave more context available for the task and reduce the chance that important rules are lost among marginal notes. Making the file longer does not inherently improve results.
When the project grows, do not solve every new case by appending another paragraph to the root file. Move guidance to a narrower location when its scope permits:
- Put testing commands and test conventions in a testing rule file.
- Put API-specific response and authentication rules in an API rule file.
- Put frontend or database conventions in files that apply only to those paths.
- Keep the root file for facts that are relevant to nearly every task.
Imported files can improve organization, but they still consume context if they load. The separate auto-memory behavior documented by Anthropic loads up to its first 200 lines or 25 KB; that limit describes auto-memory loading, not a recommended length for CLAUDE.md. Do not use the two numbers interchangeably.
Use .claude/rules/ for modular and path-specific guidance
Create one rule file per coherent topic, such as .claude/rules/testing.md or .claude/rules/api-design.md. A rule without a paths field loads unconditionally. Add YAML frontmatter when the rule should activate only for matching files:
---
paths:
- "src/api/**/*.ts"
- "tests/api/**/*.ts"
---
# API rules
- Keep handlers in `src/api/handlers/`.
- Return the shared typed error response.
- Run the focused API test command after changes.Path-scoped rules keep unrelated work from carrying instructions it does not need. Review nested CLAUDE.md files and rule files periodically for contradictions. If two files give different commands or styles for the same path, consolidate the decision or make the scope explicit instead of expecting Claude to resolve the conflict correctly every time.
Use imports when ownership or organization calls for them
A CLAUDE.md file can include another file with @path/to/file syntax. Relative and absolute paths are supported, and imports may nest up to five levels. Imports inside Markdown code blocks are not interpreted as imports, so examples can safely show the syntax without loading the referenced file.
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.
# Project instructions
@docs/architecture.md
@.claude/rules/testing.mdUse an import when a separate file has a clear owner or is useful on its own—for example, a maintained architecture note or a test workflow shared by several entry points. Do not split a short file into many fragments merely to reduce its visible line count. The imported content still contributes to the context Claude receives, so organization and context cost must be considered together.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Understand loading and confirm what Claude actually saw
Applicable instruction files are discovered from the directory hierarchy above the working directory at launch. As work reaches a subdirectory, instructions located there can become relevant. This means a session started at the repository root may have broad project guidance first, while a task in a nested package can acquire additional local rules.
Do not rely on a mental model of the hierarchy. In Claude Code, use /context to inspect the context currently loaded and /memory where appropriate to inspect memory information. Confirm that the expected project file, local file, and relevant rule files appear. If a rule is missing, check the working directory, filename, directory placement, frontmatter paths, and whether the task has reached the directory where the rule applies.
/context
/memoryWhen a rule seems ignored
- Confirm the file is named exactly
CLAUDE.mdor is in the intended.claude/rules/directory. - Confirm Claude Code started in the repository or another directory whose hierarchy includes the file.
- For a path-scoped rule, compare the frontmatter pattern with the actual files being edited.
- Check for a nested instruction that conflicts with the broader rule.
- Inspect
/contextand/memoryinstead of assuming the file loaded. - Rewrite the rule as a specific action with a command, path, or check if the loaded instruction is still too vague.
Separate guidance from enforcement
A sentence such as “never run this destructive command” expresses an intention, but it is not a guaranteed block. Claude Code’s documentation distinguishes contextual instructions from enforced configuration. If a tool action must be denied, use an appropriate permission setting or a PreToolUse hook, and keep the contextual explanation in CLAUDE.md so the agent understands the safe workflow.
This separation also clarifies what belongs in the file. Explain why a command is dangerous, which safer alternative to use, and which approval or review step is required. Let the enforcement mechanism make the final decision. CI should remain the authority for tests, linting, security checks, and deployment gates; a Markdown instruction should tell Claude how to reach those gates, not replace them.
Free tools Windows power users keep installed
One-click scans. No signup required.
A complete authoring workflow
- Inventory the repository. Identify the actual build, test, lint, generation, migration, and release commands, plus the directories that define the architecture.
- Generate or draft a small root file. Use
/initfor a starting point if helpful, then remove guesses and write only durable project facts. - Add the project map. Explain the product in a few lines and name the important directories and boundaries.
- Add commands. Give exact commands and note prerequisites or ordering when one check depends on another.
- Add conventions. State naming, formatting, API, testing, dependency, and generated-file rules that the repository consistently follows.
- Add the completion workflow. Define the checks required before a change is ready for review or commit.
- Move narrow rules out of the root. Create topic files or path-scoped rules under
.claude/rules/when guidance is not universal. - Review for contradictions. Search nested files and imports for older wording, duplicate commands, and incompatible requirements.
- Verify loading. Start Claude Code from the intended directory and inspect
/contextor/memory. - Maintain from real corrections. Add a rule after a repeated mistake or recurring correction, and remove rules that no longer describe the codebase.
Common failure modes and fixes
The file is a wall of background information
Long historical explanations consume context without telling Claude what to do. Keep a short rationale only when it changes a decision; move detailed history to normal project documentation and link to it internally by path or import when needed.
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 instructions describe ideals rather than repository behavior
“Use clean architecture” cannot be checked without a definition. Replace it with the actual layer boundaries, allowed dependencies, and test command. If the project has exceptions, state the exception and its scope.
The root file contains every specialized rule
Move rules for a single package or file type into path-scoped files. This reduces irrelevant context and gives the team a clear owner for each topic.
Imports are used as a line-count trick
Splitting a document does not eliminate context cost. Import only material that should load together; use path-scoped rules when the material is relevant only to particular files.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A local preference is committed accidentally
Keep personal project instructions in CLAUDE.local.md and exclude that file from source control. Shared requirements belong in the tracked project file or tracked rules directory.
A rule conflicts with a nearer rule
Inspect the directory hierarchy and nested files. Decide which instruction should own the behavior, remove the duplicate, and make any remaining scope explicit in headings or frontmatter.
The team expects a Markdown file to provide security
Move the security requirement to permissions, hooks, CI, or another control that can enforce it. Keep CLAUDE.md as the explanation of the safe process and the commands Claude should use.
How to keep the file useful over time
Review the file when commands, directory ownership, build tools, or architectural boundaries change. Treat repeated human corrections as maintenance signals: if several sessions require the same reminder, add a concise rule in the narrowest location that applies. If a rule is never relevant, conflicts with current practice, or merely restates a tool’s default behavior, remove it.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsAsk reviewers to check instruction changes with the same care as code changes. A changed test command can make every future session fail; a broadened path pattern can load an API rule into unrelated work. Keep ownership visible through headings and filenames, and verify the loaded result after reorganizing files.
What a strong result looks like
When Claude Code opens a task, it should be able to answer four questions without asking you to repeat yourself: what this repository contains, which commands prove a change works, which patterns the codebase expects, and what steps make the work complete. A root CLAUDE.md under 200 lines, supported by focused rules and verified with /context, is usually a better operating manual than a long catalog of aspirations. Keep enforcement in the mechanisms designed for enforcement, and let the Markdown file provide the durable context that helps the agent make the right choices.
Quick Recap
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.
