methodology-setup

Refresh and reinitialize Azurita memory-bank files to align with repository changes.

1|Updated Sep 6, 2024
One-click install
npx skills add https://github.com/carlos18bp/gym_project --skill methodology-setup-carlos18bp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: methodology-setup
Source: https://github.com/carlos18bp/gym_project/tree/main/.agents/skills/methodology-setup
Command: npx skills add https://github.com/carlos18bp/gym_project --skill methodology-setup-carlos18bp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When project structure or runtime guidance drifts after major changes, stale methodology and memory files cause the AI to follow outdated rules, leading to inconsistent outputs and slower iteration.

Core Features & Use Cases

  • Memory-bank refresh: Reinitializes or updates Azurita memory-bank files on explicit request or detected guidance drift.
  • Repo-aligned updates: Reads current memory first, verifies only real codebase facts, and updates only relevant files to avoid unnecessary churn.
  • Surface alignment guardrails: Keeps runtime guidance synchronized with the actual repo layout, including AGENTS scopes and relevant config/compatibility surfaces.

Quick Start

Ask an AI to run a methodology-setup refresh by explicitly requesting a memory file update for the gym_project repository.

Frequently Asked Questions about methodology-setup

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

FAQPage Schema
Why does my AI follow outdated workflow guidance after repository changes?

Stale methodology memory files cause outdated workflow guidance after repository changes. Refreshing and reinitializing these memory-bank files realigns runtime guidance with the actual codebase layout and surfaces.

How do I refresh AI memory files for codebase alignment?

Refresh AI memory files for codebase alignment by explicitly requesting a methodology setup update. The process reads existing memory first, verifies factual deltas from the actual repo, and updates only targeted methodology files.

When do I need to reinitialize Azurita memory-bank files?

Reinitialize Azurita memory-bank files when methodology guidance drifts or when repository layout, runtime surfaces, or recurring workflow guidance undergo major changes requiring codebase synchronization.

Does updating memory-bank files require reading existing memory first?

Updating memory-bank files requires reading existing memory first to verify only real codebase facts. This approach avoids unnecessary churn by updating exclusively relevant methodology files with verified factual deltas.

What is the best way to fix inconsistent AI outputs caused by guidance drift?

Fixing inconsistent AI outputs caused by guidance drift requires reinitializing memory-bank files to align runtime guidance with the actual repository layout. This synchronizes AGENTS scopes and relevant config compatibility surfaces.