last30flames
CLAUDE.md38 starsChanged 4 months agoMITView on GitHub
This project must only gather data through: Never add sources that scrape or access Reddit, X/Twitter, TikTok, Instagram, or any platform behind a login, cookie, or whose Terms of Service such access may violate. If a proposed feature needs such a source, the answer is no - reframe it around Firecrawl search of the open web instead. This rule is also stated in skills/last30flames/SKILL.md (the runtime copy) - keep the two in sync if either changes. New features must preserve…
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Never add sources that scrape or access Reddit, X/Twitter, TikTok, Instagram, or any platform behind a login, cookie, or whose Terms of …
- Very specific: line 11
If a proposed feature needs such a source, the answer is no - reframe it around Firecrawl search of the open web instead.
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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
last30flames - project constraints
Data sources (hard rule)
This project must only gather data through:
- The Firecrawl CLI (web search + full-page content).
- Open, public APIs that publish engagement numbers openly and permit this use, currently the Hacker News Algolia API, the Lobste.rs JSON feeds, the Bluesky AT Protocol API, and the official GitHub API.
Never add sources that scrape or access Reddit, X/Twitter, TikTok, Instagram, or any platform behind a login, cookie, or whose Terms of Service such access may violate.
If a proposed feature needs such a source, the answer is no - reframe it around Firecrawl search of the open web instead.
This rule is also stated in skills/last30flames/SKILL.md (the runtime copy) - keep the two in sync if either changes.
Design constraints
New features must preserve the design principles in the README: keyless by default (keys only raise rate limits), no LLM calls in the engine (the agent harness does the synthesis), and no harness-specific assumptions.
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.