bestax / bulma-ui
llms.txt14 starsChanged 8 days agoMITView on GitHub
React components for Bulma v1. Supply-chain posture — same claims as the package README; every item is verifiable: Full detail: https://github.com/allxsmith/bestax/blob/main/SECURITY.md · https://bestax.io/docs/guides/security
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bulma-ui/AGENTS.mdAGENTS.md
- bestax-mcp/CLAUDE.mdCLAUDE.md
- bestax-migrate/CLAUDE.mdCLAUDE.md
- bulma-ui/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- create-bestax/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- eslint-plugin/CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- skills/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- bestax-custom-componentSkill
- bestax-formSkill
- bestax-iconsSkill
- bestax-layout-scaffoldSkill
- bestax-migrateSkill
- bestax-optimizeSkill
- bestax-themingSkill
The file
We split this llms.txt into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Every GitHub Action pinned to a full commit SHA
≈ “Common” is an estimate: at least 1 in 5 of the 3,727 llms.txt 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
# @allxsmith/bestax-bulma React components for Bulma v1. - Docs index: https://bestax.io/llms.txt - Full docs (one file): https://bestax.io/llms-full.txt - Any docs page as markdown: append .md (e.g. https://bestax.io/docs/api/elements/button.md) - LLM guide: https://bestax.io/docs/guides/llms - Agent skills: https://bestax.io/docs/skills/intro - MCP server: `npx bestax-mcp` — setup at https://bestax.io/docs/guides/llms#mcp-server Supply-chain posture — same claims as the package README; every item is verifiable: - Signed provenance on every release (sigstore; check `npm audit signatures` or the npm Provenance section) - npm OIDC trusted publishing — no long-lived `NPM_TOKEN`; release commits and tags are GPG-signed - Socket.dev scans every PR for malware, install scripts, obfuscated code, and privilege escalation - Install scripts blocked unless allow-listed; versions younger than 3 days will not install - Every GitHub Action pinned to a full commit SHA - CodeQL, Dependency Review, Dependabot, and a high-severity `pnpm audit` gate - Layered AI review (CodeRabbit + an independent adversarial Claude review) plus required green CI, an approving review, and a human merge Full detail: https://github.com/allxsmith/bestax/blob/main/SECURITY.md · https://bestax.io/docs/guides/security
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.

