cursor rules compiler

AI Community

Skill notes

Follow prompts/161_cursor_advanced_rules_prompt.md.

Rules:

Inspect the repository first. - Keep always-on rules short. - Use globs for file-specific conventions. - Put long context in docs/ai/* and reference it. - Add secret, Git, validation, and execution guardrails. - Avoid duplicate AGENTS.md and Cursor rule content unless deliberately needed.

--- > Source: cembasaranoglu/crafting-system-claude — distributed by TomeVault.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Cursor Rules Compiler

Use when creating Cursor project rules, AGENTS.md, or AI-ready repository context.

Follow `prompts/161_cursor_advanced_rules_prompt.md`.

Rules:

- Inspect the repository first.
- Keep always-on rules short.
- Use globs for file-specific conventions.
- Put long context in `docs/ai/*` and reference it.
- Add secret, Git, validation, and execution guardrails.
- Avoid duplicate AGENTS.md and Cursor rule content unless deliberately needed.

---
> Source: [cembasaranoglu/crafting-system-claude](https://github.com/cembasaranoglu/crafting-system-claude) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.