[Перевод] Что вы не знали о Claude Code: архитектура, управление и инженерные практики

Сегодняшняя статья основана на полугодовом опыте глубокого использования Claude Code и кучи набитых шишек. Надеюсь, это будет полезно. Поначалу я использовал его как обычный чат-бот, но довольно быстро понял, что что-то идёт не так: контекст становился всё более хаотичным, инструментов становилось всё больше, но эффективность только падала, правила становились всё длиннее, но соблюдались всё реже. После некоторого времени ковыряния и изучения самого Claude Code я осознал – это не проблема промптов, а особенность архитектуры самой системы. В этой статье я хочу обсудить несколько вещей: как Claude Code работает изнутри, почему контекст засоряется и как с этим бороться, как правильно проектировать Skills и Hooks, как правильно использовать Subagents, как архитектура Prompt Caching влияет на всё, и как написать действительно полезный CLAUDE.md.

https://habr.com/ru/articles/1012412/

#ии #claudecode #anthropic #claude #hooks #skills #mcp #claudemd

Что вы не знали о Claude Code: архитектура, управление и инженерные практики

Обложка *Это перевод статьи разработчика нескольких мега-популярных инструментов - https://github.com/tw93 . Она была опубликовала в твиттере на китайском языке, потом криво переведена на английский,...

Хабр

Tibo (@thsottiaux)

Codex에 'hooks' 기능 도입이 예고된 짧은 발표 트윗입니다. 코드 생성/보조 모델인 Codex에 훅(Hooks) 지원이 추가된다는 소식으로, 플러그인·확장성 또는 외부 툴 연동에 영향을 줄 가능성이 있어 개발자 관점에서 주목할 만합니다.

https://x.com/thsottiaux/status/2031982340826910812

#codex #hooks #openai #ai

Tibo (@thsottiaux) on X

Hooks are coming to codex. That’s all I wanted to say.

X (formerly Twitter)

