← All skills
remember
Use when explicitly saving important discoveries or learnings to auto-memory for future sessions.
About this skill
Use when explicitly saving important discoveries or learnings to auto-memory for future sessions.
SKILL.md
remember.SKILL.mdPlace it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review the contents and run it in a controlled environment first.
--- name: remember description: Use when explicitly saving important discoveries or learnings to auto-memory for future sessions. category: Engineering version: 1.0.0 tools: [] --- # Remember — Save Knowledge Explicitly Write an explicit entry to auto-memory when a discovery is too important to rely on auto-capture. ## When to Use | Situation | Example | |-----------|---------| | Hard-won debugging insight | "CORS errors on /api/upload are caused by the CDN, not the backend" | | Project convention not in SYNTIC.md | "We use barrel exports in src/components/" | | Tool-specific gotcha | "Jest needs `--forceExit` flag or it hangs" | | Architecture decision | "We chose Drizzle over Prisma for type-safe SQL" | | Preference for Claude | "Don't add comments explaining obvious code" | ## Workflow ### Step 1: Parse the Knowledge Extract: - **What**: The concrete fact or pattern - **Why it matters**: Context - **Scope**: Project-specific or global? ### Step 2: Check for Duplicates Search MEMORY.md for related entries. Show matching entries and ask: update existing or add new? ### Step 3: Write to MEMORY.md Append one-line entries: - Concise; one line when possible - Include concrete command or value, not just concept - ✓ "Build with `pnpm build`, tests with `pnpm test:e2e`" - ✗ "The project uses pnpm for building and testing" ### Step 4: Check Space If MEMORY.md exceeds 180 lines, warn the user. Consider running review to free space. ### Step 5: Suggest Promotion If the knowledge sounds like a rule (imperative, always/never, convention), suggest promoting to SYNTIC.md for higher priority enforcement. ### Step 6: Confirm Verify entry is saved, show line count, confirm Claude will see it next session. ## What NOT to Use - **Temporary context**: Use session memory - **Enforced rules**: Use promotion to SYNTIC.md - **Cross-project knowledge**: Use `~/.syntic/SYNTIC.md` - **Secrets**: Never store credentials, tokens, or secrets ## Tips - Be concise; one line beats paragraphs - Include concrete command/value, not just concept - If remembering the same thing twice, promote to SYNTIC.md - Dated state files: save before pauses, index in MEMORY.md
Install
Syntic App
- 1Create a dedicated folder for this skill in your local skills library.
- 2Place SKILL.md into that folder.
- 3Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1Save SKILL.md in your local Syntic Code skills directory.
- 2Keep related files in the same skill folder.
- 3Run in a safe environment and validate outputs.