agentleFS
BenknightdarkBenknightdark/neo-skills/AGENTS.md

neo-skills

AGENTS.md7 starsChanged 6 months agoMITView on GitHub

List exact command lines used for project development, testing, linting, typechecking, and building: The development workflow strictly follows this 9-stage closed loop:

The file

We split this AGENTS.md into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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. Distinctive:

    Follow modular architecture and existing code formatting.

    line 9
  2. Distinctive:

    Do NOT introduce unrequested third-party dependencies.

    line 11
  3. Distinctive:

    Perceive Task: Read project guidelines (AGENTS.md) and target source files to understand goals and constraints.

    line 43
  4. Distinctive:

    Establish Baseline: Run existing test and build commands to confirm the project is in a stable, passing state.

    line 44
  5. Distinctive:

    Reproduce Problem: Write or run test cases/verification steps that reliably reproduce the issue or requirement.

    line 45
  6. Distinctive:

    Incremental Verification: Run local test, lint, and build commands immediately after each edit.

    line 48
  7. Very specific:

    Self-Review: After an AI Agent finishes modifying code, tests, configuration, or scripts, activate neo-code-review and review the current …

    line 49
  8. Distinctive:

    Remediate on Failure: If verification or review finds a critical issue, the review scope is unclear, or the skill cannot be loaded, do not …

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md 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
AGENTS.md

neo-skills AGENTS.md


1. Project Overview

  • Primary Technology Stack: Node.js / JavaScript
  • Coding & Architectural Conventions:
    • Follow modular architecture and existing code formatting.
    • Inspect existing implementation files before creating new utilities.
    • Do NOT introduce unrequested third-party dependencies.

2. Commands

List exact command lines used for project development, testing, linting, typechecking, and building:

Command TypeExact Command LinePurpose / Scope
Unit / Integration Testsnpm testVerify behavioral correctness
Skill Syntax Checkpython3 scripts/check-skills-syntax.pyVerify skill markdown and frontmatter syntax
Build Checknpm run buildConfirm clean compilation

3. Workflow

The development workflow strictly follows this 9-stage closed loop:

graph TD
    Step1[1. Perceive Task] --> Step2[2. Establish Baseline]
    Step2 --> Step3[3. Reproduce Problem]
    Step3 --> Step4[4. Plan Edits]
    Step4 --> Step5[5. Minimal Implementation]
    Step5 --> Step6[6. Incremental Verification]
    Step6 --> Step7[7. Self-Review]
    Step7 -->|Fail| Step4
    Step7 -->|Pass| Step9[9. Handoff upon Pass]
  1. Perceive Task: Read project guidelines (AGENTS.md) and target source files to understand goals and constraints.
  2. Establish Baseline: Run existing test and build commands to confirm the project is in a stable, passing state.
  3. Reproduce Problem: Write or run test cases/verification steps that reliably reproduce the issue or requirement.
  4. Plan Edits: Decompose the task into small, atomic edit plans to avoid large single-turn changes.
  5. Minimal Implementation: Apply minimal code changes while preserving existing comments and public API contracts.
  6. Incremental Verification: Run local test, lint, and build commands immediately after each edit.
  7. Self-Review: After an AI Agent finishes modifying code, tests, configuration, or scripts, activate neo-code-review and review the current uncommitted working tree with --working-tree. Inspect diffs and execution logs; if checks fail, read full un-truncated error logs to find the root cause.
  8. Remediate on Failure: If verification or review finds a critical issue, the review scope is unclear, or the skill cannot be loaded, do not declare completion or hand off. Return to "Plan Edits / Minimal Implementation", then rerun verification and neo-code-review after each remediation.
  9. Handoff upon Pass: Once all verification sensors pass, present a concise report with empirical proof for handoff.

4. Forbidden Antipattern Redlines

Forbidden ActionWhy It Is ProhibitedRequired Behavior
Silent Exception SwallowingHides runtime failures and causes silent data corruption.Let exceptions surface or handle explicitly with logging.
Test Deletion / SuppressionForces builds to pass without fixing underlying bugs.Fix root cause in source or update contract with justification.
Hallucinated SignaturesInvokes non-existent methods causing runtime crashes.View symbol definition using search tools first.
Unverified Completion ClaimMisleads user regarding feature or bug state.Run test/build commands and present log proof.

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.