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:
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository28 other files it gives its agents.
- generate-skillSkill
- neo-azure-pipelinesSkill
- neo-clarificationSkill
- neo-clean-architectureSkill
- neo-code-reviewSkill
- neo-csharp-interface-generatorSkill
- neo-csharpSkill
- neo-dotnet-ef-coreSkill
- neo-dotnet-minimal-apisSkill
- neo-dotnet-mvcSkill
- neo-dotnetSkill
- neo-dotnet-tag-helperSkill
- neo-dotnet-webapiSkill
- neo-harness-projectSkill
- neo-harnessSkill
- neo-javascriptSkill
- neo-opentelemetrySkill
- neo-prSkill
- neo-python-managerSkill
- neo-pythonSkill
- neo-rabbitmqSkill
- neo-rustSkill
- neo-stop-slopSkill
- neo-sub-agentSkill
- neo-swiftSkill
- neo-swift-uiSkill
- neo-typescriptSkill
- neo-vueSkill
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
- Distinctive: line 9
Follow modular architecture and existing code formatting.
- Distinctive: line 11
Do NOT introduce unrequested third-party dependencies.
- Distinctive: line 43
Perceive Task: Read project guidelines (AGENTS.md) and target source files to understand goals and constraints.
- Distinctive: line 44
Establish Baseline: Run existing test and build commands to confirm the project is in a stable, passing state.
- Distinctive: line 45
Reproduce Problem: Write or run test cases/verification steps that reliably reproduce the issue or requirement.
- Distinctive: line 48
Incremental Verification: Run local test, lint, and build commands immediately after each edit.
- Very specific: line 49
Self-Review: After an AI Agent finishes modifying code, tests, configuration, or scripts, activate neo-code-review and review the current …
- Distinctive: line 50
Remediate on Failure: If verification or review finds a critical issue, the review scope is unclear, or the skill cannot be loaded, do not …
≈ “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.
Files
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 Type | Exact Command Line | Purpose / Scope |
| Unit / Integration Tests | npm test | Verify behavioral correctness |
| Skill Syntax Check | python3 scripts/check-skills-syntax.py | Verify skill markdown and frontmatter syntax |
| Build Check | npm run build | Confirm 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]- Perceive Task: Read project guidelines (
AGENTS.md) and target source files to understand goals and constraints. - Establish Baseline: Run existing test and build commands to confirm the project is in a stable, passing state.
- Reproduce Problem: Write or run test cases/verification steps that reliably reproduce the issue or requirement.
- Plan Edits: Decompose the task into small, atomic edit plans to avoid large single-turn changes.
- Minimal Implementation: Apply minimal code changes while preserving existing comments and public API contracts.
- Incremental Verification: Run local test, lint, and build commands immediately after each edit.
- Self-Review: After an AI Agent finishes modifying code, tests, configuration, or scripts, activate
neo-code-reviewand 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. - 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-reviewafter each remediation. - Handoff upon Pass: Once all verification sensors pass, present a concise report with empirical proof for handoff.
4. Forbidden Antipattern Redlines
| Forbidden Action | Why It Is Prohibited | Required Behavior |
| Silent Exception Swallowing | Hides runtime failures and causes silent data corruption. | Let exceptions surface or handle explicitly with logging. |
| Test Deletion / Suppression | Forces builds to pass without fixing underlying bugs. | Fix root cause in source or update contract with justification. |
| Hallucinated Signatures | Invokes non-existent methods causing runtime crashes. | View symbol definition using search tools first. |
| Unverified Completion Claim | Misleads user regarding feature or bug state. | Run test/build commands and present log proof. |
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
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.