[Claude Code, HTTP Hook 기능 추가

Claude Code는 HTTP Hook 기능을 추가하여, 이벤트를 URL에 전송하고 응답을 기다리는 방식으로 더 사용하기 쉽고 안전한 훅 이벤트 처리를 제공합니다. 이를 통해 웹앱을 구축하거나 로컬호스트에서도 상태 관리 및 권한 관리가 가능해졌습니다.

https://news.hada.io/topic?id=27219

#claude #http #hooks #webapp #api

Claude Code, HTTP Hook 기능 추가

<ul> <li>기존의 <strong>코맨드 훅</strong>보다 더 사용하기 쉽고 안전함</li> <li>클로드 코드가 훅 이벤트를 URL에 전송하고 답변을 기다리는 ...

GeekNews
【完全版活用ガイド】Claude Code拡張機能の全体像を知る - Qiita

はじめに Claude Codeは対話するだけでも十分に使える。しかし5つの拡張機能を使いこなすと、開発の質と速度が段違いに変わる。この記事では、CLAUDE.md / Skills / Subagents / Hooks / MCP Serversの5機能を、設計意図か...

Qiita

Not my post but worth reading...

pre-commit hooks are fundamentally broken

https://jyn.dev/pre-commit-hooks-are-fundamentally-broken/

Note that the pre-commit framework can also be used to manage pre-push and other hooks

#git #precommit #hooks

pre-commit hooks are fundamentally broken

use pre-push hooks instead

Ivan Leo (@ivanleomk)

OpenAI Codex GitHub 토론 링크를 공유하며 'codex hooks'에 대한 업데이트를 문의하는 트윗입니다. 작성자는 'agent traces' 관련 아이디어가 있어 시도해보고 싶다고 밝혔고, @thsottiaux를 멘션했습니다.

https://x.com/ivanleomk/status/2021577254195601674

#codex #openai #hooks #developertools

Ivan Leo (@ivanleomk) on X

https://t.co/KyKdrSOJsS any updates here on codex hooks? Have an idea around agent traces that I'd love to try @thsottiaux :)

X (formerly Twitter)

Instagram Algorithm is a whole new game! 📲⚡

If you’re still stuck guessing what works and what doesn’t — it’s time to stop playing blind.
The rules have changed, and so should your strategy!

👉 New keywords
👉 Smart storytelling
👉 Visual hooks
👉 Audience-first content

#instagram #keywords #storytelling #visual #hooks #marketing

Update zu meinem Blogeintrag „Zweiseitiger Druck in LaTeX & PDF“:
Abschnitt zu Hooks ergänzt + Doku-Link

Hinweis stammt von Marei (@TeXhackse)

Blogeintrag: https://404lifenotfound.freeddns.org/posts/pdf-zweiseitig/

Siehe ursprünglicher Post hier: https://wien.rocks/@sheeptastic/115853403415342083

#TeXLaTeX #PDF #Hooks #LaTeXTips #OpenSource #pdfarranger #Studium #Schule #Abschlussarbeit

Zweiseitiger Druck in LaTeX & PDF: Kapitelanfänge richtig platzieren

Bei der Druckvorbereitung meiner Abschlussarbeit für den zweiseitigen Druck kam es zu einem typischen Layoutproblem: Zwei von fünf Kapiteln begannen auf der linken, also geraden Seite, obwohl Kapitelanfänge im Buchdruck üblicherweise auf der rechten, also ungeraden Seite stehen sollten. Ich hatte dem Mitarbeiter im Copyshop genau angegeben, welche Teile meiner Arbeit auf der rechten Seite beginnen sollten. Die Frontmatter, also Declaration of Authorship, Acknowledgements, Abstract, Contents, List of Figures, Bibliography sowie die Anhänge Appendix A, B und C, wurden korrekt rechts platziert. Auch der Hauptteil begann auf der richtigen Seite.

404 life not found
https://dev.to/usama_dev/react-hooks-and-the-rules-of-hooks-the-understanding-that-finally-clicked-for-me-hm4 - #React #Hooks are an ordered list of references into their internals. So defining them conditionally breaks the order. Or defining them outside React functions means they never tie to React internals. Brilliant observation https://github.com/Usamaazeem03.
React Hooks and the Rules of Hooks – The Understanding That Finally Clicked for Me

Today, something finally clicked for me. I had been using React Hooks for a long time, but if I’m...

DEV Community

Lean4 proof that SSOT requires definition-time hooks and introspection

https://zenodo.org/records/18177320

#HackerNews #Lean4 #SSOT #proof #definition-time #hooks #introspection #Zenodo

Formal Foundations for the Single Source of Truth Principle

Any system encoding facts faces a fundamental constraint: when multiple independent locations encode the same fact, truth becomes indeterminate. We prove that DOF = 1 (Single Source of Truth) is the unique representation guaranteeing coherence, the impossibility of disagreement among encodings. The Core Theorem (Oracle Arbitrariness). In any incoherent encoding system (DOF > 1 with divergent values), no resolution is principled: for ANY oracle claiming to identify the "true" value, there exists an equally-present value that disagrees. This is not about inconvenience. It is about the determinacy of truth. Programming languages instantiate this epistemic structure: encoding systems become codebases, facts become structural specifications (class existence, method signatures), coherence becomes consistency across encoding locations, and DOF = 1 becomes the Single Source of Truth (DRY principle). Encoding systems → CodebasesFacts → Structural specifications (class existence, method signatures)Coherence → Consistency across encoding locationsDOF = 1 → Single Source of Truth (DRY principle)We prove that achieving DOF = 1 for structural facts requires specific language features: definition-time hooks AND introspectable derivation. Most mainstream languages (Java, C++, Rust, Go, TypeScript, etc.) lack these features and cannot achieve coherence for structural facts regardless of programmer effort. Four Theorems: Coherence Forcing: DOF = 1 is the unique value guaranteeing coherence. DOF = 0 means the fact is unrepresented; DOF > 1 permits incoherent states.Oracle Arbitrariness: Under incoherence, any resolution is arbitrary, no oracle is justified by the encodings alone.Language Requirements: For structural facts in software, DOF = 1 requires definition-time hooks AND introspection. These are logically forced.Strict Dominance: The coherence restoration complexity gap is unbounded: O(1) vs Ω(n).Theoretical Foundation. The derivation theory (independence, derivability, axis collapse) is established in previous work (https://zenodo.org/records/18123532). This paper proves the coherence consequences and instantiates them to programming languages. All theorems machine-checked in Lean 4 (2,104 lines, 119 theorems). Practical demonstration via OpenHCS PR #44: migration from 47 scattered checks to 1 ABC (DOF 47 → 1).

Zenodo