Skip to content
TrustedSkillsbeta
Back to all skills

Clean Architecture

Checked
giuseppe-trisciuoglio·vlatest·backend·MIT

This skill applies Clean Architecture principles to your backend code, promoting maintainability and testability by separating concerns effectively.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add giuseppe-trisciuoglio/developer-kit --skill clean-architecture -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

giuseppe-trisciuoglio

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned giuseppe-trisciuoglio/developer-kit at fe73fb33a0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
fe73fb33a0
Manifest
plugins/developer-kit-php/skills/clean-architecture/SKILL.md
Scanned
9 files, 4,447 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill equips AI agents with the ability to design and implement software systems following Clean Architecture principles, ensuring separation of concerns and independence from frameworks. It enables agents to structure code where business rules remain decoupled from external entities like databases, user interfaces, and external libraries.

When to use it

  • Refactoring legacy monolithic applications into modular, maintainable structures with clear dependency boundaries.
  • Designing new backend systems that require long-term scalability and ease of testing without framework lock-in.
  • Generating code skeletons where business logic must remain independent of database drivers or UI frameworks.
  • Creating unit tests that isolate core business rules from external infrastructure dependencies.

Key capabilities

  • Enforces strict dependency rules where inner layers (business logic) have no knowledge of outer layers (frameworks, DB).
  • Structures projects with distinct interfaces for use cases, entities, and external adapters.
  • Promotes high cohesion by grouping related functionality into dedicated packages or modules.
  • Facilitates easy swapping of infrastructure components without altering core business rules.

Example prompts

  • "Generate a Clean Architecture project structure for a Python backend handling user authentication."
  • "Refactor this legacy service to adhere to Clean Architecture principles, separating business logic from the database layer."
  • "Create a use case interface and its implementation for transferring funds, ensuring it remains independent of the payment gateway library."

Tips & gotchas

Ensure your AI agent understands that outer layers (like controllers or repositories) must depend on interfaces defined in inner layers. Avoid letting the agent introduce direct dependencies from business logic to specific database drivers or HTTP frameworks, as this violates core Clean Architecture tenets.