PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Applies layered n-tier architecture with enforced boundaries.
Install Architecture Paradigm Layered
$ npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install athola/claude-night-market architecture-paradigm-layered --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigm-layered .claude/skills/architecture-paradigm-layered && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "architecture-paradigm-layered" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigm-layered into .claude/skills/architecture-paradigm-layered/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigm-layered", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigm-layeredType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install athola/claude-night-market architecture-paradigm-layered --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigm-layered .agents/skills/architecture-paradigm-layered && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "architecture-paradigm-layered" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigm-layered into .agents/skills/architecture-paradigm-layered/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigm-layered", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install athola/claude-night-market architecture-paradigm-layered --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigm-layered .cursor/skills/architecture-paradigm-layered && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "architecture-paradigm-layered" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigm-layered into .cursor/skills/architecture-paradigm-layered/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigm-layered", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/athola/claude-night-market.git --path plugins/archetypes/skills/architecture-paradigm-layered--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install athola/claude-night-market architecture-paradigm-layered --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigm-layered .gemini/skills/architecture-paradigm-layered && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "architecture-paradigm-layered" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigm-layered into .gemini/skills/architecture-paradigm-layered/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigm-layered", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install athola/claude-night-market architecture-paradigm-layeredInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigm-layered .github/skills/architecture-paradigm-layered && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "architecture-paradigm-layered" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigm-layered into .github/skills/architecture-paradigm-layered/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigm-layered", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install athola/claude-night-market architecture-paradigm-layered --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigm-layered .opencode/skills/architecture-paradigm-layered && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "architecture-paradigm-layered" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigm-layered into .opencode/skills/architecture-paradigm-layered/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigm-layered", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
architecture-paradigm-layered- GitHub stars
- 341
- Token cost
- ~1.4k tokens
- SKILL.md length
- 647 words
- Files
- 1
- Skills in repo
- 152
- Repo updated
- First seen
- Licence
- MIT
At a glance
Applies layered n-tier architecture with enforced boundaries.
- Works in 5 steps: Define the Layers: Establish a clear set… → Enforce Dependency Direction: Code in a… → Centralize Cross-Cutting Concerns:… → …
- Designing moderate systems needing clear presentation
- SKILL.md covers When to Employ This Paradigm, When NOT To Use This Paradigm, Adoption Steps and Key Deliverables, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Architecture Paradigm Layered is an agent skill from athola/claude-night-market. Applies layered n-tier architecture with enforced boundaries. Use when designing moderate systems needing clear presentation, domain, and persistence layers.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: 23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context… The licence is MIT.
When your agent uses it
- Designing moderate systems needing clear presentation
- Persistence layers
Example prompts
- “Use the architecture-paradigm-layered skill to apply layered n-tier architecture with enforced boundaries”
- “/architecture-paradigm-layered”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Define the Layers: Establish a clear set of layers. A common stack includes: Presentation -> Application/Service -> Domain -> Data Access.
- Enforce Dependency Direction: Code in a given layer may only depend on the layer immediately below it. Forbid any "upward" dependencies or…
- Centralize Cross-Cutting Concerns: Implement concerns like logging, authentication, and validation as centralized middleware or policies…
- Test Each Layer Appropriately: Apply testing strategies suitable for each layer, such as unit tests for the domain layer, service-layer…
- Document and Enforce Interactions: Maintain up-to-date dependency diagrams and use automated architecture tests to prevent developers from…
What it can do on your machine
Read from SKILL.md and the folder at commit 9f3eb00. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Architecture Paradigm Layered loads about 1.4k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 647 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from athola/claude-night-market at commit 9f3eb00, republished under its MIT licence (© athola). 647 words, ~1,450 tokens.
Download SKILL.mdSave it as
.claude/skills/architecture-paradigm-layered/SKILL.md (or your agent's skills folder).- name
- architecture-paradigm-layered
- description
- Applies layered n-tier architecture with enforced boundaries. Use when designing moderate systems needing clear presentation, domain, and persistence layers.
- alwaysApply
- false
- category
- architectural-pattern
- tags
- architecture, layered, n-tier, separation-of-concerns, monolith
- usage_patterns
- paradigm-implementation, legacy-system-modernization, team-structure-alignment, compliance-requirements
- complexity
- low
- model_hint
- fast
- estimated_tokens
- 700
The Layered (N-Tier) Architecture Paradigm
When to Employ This Paradigm
- When teams need clear architectural boundaries and a familiar structure for moderate-sized systems.
- When compliance or operations teams require clear separation of concerns (e.g., UI vs. domain logic vs. persistence).
- When the deployment artifact remains a monolith, but code clarity and separation are degrading.
When NOT To Use This Paradigm
- When high scalability demands require independent scaling of components
- When multiple teams need independent deployment cycles
- When complex business logic requires frequent cross-layer communication
- When microservices architecture is already planned or in place
- When real-time processing requirements make layered communication too slow
Adoption Steps
- Define the Layers: Establish a clear set of layers. A common stack includes: Presentation -> Application/Service -> Domain -> Data Access.
- Enforce Dependency Direction: Code in a given layer may only depend on the layer immediately below it. Forbid any "upward" dependencies or imports.
- Centralize Cross-Cutting Concerns: Implement concerns like logging, authentication, and validation as centralized middleware or policies, rather than duplicating this logic in each layer.
- Test Each Layer Appropriately: Apply testing strategies suitable for each layer, such as unit tests for the domain layer, service-layer tests for orchestration logic, and integration tests for persistence adapters.
- Document and Enforce Interactions: Maintain up-to-date dependency diagrams and use automated architecture tests to prevent developers from creating "shortcut" dependencies that violate the layering rules.
Key Deliverables
- An Architecture Decision Record (ADR) that captures the responsibilities of each layer, the allowed dependencies between them, and the policy for any exceptions.
- A formal dependency diagram stored with the project documentation.
- Automated architectural checks (e.g., using ArchUnit, dep-cruise, or custom scripts) to prevent rule violations from being merged.
Technology Guidance
Layer Implementation Patterns:
- Presentation Layer: React/Vue/Angular (Frontend), MVC Controllers (Backend)
- Application Layer: Service classes, Application services, Use case orchestrators
- Domain Layer: Business entities, Domain services, Business rules validation
- Data Access Layer: Repository pattern, ORM mappers, Data access objects (DAO)
Architecture Enforcement Tools:
- Java: ArchUnit for dependency rule testing
- JavaScript/TypeScript: ESLint rules with dependency tracking
- C#: NDepend for architectural analysis
- Python: Custom decorators and import analysis tools
Common Layer Stacks:
- 3-Layer: Presentation → Business Logic → Data Access
- 4-Layer: Presentation → Application → Domain → Infrastructure
- 5-Layer: UI → Controller → Service → Domain → Persistence
Show full SKILL.md (280 more words)Show less
Real-World Examples
Enterprise ERP Systems: SAP and Oracle ERP use layered architecture to separate user interfaces from business logic and database operations, enabling different frontend applications to share the same business rules.
Banking Applications: Financial institutions employ layered architecture to maintain strict separation between customer-facing interfaces, transaction processing, and secure data storage for regulatory compliance.
E-commerce Platforms: Traditional e-commerce sites use layered architecture to separate product catalogs, shopping cart logic, order processing, and payment handling into distinct layers.
Risks & Mitigations
- Excessive Rigidity and Latency:
- Mitigation: For features that span multiple layers, strict adherence can lead to excessive "pass-through" code and increased latency. In such cases, consider using a Façade pattern to provide a more direct interface where appropriate.
- "Leaky" Layers:
- Mitigation: Developers may be tempted to bypass architectural rules for expediency, which degrades the architecture. Treat all architectural violations as build-breaking failures or critical issues in code review.
Concrete Components
Vocabulary for the tools and abstractions an implementation of this
paradigm tends to carry. Not dependencies, and not tools: frontmatter.
dependency-validator: fails the build when a layer imports above its allowed depthlayer-enforcer: static-analysis gate that checks namespaces match layer rulesarchitecture-compliance-checker: diffs the implemented layer graph against the documented one
Exit Criteria
- An ADR captures the chosen layer stack (3-layer, 4-layer, or 5-layer), responsibilities per layer, allowed dependency direction, and the policy for cross-layer exceptions.
- A formal dependency diagram is committed to project documentation and matches the ADR's stated layer boundaries.
- Automated architectural checks (ArchUnit, dep-cruise, or equivalent) are wired into CI and fail the build on any upward dependency.
- Cross-cutting concerns (logging, auth, validation) are implemented once as middleware or policy and are not duplicated across layer implementations.
© athola, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/archetypes/skills/architecture-paradigm-layered of athola/claude-night-market.
Open the folder on GitHubat commit 9f3eb00
Compare with similar skills
Architecture Paradigm Layered next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Architecture Paradigm Layered this skillathola/claude-night-market | 341 | — | ~1.4k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Mailspring App ScreenshotsFoundry376/Mailspring | 18k | — | ~1.5k | Automated safety check: Pass | GPL-3.0 | |
| Merge Dependabot PRsonyx-dot-app/onyx | 32k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Android UI Visual Reviewpermissionlesstech/bitchat-android | 7.8k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Constraint-Driven Developmentaddyosmani/agent-skills | 105k | 2 repos | ~5.2k | Automated safety check: Pass | MIT |
Similar skills
Mailspring App Screenshots
Foundry376/Mailspring
Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.
Merge Dependabot PRs
onyx-dot-app/onyx
Triages and lands a batch of open Dependabot PRs in the Onyx repo, where main is gated exclusively by GitHub's merge queue: approves and enqueues green PRs, closes superseded duplicates, fixes…
Android UI Visual Review
permissionlesstech/bitchat-android
Analyze an Android pull request, branch, commit, or patch for user-visible changes and produce reproducible before/after screenshots from isolated builds.
Constraint-Driven Development
addyosmani/agent-skills
Records a project's quality bar in CONSTRAINTS.md and watches diffs for signs an agent quietly weakened it, such as suppressions, skipped tests or lowered thresholds.
Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
More from athola/claude-night-market
All 152 skills in this repoNight Market Diagnostics Toolkit
athola/claude-night-market
Run and interpret repo diagnostic scripts (ratchets, validators, token stats).
Skills Eval
athola/claude-night-market
Evaluate Claude skill quality through auditing. An agent skill from athola/claude-night-market.
Agent Teams
athola/claude-night-market
Coordinates Claude agent teams via filesystem protocol. An agent skill from athola/claude-night-market.
Delegation Core
athola/claude-night-market
Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer).
Elegant Code
athola/claude-night-market
Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage.
Skill Library Mission
athola/claude-night-market
Build a project skill library in .claude/skills/ via discovery, parallel authoring, and review.
Related
Categories
Questions about Architecture Paradigm Layered
What does Architecture Paradigm Layered do?
Applies layered n-tier architecture with enforced boundaries. Architecture Paradigm Layered is an agent skill from athola/claude-night-market. Applies layered n-tier architecture with enforced boundaries.
When should I use Architecture Paradigm Layered?
Architecture Paradigm Layered fits situations like: designing moderate systems needing clear presentation; persistence layers.
How do I install Architecture Paradigm Layered in Claude Code?
Run `npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a claude-code`. Or copy the skill folder (plugins/archetypes/skills/architecture-paradigm-layered in athola/claude-night-market) into .claude/skills/architecture-paradigm-layered in your project. Claude Code loads it when a task matches its description.
How do I install Architecture Paradigm Layered in Codex?
Run `npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a codex`. Or copy the skill folder (plugins/archetypes/skills/architecture-paradigm-layered in athola/claude-night-market) into .agents/skills/architecture-paradigm-layered in your project. Codex loads it when a task matches its description.
Can I use Architecture Paradigm Layered in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add athola/claude-night-market --skill architecture-paradigm-layered -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-paradigm-layered, .gemini/skills/architecture-paradigm-layered, .github/skills/architecture-paradigm-layered and .opencode/skills/architecture-paradigm-layered in your project.
What does Architecture Paradigm Layered need to run?
SKILL.md names no scripts, command-line tools or credentials: Architecture Paradigm Layered is instructions for the agent only.
Does Architecture Paradigm Layered access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Architecture Paradigm Layered safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Architecture Paradigm Layered use?
Architecture Paradigm Layered is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Architecture Paradigm Layered use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Architecture Paradigm Layered?
Skills that share tags, products or a category with Architecture Paradigm Layered: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Mailspring App Screenshots (Foundry376/Mailspring, 18k stars), Merge Dependabot PRs (onyx-dot-app/onyx, 32k stars) and Android UI Visual Review (permissionlesstech/bitchat-android, 7.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architecture Paradigm Layered?
athola (a GitHub user) maintains it in athola/claude-night-market, which has 341 GitHub stars. The repository holds 152 skills in this directory. The repository was last updated on October 9, 2026.
Source: athola/claude-night-market on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.