stick-around
CLAUDE.md1 starsChanged 3 months agoMITView on GitHub
After code changes, run make dev (builds the Tauri binary and installs it to the plugin cache used by the /stick-around:play skill). Plain npm run build / tauri build alone does not copy the binary to the launcher path — relaunches will still run the stale build. Prefer straightforward control flow. Keep error paths obvious and localized. Do not add interfaces, config keys, or abstractions without a concrete caller. No speculative features. Duplicate small local logic when it preserves clarity.…
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
After code changes, run make dev (builds the Tauri binary and installs it to the plugin cache used by the /stick-around:play skill).
- Distinctive: line 26
Prefer straightforward control flow.
- Distinctive: line 30
Do not add interfaces, config keys, or abstractions without a concrete caller.
- Very specific: line 38
Never log secrets or tokens.
- Distinctive: line 42
Write tests first. Red → Green → Refactor.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
stick-around
Applying changes
After code changes, run make dev (builds the Tauri binary and installs
it to the plugin cache used by the /stick-around:play skill). Plain
npm run build / tauri build alone does not copy the binary to the
launcher path — relaunches will still run the stale build.
Universal Rules
- Strict TypeScript — No
any, no// @ts-ignore, noas unknown as. Fix type errors, don't suppress them. - Read before editing — Understand existing code before modifying it.
- Match existing patterns — Follow the conventions already established in each project.
- Test your changes — Run typecheck and tests relevant to your changes.
- Git: Conventional commits (
feat:,fix:,chore:,refactor:,test:,ci:). IMPORTANT: No Co-Authored-By trailer. No "Generated with Claude Code" footer in PR descriptions.
Engineering Principles
KISS
Prefer straightforward control flow. Keep error paths obvious and localized.
YAGNI
Do not add interfaces, config keys, or abstractions without a concrete caller. No speculative features.
DRY (Rule of Three)
Duplicate small local logic when it preserves clarity. Extract shared helpers only after three repeated, stable patterns.
Secure by Default
Never log secrets or tokens. Validate at system boundaries. Keep network/filesystem/shell scope narrow.
TDD
Write tests first. Red → Green → Refactor. New features and bug fixes start with a failing test that defines the expected behavior before writing implementation code.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
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.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.