Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
中文简介正在准备中。当前显示原文说明。
GRASP principles knowledge base for PHP 8.5 projects. Provides quick reference for 9 responsibility assignment patterns (Information Expert, Creator, Controller, Low Coupling, High Cohesion, Polymorphism, Pure Fabrication, Indirection, Protected Variations). Use for architecture audits and design decisions.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
GRASP (General Responsibility Assignment Software Patterns) provides guidelines for assigning responsibilities to classes and objects in object-oriented design.
| Principle | Core Question | Goal |
|---|---|---|
| Information Expert | Who has the data? | Assign to class with information |
| Creator | Who creates objects? | Assign creation responsibility |
| Controller | Who handles system events? | Coordinate use case flow |
| Low Coupling | How to reduce dependencies? | Minimize interconnections |
| High Cohesion | How to focus responsibilities? | Keep related things together |
| Polymorphism | How to handle type variations? | Use polymorphic operations |
| Pure Fabrication | What if no domain class fits? | Create artificial class |
| Indirection | How to decouple? | Add intermediate object |
| Protected Variations | How to handle change? | Hide variation points |
# Feature Envy: Class uses other class's data more
Grep: "->get.*->get.*->get" --glob "**/*.php"
# Train wreck calls
Grep: "->.*()->.*()->.*()->" --glob "**/*.php"
Signs: Method accesses other object's data extensively, data and behavior separated.
# Random creation locations
Grep: "new\s\+[A-Z][a-z]*[A-Z]" --glob "**/*.php"
Signs: Objects created in unexpected places, no clear creation ownership.
# Fat controllers (>100 lines)
find . -path "*/Controller/*.php" -exec wc -l {} \; | awk '$1 > 100'
# Business logic in controllers
Grep: "if.*&&.*||" --glob "*Controller.php"
Signs: Controller has >100 lines, business logic in controller.
# High dependency count (>7)
Grep: "__construct" --glob "**/*.php" -A 15
# Concrete type dependencies
Grep: "function.*([A-Z][a-z]*[A-Z]" --glob "**/*.php"
Signs: Class has >7 dependencies, depends on concrete classes.
# Unrelated method names
Grep: "public function" --glob "**/*.php" | grep -E "And[A-Z]|Or[A-Z]"
# Multiple responsibilities in class name
Grep: "class.*Manager|class.*Handler|class.*Processor" --glob "**/*.php"
Signs: Methods don't relate to each other, class does many unrelated things.
// BAD: Logic outside of object with data
final class OrderService
{
public function calculateTotal(Order $order): Money
{
$total = Money::zero();
foreach ($order->getLines() as $line) {
$total = $total->add($line->getProduct()->getPrice()->multiply($line->getQuantity()));
}
return $total;
}
}
// GOOD: Logic in class that has the data
final class Order
{
public function total(): Money
{
return array_reduce(
$this->lines,
fn(Money $sum, OrderLine $line) => $sum->add($line->total()),
Money::zero(),
);
}
}
// BAD: Depends on concrete classes
final class ReportGenerator
{
public function __construct(
private DoctrineOrderRepository $orders,
private SymfonyMailer $mailer,
) {}
}
// GOOD: Depends on abstractions
final readonly class ReportGenerator
{
public function __construct(
private OrderReader $orders,
private Mailer $mailer,
) {}
}
// BAD: Low cohesion - unrelated responsibilities
final class UserManager
{
public function register(array $data): User { }
public function sendEmail(User $user): void { }
public function generateReport(): string { }
}
// GOOD: High cohesion - focused responsibilities
final readonly class UserRegistrationService
{
public function register(RegistrationData $data): User { }
public function confirmEmail(Token $token): void { }
}
| GRASP | DDD Application |
|---|---|
| Information Expert | Entities contain their behavior |
| Creator | Aggregates create their entities |
| Controller | Application Services / Use Cases |
| Low Coupling | Bounded Context boundaries |
| High Cohesion | Aggregate consistency boundary |
| Polymorphism | Domain Services, Strategies |
| Pure Fabrication | Repositories, Factories, Specifications |
| Indirection | Anti-Corruption Layer, Adapters |
| Protected Variations | Ports & Adapters, Domain Events |
For detailed patterns and examples, see references/:
information-expert.md — Tell Don't Ask, calculations in ownercreator.md — Factory patterns, aggregation rulescontroller.md — Use case handlers, thin controllerslow-coupling.md — Dependency injection, abstractionshigh-cohesion.md — Focused responsibilitiespolymorphism.md — Strategy pattern, type variationspure-fabrication.md — Repositories, specificationsindirection.md — Adapters, mediatorsprotected-variations.md — Stable interfacesantipatterns.md — Common GRASP violationsassets/report-template.md — GRASP audit report format还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
中文简介正在准备中。当前显示原文说明。
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
中文简介正在准备中。当前显示原文说明。
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
中文简介正在准备中。当前显示原文说明。
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
中文简介正在准备中。当前显示原文说明。
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
中文简介正在准备中。当前显示原文说明。
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
中文简介正在准备中。当前显示原文说明。