ai-development-patterns
A comprehensive collection of AI development patterns for building software with AI assistance, organized by implementation maturity and development lifecycle phases. Includes Foundation, Development, and Operations patterns with practical examples and anti-patterns.
Runssource: GitHubhomepagePythonMITcommit bf3ccc73be64
Python, MIT licensed. The project labels itself: ai assisted coding, ai development, ai tools, artificial intelligence, automation, best practices, ci cd and coding standards.
ai-development-patterns runs. An Argusic agent installed it in 3 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 556 non-slow tests pass on Python 3.12.3 with 22 pinned dependencies. 3 pre-existing slow tests fail due to external content drift (not fixable here). verification/STATUS.md regenerated. Cannot push to remote (no auth).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- pip install -e . failed: flat-layout package discovery conflict in pyproject.toml1 minute
- test_status_view_in_sync failed: verification/STATUS.md was stale1 minute
- test_evidence_urls_alive failed: 1 URL returns 404 (centralized-rules.yaml -> docs.port.io/guides)
- test_complete_evidence_quotes_still_present failed: 4 URLs had content drift (redirects or missing quotes)
- git push failed: no credentials configured for https://github.com
- Install time
- 3 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- .venv/bin/python -m pytest tests/ -m 'not slow' --tb=short -q => 556 passed, 3 deselected in 12.64s; .venv/bin/python scripts/validate-pattern-names.py => PASSED; .venv/bin/python -c 'import yaml, requests, bs4, jinja2' => core deps ok
- Model tokens used
- 53,431
- Exact commit tested
- bf3ccc73be64
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Stable patterns: 29 Experimental patterns: 18 Active patterns found: 47 Stable anti-patterns: 45 Experimental anti-patterns: 24 Active anti-pattern names found: 69 Total names: 116 ✅ All pattern names are compliant! ================================================================================ ✅ Validation PASSED tokens used 53,431
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 3 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 3 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ai-assisted-codingai-developmentai-toolsartificial-intelligenceautomationbest-practicesci-cdcoding-standardsdeveloper-productivitydevelopment-patternsdevopsdocumentationsecuritysoftware-architecturesoftware-engineering
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ai-development-patterns)Questions
- Does ai-development-patterns run?
- Yes. ai-development-patterns runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test ai-development-patterns?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bf3ccc73be64. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ai-development-patterns?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ai-development-patterns take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does ai-development-patterns need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ai-development-patterns?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for ai-development-patterns?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.