poeaa
Skill0 starsChanged 29 days agoNo licenceView on GitHub
Apply the patterns from Martin Fowler's 'Patterns of Enterprise Application Architecture' (PoEAA) when designing the internals of a server-side business application. Use when: (1) Deciding where to put business/domain logic (Transaction Script vs Domain Model vs Table Module), (2) Designing data-access / object-relational mapping (Active Record, Data Mapper, Unit of Work, Identity Map, Repository, Lazy Load), (3) Structuring layers (presentation / domain / data source) and a Service Layer, (4) Handling web request flow (Page/Front Controller, Template/Transform View), distribution (Remote Facade, DTO), concurrency (Optimistic/Pessimistic Offline Lock), or session state. Reach for this whenever someone asks how to organize an enterprise app's layers, ORM mapping, or domain-logic placement, even if they don't name the patterns.
In this repository32 other files it gives its agents.
- accelerateSkill
- advanced-refactoringSkill
- automated-testingSkill
- clean-architectureSkill
- clean-codeSkill
- cleanupSkill
- commit-messageSkill
- databaseSkill
- design-patternsSkill
- devtoolsSkill
- feature-flagsSkill
- github-actions-cicdSkill
- github-actions-pipelineSkill
- git-workflowSkill
- implementation-patternsSkill
- legacy-codeSkill
- loggingSkill
- pragmatic-programmerSkill
- project-planSkill
- project-structureSkill
- readme-updaterSkill
- refactoringSkill
- remember-your-trainingSkill
- securitySkill
- shell-scriptsSkill
- source-control-readySkill
- statement-of-workSkill
- tddSkill
- technical-estimateSkill
- terraform-aws-infrastructureSkill
- user-storiesSkill
- xunit-test-patternsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
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.

