agentleFS
rakaarwakyrakaarwaky/agents-arwaky/skills/architechture/aes-fix/SKILL.md

aes-fix

Skill0 starsChanged 5 days agoMITView on GitHub

AES rule fix references for AES1xx-AES7xx: one step-N file per rule code with concrete fix steps and a verify command.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Turn progress gates: Run lint-arwaky-cli report once at the start of the turn (baseline) and once at the end (delta).

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

aes-fix

Rules

  • One fact, one home. Each references/step-N-AESxxx.md carries the how-to-fix for its rule code; do not restate the same fix in two files.
  • Cite the checker name, not just the rule code, when pointing at implementation (e.g. NamingConventionChecker for AES101).
  • Every reference ends with a Verify step naming the exact command.
  • Turn progress gates. Run lint-arwaky-cli report once at the start of the turn (baseline) and once at the end (delta). A positive delta means the run added problems; the turn is not done.
  • Orchestration and ship are part of step-0-setup.md: group violations by owning member, spawn one subagent per member with its own violations and rule reference links, verify the delta, then open a PR and merge to main.
  • Completion. The end-of-turn report shows zero or negative delta for every touched rule and the PR is merged to main.

Routing

Rule codeReferenceWhat it checks
setupstep-0-setup.mdBaseline, group by member, spawn subagents, verify delta, open PR, merge to main
AES101step-1-AES101.mdNaming: Variable
AES102step-2-AES102.mdNaming: Function / Method
AES103step-3-AES103.mdNaming: Class / Struct
AES201step-4-AES201.mdOrphan: Dead Function / Method
AES202step-5-AES202.mdOrphan: Dead Class / Struct
AES203step-6-AES203.mdOrphan: Dead File
AES204step-7-AES204.mdOrphan: Dead Module
AES205step-8-AES205.mdOrphan: Dead Package
AES301step-9-AES301.mdRole: Agent Layer
AES302step-10-AES302.mdRole: Capabilities Layer
AES303step-11-AES303.mdRole: Contract Layer
AES304step-12-AES304.mdRole: Root Layer
AES305step-13-AES305.mdRole: Surface Layer
AES401step-14-AES401.mdImport: Wildcard
AES402step-15-AES402.mdImport: Unused
AES403step-16-AES403.mdImport: Cycle
AES404step-17-AES404.mdImport: Cross-Layer Upward
AES405step-18-AES405.mdImport: Cross-Sibling
AES406step-19-AES406.mdImport: External
AES501step-20-AES501.mdQuality: Error Handling
AES502step-21-AES502.mdQuality: Test Coverage
AES503step-22-AES503.mdQuality: Type Safety
AES504step-23-AES504.mdQuality: Doc Coverage
AES505step-24-AES505.mdQuality: Logging
AES506step-25-AES506.mdQuality: Performance
AES601step-26-AES601.mdStructure: File Size
AES602step-27-AES602.mdStructure: Module Size
AES603step-28-AES603.mdStructure: Package Size
AES604step-29-AES604.mdStructure: Function Length
AES605step-30-AES605.mdDocument Structure: PRD.md Conformance
AES606step-31-AES606.mdDocument Structure: ROADMAP.md Conformance
AES607step-32-AES607.mdDocument Structure: CONTRIBUTING.md Conformance
AES608step-33-AES608.mdDocument Structure: ARCHITECTURE.md Conformance
AES609step-34-AES609.mdDocument Structure: README.md Conformance
AES610step-35-AES610.mdDocument Structure: AGENTS.md Conformance
AES701step-36-AES701.mdProject Structure: Root Layout
AES702step-37-AES702.mdProject Structure: Crates / Modules
AES703step-38-AES703.mdProject Structure: Scripts
AES704step-39-AES704.mdProject Structure: Tests
AES705step-40-AES705.mdProject Structure: Docs
AES706step-41-AES706.mdProject Structure: PR-LA Folder Mapping

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.