rtk-ai/rtk

cluade.md bloat

Open

#598 opened on Mar 15, 2026

View on GitHub
 (1 comment) (2 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
documentationeffort-smallenhancementgood first issue

Description

First of all, well done and thanks! Second, for a project aiming to improve token spend - you bloat the claude.md in a terrible way without telling us. Why do we need there info on token consumption? Why the word Cargo needs to be added to my context for a js project? etc. It's like an hidden ad, not cool.

This is my summarized lines. I suggest you find the best 3-liner instead of the current bloat.

<!-- rtk-instructions -->
# RTK - Token-Optimized CLI Proxy (60-90% savings)
Always prefix ALL commands with `rtk` (e.g., `rtk git status`, `rtk pnpm install`, `rtk docker ps`). Works with git, gh, pnpm/npm/npx, docker, kubectl, curl, cargo, tsc, vitest, and more.
If RTK has a filter it compresses output; if not it passes through unchanged — so it's always safe to use. In command chains: `rtk git add . && rtk git commit -m "msg"`.
Meta commands: `rtk gain` (savings stats), `rtk discover` (find missed usage), `rtk proxy <cmd>` (bypass filtering for debug).
<!-- /rtk-instructions -->

And thanks again

Contributor guide

Tech stack
None
Domain
clideveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Investigate the current content of claude.md in the repository root. The issue reports that the file contains verbose instructions cluttering the AI context. Focus on the section between <! rtk instructions > and <! /rtk instructions >. The user suggests condensing it to a brief 3 liner that covers: always prefix commands with `rtk`, safe to use, and meta commands (`rtk gain`, `rtk discover`, `rtk proxy`). Ensure the markdown formatting is preserved and the change aligns with project goals of token optimization.