Artículos Relacionados con CLAUDE.md

El Centro de Noticias de HTX ofrece los artículos más recientes y un análisis profundo sobre "CLAUDE.md", cubriendo tendencias del mercado, actualizaciones de proyectos, desarrollos tecnológicos y políticas regulatorias en la industria de cripto.

This is How God Karpathy Uses Claude?

Andrej Karpathy, a prominent figure in AI, has reportedly joined Anthropic, leading to a noticeable decrease in his open-source contributions and social media activity. A document claiming to be his personal "CLAUDE.md" file—a set of instructions for the Claude AI to follow within a specific codebase—has been circulating online. While its authenticity is unverified, the content aligns closely with Karpathy's publicly shared principles on effective AI-assisted programming. The document outlines key rules for AI coding assistants, emphasizing the importance of reading existing code thoroughly before writing new code to maintain consistency. It advises against over-engineering, advocating for simple, surgical modifications that match the project's existing style. Other guidelines include clarifying assumptions upfront, writing meaningful tests, thoughtful debugging, and carefully considering dependencies. The core message is that these principles help prevent common AI coding failures, such as introducing unnecessary abstractions, style drift, or making invisible architectural decisions. The community has noted that even experts like Karpathy require detailed instructions to guide AI effectively, akin to managing a junior developer. A related GitHub repository, "andrej-karpathy-skills," which encapsulates these ideas, is reported to significantly reduce Claude's code error rate. Ultimately, the advice stresses that the best CLAUDE.md is tailored to one's own tech stack and coding practices.

marsbit06/27 07:32

This is How God Karpathy Uses Claude?

marsbit06/27 07:32

Topping GitHub's Trending, the Essential Guide for Claude Code Users

The CLAUDE.md file, trending on GitHub, is a project-level guide for Claude Code designed to dramatically improve its accuracy and efficiency. It addresses key issues like repetitive context explanations, unauthorized code changes, and forgotten decisions across sessions. By placing this plain-text file in a project root, Claude Code reads it automatically at the start of each session. The guide includes rules to eliminate redundant explanations, enforce strict behavioral constraints (e.g., no modifications outside the requested scope without confirmation), and establish a "memory" system using companion files like MEMORY.md and ERRORS.md to log past decisions and failures. It also locks in the project's specific tech stack to prevent inappropriate tool recommendations. Highlighted are four foundational rules from Andrej Karpathy that reportedly increased coding accuracy from 65% to 94%: always ask for clarity first, implement the simplest solution, never touch unrelated code, and explicitly flag uncertainties. The article quantifies significant weekly cost savings for developers and teams by eliminating wasted time on re-explaining context, rolling back unauthorized edits, and re-evaluating previously rejected solutions. The core message is that a small, upfront investment in creating a CLAUDE.md file leads to a more predictable, controlled, and cost-effective AI programming assistant.

marsbit05/18 09:38

Topping GitHub's Trending, the Essential Guide for Claude Code Users

marsbit05/18 09:38

Claude always makes mistakes in writing code? These 12 rules reduce the error rate to 3%

Claude's Coding Errors Drop to 3% with 12 Key Rules In early 2026, Andrej Karpathy's critique of Claude's coding failures led to the creation of a CLAUDE.md file with 4 foundational rules: "Think before coding," "Prefer simplicity," "Make surgical edits," and "Execute goal-first." These effectively reduced common errors from 40% to 3% in applicable tasks. However, as Claude Code evolved into multi-step agent workflows by May 2026, new failure modes emerged. Eight additional rules were developed to address these gaps: 5. Don't make non-linguistic decisions (e.g., API retry logic). 6. Set hard token budgets to prevent runaway iterations. 7. Expose conflicts; don't average contradictory code patterns. 8. Read existing code before writing to avoid duplication. 9. Ensure tests validate real logic, not just pass. 10. Use checkpoints for long-running, multi-step tasks. 11. Follow existing conventions over introducing new patterns. 12. Fail explicitly; avoid silent failures that appear successful. Testing across 30 codebases showed the 12-rule version maintained a 76% adherence rate while reducing the overall error rate to 3%, covering new agent-specific issues. The key is to treat CLAUDE.md as a behavioral contract targeting observed failures, keeping it under 200 lines for effectiveness. Users should adapt the rules to their specific workflows.

marsbit05/14 10:07

Claude always makes mistakes in writing code? These 12 rules reduce the error rate to 3%

marsbit05/14 10:07

活动图片

Ethereumright-arrow

Othersright-arrow