dyolink/.cursor/skills/capture-convention/SKILL.md

name, description

name	description
dyolink-capture-convention	Saves a new Dyolink project convention into AGENTS.md, .cursor/rules, or .cursor/skills. Use when the user says remember this, save as convention, add to project rules, document for future agents, or asks to update agent docs after a task.

Capture convention

Persist a durable project pattern so the next agent chat knows it without re-explaining.

Trigger phrases

• "Remember this"
• "Save as convention" / "Add to project rules"
• "Document this for future agents"
• "Update the cursor rules/skills"

Workflow

1. Confirm it is durable — not a one-off fix. If unclear, ask: "Should every future agent follow this?"
2. Choose target:
   • Short rule (always or file-scoped) → .cursor/rules/{topic}.mdc
   • Step-by-step process → .cursor/skills/{name}/SKILL.md (new folder if needed)
   • High-level pointer only → one line in AGENTS.md linking to the rule/skill
3. Write concisely — bullets, one example, under 50 lines per rule file.
4. Avoid duplication — merge into an existing rule if the topic fits.
5. Commit with the feature — remind user these files belong in git with the code change.

Rule file template

---
description: One-line summary
globs: frontend/src/**   # omit if alwaysApply: true
alwaysApply: false
---

# Title

- Bullet convention
- ✅ Do / ❌ Don't example

What not to capture

• Temporary deadlines or "for v1 only" unless labeled as such
• Secrets, env values, credentials
• Entire chat transcripts — distill to 3–7 bullets

Example

User: "Remember: all lab task status badges use labTaskStatusDisplay helpers."

Action: Add bullet to frontend-components.mdc or backend-nestjs.mdc (whichever fits), not a new 200-line doc.