rules
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: rules
description: Generate auto-extraction rules for AI tools. Writes guidelines to CLAUDE.md, .cursorrules, etc.…
category: data
runtime: no special runtime
---
# rules output preview
## PART A: Task fit
- Use case: Generate auto-extraction rules for AI tools. Writes guidelines to CLAUDE.md, .cursorrules, etc. that teach the AI when and how to store memories. Use when the user wants to set up proactive memory extraction. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Instructions” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Generate auto-extraction rules for AI tools. Writes guidelines to CLAUDE.md, .cursorrules, etc. that teach the AI when and how to store memories. Use when the user wants to set up proactive memory extraction. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Instructions” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/amem`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Instructions”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: rules
description: Generate auto-extraction rules for AI tools. Writes guidelines to CLAUDE.md, .cursorrules, etc.…
category: data
source: tomevault-io/skills-registry
---
# rules
## When to use
- Generate auto-extraction rules for AI tools. Writes guidelines to CLAUDE.md, .cursorrules, etc. that teach the AI when…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Instructions” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "rules" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Instructions
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}/amem:rules — Generate Extraction Rules
Generate memory extraction guidelines for AI tools.
Instructions
Run via Bash:
amem-cli rulesIf
amem-cliis not on PATH, use:npx @aman_asmuei/amem rulesThis writes extraction rules to each tool's rules file:
- Claude Code:
CLAUDE.md - Cursor:
.cursorrules - Windsurf:
.windsurfrules - GitHub Copilot:
.github/copilot-instructions.md
- Claude Code:
To target a specific tool:
amem-cli rules --tool cursorTo write to a custom path:
amem-cli rules --path ./my-rules.md
Source: amanasmuei/amem — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review