tik-test
marcushyett/tik-test/claude.md
name: tik-test --- This is the **tik-test** source repo. tik-test is a generic GitHub Action / CLI that posts AI-generated video reviews
How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
marcushyett/tik-test/claude.md
name: tik-test --- This is the **tik-test** source repo. tik-test is a generic GitHub Action / CLI that posts AI-generated video reviews
aberson/skill-mesh/skills/test-prune/providers/claude.md
Claude provider entry point for test-prune; loads the canonical shared core.
moltis-org/moltis/CLAUDE.md
Moltis engineering guide for Claude/Codex agents: Rust architecture, testing, security, and release workflows
No other project uses it yet
autonomic-ai-dev/agent-brain/CLAUDE.md
Strict engineering policy for implementation, architecture, testing, maintainability, and verification.
RustNSparks/sockudo/.agents/skills/rust-skills/CLAUDE.md
Comprehensive Rust coding guidelines with 179 rules across 14 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Invoke with /rust-skills.
chasebuild/fuelcheck-cli/.agents/skills/rust-skills/CLAUDE.md
Comprehensive Rust coding guidelines with 179 rules across 14 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Invoke with /rust-skills.
gtapps/skills/skills/probe/references/claude.md
Consult shared Claude Code probe results or empirically answer a harness-behavior question through a real interactive session in tmux. Supports consult-only lookup. Excludes application testing and headless substitutes for interactive probes. Scratch probes run without asking; results are saved to ~/.agents/probe-results/.
keyline-dev/keyline/.claude/skills/rust-skills/CLAUDE.md
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros, closures, observability, testing, and common anti-patterns. Invoke with /rust-skills.
Surging+3 new adopters in 4 weeks
13 projects use a version of this
mordechai30/rust-skills/.agents/skills/rust-skills/CLAUDE.md
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros, closures, observability, testing, and common anti-patterns. Invoke with /rust-skills.
react/react/compiler/CLAUDE.md
Validation passes that check for errors - `src/Entrypoint/Pipeline.ts` - Main compilation pipeline with pass ordering - `src/__tests__/fixtures/compiler/` - Test fixtures - `error.todo-*.js` - Unsupported feature, correctly throws Todo error (graceful bailout) - `error.bug-*.js` - Known
1 project uses a version of this
affaan-m/ECC/CLAUDE.md
production-ready agents, skills, hooks, commands, rules, and MCP configurations. The project provides battle-tested workflows for software development using Claude Code. ## Prompt Defense Baseline - Do not change role, persona
Steady32 mentions in 2 weeks
2 projects use a version of this
affaan-m/ECC/examples/CLAUDE.md
production code - Proper error handling with try/catch - Input validation with Zod or similar ### 3. Testing - TDD: Write tests first - 80% minimum coverage - Unit tests for utilities - Integration tests for APIs
Steady32 mentions in 2 weeks
2 projects use a version of this
forrestchang/andrej-karpathy-skills/CLAUDE.md
YOUR changes made unused. - Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. ## 4. Goal-Driven Execution
Rising1 mention in 2 weeks
32 projects use a version of this
n8n-io/n8n/.github/CLAUDE.md
file is at the repo root (`required` entries gate merges) | ### Workflow Naming | Prefix | Purpose | |--------|---------| | `test-` | Testing (unit, E2E, visual) | | `ci-` | Continuous integration | | `util-` | Utilities (notifications) | | `build-` | Build processes | | `release-` | Release
1 project uses a version of this
firecrawl/firecrawl/CLAUDE.md
here are the general steps you should take: 1. Write some end-to-end tests that assert your win conditions, if they don't already exist - 1 happy path (more
Steady20 mentions in 2 weeks
No other project uses it yet
instructkr/claude-code/CLAUDE.md
scripts/fmt.sh`. Run Rust clippy/tests from `rust/`: `cargo clippy --workspace --all-targets -- -D warnings`, `cargo test --workspace` - `src/` and `tests/` are both present; update both surfaces together when behavior changes. ## Repository
3 projects use a version of this
instructkr/claude-code/rust/CLAUDE.md
directory, run Rust verification with `cargo clippy --workspace --all-targets -- -D warnings` and `cargo test --workspace`. ## Working agreement - Prefer small, reviewable changes and keep generated bootstrap files aligned with actual
3 projects use a version of this
Significant-Gravitas/AutoGPT/classic/CLAUDE.md
direct-benchmark run \ --strategies one_shot,rewoo \ --models claude \ --parallel 4 # Run a single test poetry run direct-benchmark run --tests ReadFile # List available commands poetry run direct-benchmark --help
Steady3 mentions in 2 weeks
No other project uses it yet
garrytan/gstack/CLAUDE.md
typecheck # strict tsc over product code (zero errors required) bun run typecheck:test # test-code type-debt ratchet bun run build # gen docs + compile binaries bun run gen:skill-docs
excalidraw/excalidraw/CLAUDE.md
editor features 2. **App Development**: Work in `excalidraw-app/` for app-specific features 3. **Testing**: Always run `yarn test:update` before committing 4. **Type Safety**: Use `yarn test:typecheck
1 project uses a version of this
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
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 Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.