agentleFS
Sign inStart free
salmandevsalmandev/everything-gemini/skills/continuous-learning/SKILL.md

continuous-learning

Skill2 starsChanged 28 days agoApache-2.0View on GitHub

Extracts architectural lessons, developer corrections, and project conventions from the current session and records them into permanent rules or Knowledge Items. Activate when the user runs /learn or after resolving a complex issue.

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use project-guidelines-example, clickhouse-io and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HABUBUSSSkill

    project-guidelines-example

    Also in 7 projects that use this

  • HABUBUSSSkill

    clickhouse-io

    ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.

    Also in 6 projects that use this

  • mstuder-slalomSkill

    continuous-learning-v2

    Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    Also in 7 projects that use this

  • Microsoft AzureSkill

    iterative-retrieval

    Max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation. Use when spawning sub-agents to complete scoped work.

    Also in 9 projects that use this

  • mstuder-slalomSkill

    django-verification

    Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

    Also in 4 projects that use this

  • nek1987Skill

    postgres-patterns

    PostgreSQL patterns for reviewing migrations and writing efficient queries. Use when reviewing Alembic migrations, optimizing queries, or debugging database issues.

    Also in 7 projects that use this

  • +4 more from HABUBUSS
  • +1 more from mstuder-slalom

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the insight affects the broader repository architecture, write a dedicated Knowledge Item in <appDataDir>/knowledge with metadata.json …

    line 31

“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Continuous Learning & Instinct Recording

This skill enables Antigravity to retain lessons and developer feedback so mistakes are never repeated.

Learning Workflow

1. Identify the Core Insight

Determine what was learned:

  • Correction: Did the user correct a style, framework version, or tool choice?
  • Bug Fix: Was an obscure bug or configuration issue solved after debugging?
  • Workflow: Was an optimal command sequence identified for building/testing?

2. Format the Instinct

Formulate a concise, imperative rule:

  • Bad: "We had an issue with Docker not starting on port 8080."
  • Good: "Always map Docker container port 8080 to host 8081 to avoid conflicting with local proxy."

3. Persist to .agents/rules/instincts.md

Append the new instinct under the appropriate section in .agents/rules/instincts.md:

- **Topic Name**: Concrete rule statement.

4. For Major Architectural Changes: Create Knowledge Item

If the insight affects the broader repository architecture, write a dedicated Knowledge Item in <appDataDir>/knowledge with metadata.json and artifact details.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free