VS Code extension + CLI that watches Claude/Codex sessions, generates live AI commentary, and dispatches prompts to existing or new agent sessions. Distribution: VS Code Marketplace · npm · Homebrew Always include pros and cons for every significant decision — stack choices, logic approaches, architectural trade-offs. Applies to all non-trivial decisions where alternatives exist. If user accidentally types Cyrillic characters (wrong keyboard layout), convert to English QWERTY equivalent: - й→q, ц→w, у→e, к→r, е→t, н→y, г→u, ш→i, щ→o, з→p, ф→a,…
Tilus caches generated kernels. During development, set the cache directory via tilus.option.cache_dir("some-cache-dir") to inspect the generated source.cu files. drivers.py:build_program orchestrates the full compilation: 1. Verify — ir.tools.verify(prog) 2. Optimize (Tilus IR) — optimizeprogram applies getdefaultpasses() from transforms/init_.py 3. Lower to Hidet IR — backends.codegen.generateirmodule 4. Optimize (Hidet IR) — optimizeirmodule applies Hidet-level passes 5. Codegen — Emit CUDA C source 6. Compile — Build .so via nvcc
The current repository instructions are maintained in AGENTS.md. Read and follow that file as the single source of truth for project structure, tooling, testing, security, and Pane automation.
On the first message of a conversation, tell the user: "AI-Driven Development ON - Date: {currentdate}, TZ: {currenttimezone}." Project docs, memory, specs, and plans live in aidd_docs/. @aidddocs/memory/architecture.md @aidddocs/memory/backlog.md @aidddocs/memory/cli.md @aidddocs/memory/codebase-map.md @aidddocs/memory/coding-assertions.md @aidddocs/memory/deployment.md @aidddocs/memory/ecosystem.md @aidddocs/memory/project-brief.md @aidddocs/memory/testing.md @aidddocs/memory/vcs.md
On the first message of a conversation, tell the user: "AI-Driven Development ON - Date: {currentdate}, TZ: {currenttimezone}." Project docs, memory, specs, and plans live in aidd_docs/. @aidddocs/memory/architecture.md @aidddocs/memory/auth.md @aidddocs/memory/cli.md @aidddocs/memory/codebase-map.md @aidddocs/memory/coding-assertions.md @aidddocs/memory/deployment.md @aidddocs/memory/ecosystem.md @aidddocs/memory/project-brief.md @aidddocs/memory/telemetry.md @aidddocs/memory/testing.md @aidd_docs/memory/vcs.md
Semantic commit messages: label(scope): description Labels: fix, feat, chore, docs, test, devops Never add Co-Authored-By agents in commit message. Never add "Generated with" in commit message. Never add test plan to PR description. Keep PR description short — a few bullet points at most. Branch naming for issue fixes: fix-<issue-number> Never git push without an explicit instruction to push. Applies even when a PR is already open for the branch — additional commits are immediately visible to reviewers. Commit locally,…
IMPORTANT: Every change to this plugin MUST include updates to all three files: Before committing ANY changes: Workflow commands use workflows: prefix to avoid collisions with built-in commands: - /workflows:plan…
You are a senior software design consultant. You interview, you design, you produce a blueprint. You do not write application code. Last verified: 2026-07-27 Treat these as standing instruction, not a checklist you tick once. 1. Never generate a blueprint before the confirmation gate. The interview is mandatory. 2. Max 3 questions per message. Conversational, not an interrogation. 3. Be opinionated. Recommend ONE option with rationale. Never list five and ask the user to pick. 4. Detect the user's language…
Instructions for Claude Code (or any AI coding agent) in this repo. (AGENTS.md symlinks here.) This is the workspace map; per-crate detail lives in nested guides, auto-loaded when you touch their tree: What the guides hold. A nested CLAUDE.md says what its crate IS, plus the facts no single declaration can own: cross-file workflows, comment-less manifests, and directory-shape rules. Everything else a change needs — the constraint that looks like a bug, the WHY, the test that pins it —…
The landing page: a self-contained Astro static site (NOT Rust) → GitHub Pages. A consumer of the Rust workspace's outputs — version, rendered docs, demo media all flow in from outside site/. Parent guide: the workspace ../CLAUDE.md. Human detail: README.md. You are in the Astro consumer, not the Rust producer. Rust house rules (cargo/clippy, just preflight, the crate CI gates) do not apply to a site-only change. The gates here are just site-check (+ just site-fmt) and just site-e2e. astro…
This repo is a Claude Code plugin marketplace shipping a single plugin, BMAD Planning & Orchestrator — a harness for the BMAD Method focused on planning and orchestration only. There…
이 파일은 매 세션 전문이 로드된다. 그래서 여기엔 항상 적용되는 규칙만 둔다. 길고 상황별인 절차는 docs/reference/ 로 내리고 아래 인덱스에서 "언제 읽는가"로 가리킨다. 새 규칙을 더할 때도 같은 기준으로 배치한다 — 항상 적용이면 여기, 특정 작업 때만이면 참조 문서. 각 문서의 frontmatter(summary/read_when)가 그 문서의 적용 범위를 다시 명시한다. 외부 컨트리뷰션을 받을 수 있도록 이 저장소는 영어를 first language 로 한다. - PR 제목·본문은 영어만. 한국어로 지시받아도(예: "PR 올려줘") PR 산출물은 영어로 작성한다. 기존 git log(한국어)를 모방하려는 커밋 컨벤션 자동 감지보다…
Director is an MCP gateway. It allows users to create and manage multiple playbooks. Each playbook aggregates MCP servers and prompts. We've just migrated director from a single tenant, local…
The rules above are shared with Codex and are the single source of truth. Do not restate or paraphrase them here — a second copy drifts, and the two agents then work from different instructions. Repo rules go in AGENTS.md; only the Claude-specific handoff rules below belong in this file. This repo is edited by both Codex and Claude, sometimes on the same day. - Before starting, read the newest handoffs/_registry.md entry and check its Owner and Branch. - If…
AI entry for this repo. Human workflow, evidence rules, and the docs map live in CONTRIBUTING.md and Docs/README.md. Change the authoritative topic doc in the same patch as the code; do not grow this file. Pulse is a macOS menu-bar usage monitor. SwiftUI draws the panel; a transparent, non-activating AppKit NSPanel owns size, placement, and input. Seventy-seven providers, no Pulse backend, no Pulse account. Per-provider routes, auth, cookies, and extra logins: Docs/providers/README.md. Sources sit in six directories under Sources/Pulse: App…
For this repository, AGENTS.md is the root engineering contract. Read it before any code change. The long-form rationale and historical failure map live in docs/engineering-invariants.md. When swarm mode is enabled, AGENTS.md still applies; swarm-mode instructions add workflow structure, not exceptions to the engineering invariants. Normal behavior is the default. If .claude/session/swarm-mode.md exists, swarm mode is enabled for the current session and you must read that file before starting complex work. When swarm mode is enabled: - Quality is the only…
Read this first if someone pointed you at GrayMatter. Three situations, three different answers. GrayMatter is a single-binary Go memory system for AI agents. Library + CLI + MCP server + TUI. Facts persist to bbolt with optional vector embeddings, for roughly a 90% cut in context tokens versus re-injecting full history — the figure go run ./benchmarks/token_count actually prints at 100 sessions. Do not read the source for this. Follow Agent setup procedure in the README: install the binary,…
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
kibitzshCLAUDE.md
