ClawTrust
1.9k Downloads
Overview
Governance-driven PHP full‑stack delivery assistant that structures analysis, implementation, and verification for backend, frontend, database, and DevOps/CI work within OpenClaw.
Key Advantages
1.Strong pre-flight analysis: explicitly defines goals, acceptance criteria, risks, constraints, and verification before coding.
2.Emphasis on safe data and schema changes, including rollback/rollout thinking and avoidance of destructive DB operations without clarity.
3.Explicit API/UI contracts (payloads, errors, pagination, idempotency) to reduce ambiguity and regression risk.
4.Built-in governance gates and stop-work rules for unclear auth/authz, destructive DB changes, and unknown runtime versions.
5.Encourages repeatable execution via memory/logging and project-level tracking of work across sessions, improving long-term maintainability and auditability. administration (memory + logs). This track,
Use Cases
- Designing and implementing new PHP backend features that affect APIs, authentication, or business-critical data flows.
- Planning and executing database schema changes, data migrations, or refactors where rollback and data integrity are important.
- Debugging complex production issues that span PHP backend, frontend, and database layers and require methodical investigation and logging.
- Refactoring legacy PHP codebases (including frameworks like Laravel, Symfony, or custom stacks) with a focus on minimizing regressions.
- Defining or updating REST/GraphQL API contracts, including error handling, pagination, and versioning strategies, with explicit agreements documented up front. overhauling underlying clients for the.
Evaluation Scores
8.6
/ 10
Reliability
8.9
Functionality
8.8
Usability
7.5
Safety
9.3
Performance
7.8
Compatibility
8.7
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.6/103/19/2026▼
OS: linux-arm64LLM: google/gemini-2.5-flash-lite
**Judgement:** High-quality, senior-level PHP full‑stack delivery skill that is particularly strong for production-grade, risk-sensitive work. It prioritizes governance, clarity, and reproducible verification over speed, making it excellent for serious engineering tasks but potentially heavy for quick experiments.
**Strengths:**
- Enforces pre-flight planning (goal, acceptance criteria, risks, constraints, verification), which reduces rework and hidden failure modes.
- Strong safety posture around auth/authz, data integrity, API contracts, and runtime/rollout uncertainties, with explicit stop‑work rules.
- Encourages explicit contracts (payloads, errors, pagination, idempotency) and structured testing instructions, improving reliability and team alignment.
- Integrates with OpenClaw memory/logging for repeatable execution and traceability across sessions.
**Key Risks / Limitations:**
- Process-heavy: the governance questions, stop‑work gates, and pre‑flight steps may feel slow or overkill for small, low-risk tasks or quick prototypes.
- May halt progress if environment details (PHP/framework/DB versions, auth rules, rollout/rollback) are not supplied, requiring more upfront user input.
- Highly specialized for PHP full‑stack and related DevOps/CI work; not suited for non-PHP stacks or purely non-engineering tasks.
- References to governance/logging files (e.g., `INFO_GOVERNANCE.md`, `LOG_CONFLICTS.md`) assume some project conventions that might not exist in all setups.
**Recommended Scenarios:**
- Production or near-production PHP work where security, data integrity, and API stability are critical.
- Complex refactors, migrations, or multi-step delivery efforts that benefit from structured planning and repeatable execution.
- Team environments that want traceable decisions, explicit contracts, and clearly documented "how to test" instructions.
- Any situation with ambiguity or multiple plausible approaches, where a methodical, senior-style engineering process is preferable to fast trial-and-error.
Comments (0)
No comments yet. Be the first!