remember

Persist guidelines and architectural decisions into repository knowledge files.

154|28|Updated Aug 31, 2018
One-click install
npx skills add https://github.com/commercetools/ui-kit --skill remember-commercetools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/commercetools/ui-kit/tree/main/.agents/skills/remember
Command: npx skills add https://github.com/commercetools/ui-kit --skill remember-commercetools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repositories often lose or scatter important conventions, design decisions, and agent behaviors across commits, PRs, and ephemeral AI sessions, making it hard to reproduce or follow standardized practices. This Skill captures those guidelines in a central, versioned location so future contributors and AI agents can discover and apply them consistently.

Core Features & Use Cases

  • Intent distillation: Translate freeform user input into concise, technical guidelines suitable for documentation.
  • Target resolution & safe writing: Determine the appropriate file (rules/, docs/conventions/, AGENTS.md, or .agents/.claude layers), detect conflicts, and write updates following repository resolution rules.
  • Conflict analysis & synchronization: Halt and report contradictions for user clarification, update local skill files when applicable, and discover affected skills including symlink resolution for coordinated updates.
  • Use Case: Record a new CI requirement or architectural decision so subsequent AI sessions and contributors reference the same, authoritative rule.

Quick Start

Use the remember skill to persist the guideline always use the --frozen-lockfile flag in CI.

Frequently Asked Questions about remember

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist repository conventions and architectural decisions for future AI coding sessions?

To persist repository conventions, you distill freeform intent into technical guidelines and write them to authoritative files like AGENTS.md or docs/conventions/. This ensures future AI agents and contributors consistently apply the same standardized practices.

How do I save project guidelines and workflow changes into a knowledge base?

You save project guidelines by scanning target files, detecting conflicts, and creating or updating documentation and local skill files. This captures workflow changes in a central, versioned location so subsequent sessions can discover and apply them consistently.

What happens when new documentation contradicts existing repository rules?

When new documentation contradicts existing repository rules, the process halts and reports the conflict for user clarification. This conflict analysis prevents overwriting valid architectural decisions without explicit user approval.

Can I record agent behavior notes and domain-specific rules across different repository layers?

Yes, you can record agent behavior notes and domain-specific rules by resolving symlinks according to repository layer rules. It determines the appropriate file location, whether in rules/, .agents/.claude layers, or AGENTS.md.

What's the best way to document CI requirements so AI agents follow them automatically?

The best way to document CI requirements is to translate them into concise, technical guidelines and persist them into the repository's knowledge base. This allows AI-assisted coding sessions to discover and apply the authoritative rule automatically.