- Home
- Skills
- Agents & Orchestration
- design reconcile
Works with the AI Agents you already use
design reconcile
Detect and resolve contradicting recommendations between multiple design review lenses.
$9
design reconcile
Example session with this skill installed
Check for conflicts between docs/remediation/design-review-security.md and docs/remediation/design-review-ux.md in this repo.
- Read your context and instructions
- Compiled the design reconcile
I have analyzed the security and UX lens reports. The automated scanner identified 3 shared code paths, and the conflict reviewer flagged 2 active contradictions that require resolution before generating the action plan.
Design Review Conflicts
| Conflict ID | Involved Findings | Resolution Status | Impact |
|---|---|---|---|
| X-001 | F-SEC-012, F-UX-004 | Decision Required | Security lens mandates 5-min session timeout; UX lens requests 60-min for form persistence. |
| X-002 | F-SEC-045, F-PERF-009 | Resolved | Both suggested changes to auth.py. Resolution: Prefer F-SEC-045 logic with inline performance optimization. |
| X-003 | F-UX-015, F-ACC-002 | Resolved | Identical fix proposed for Button.tsx contrast. Merged into single action. |
Decision D-102: Session Persistence vs Security
The following options are available for X-001:
- Option A: Implement 5-minute hard timeout (Prioritize Security).
- Option B: Implement 60-minute timeout with sliding expiration and re-auth for sensitive actions (Balanced).
- Option C: Implement client-side draft saving to allow 5-minute timeout without data loss (UX recommendation).
Next steps
- Select an option for Decision D-102 to finalize the remediation strategy.
- Run
python3 scripts/conflicts.py checkto verify the final resolution graph. - Proceed to
action-planto generate the implementation tasks.
Connects securely to your tools. The creator never sees your data.
About this skill
Design review often leads to conflicting instructions when multiple lenses (e.g., Security, UX, Performance) are applied to the same codebase. A security patch might recommend shortening a session that UX needs to keep open, or two reviews might propose incompatible refactors for the same function. This skill identifies and reconciles these contradictions before they reach your action plan.
What it does
- Detects collisions by scanning multiple lens reports for overlapping code paths and logic.
- Identifies logic loops where fix orders across different findings create circular dependencies.
- Resolves contradictions by proposing single remediations or identifying trade-offs for human decision.
- Validates consistency using scripts to ensure every conflict resolution maps back to existing findings.
- Maintains a decision log to track architectural choices and ensure consistency across the project.
How it works
- Analyze reports by running a Python script to find mechanical overlaps in the proposed remediation paths.
- Review conflicts using a specialized agent role that evaluates the impact of simultaneous changes.
- Verify resolutions to ensure no findings are lost and no circular fix orders are introduced.
- Finalize decisions by presenting trade-offs to the user and logging the outcomes in a central register.
Frameworks & tools
This skill requires Python 3 for the conflict detection and verification scripts. It integrates with existing design review workflows and can utilize subagent architectures if the host agent supports them.
Why this beats prompting it yourself
Manual reconciliation is prone to missing subtle logic collisions between hundreds of findings. This skill uses a multi-step verification process and graph-based cycle detection to ensure the final action plan is actually buildable.
Use cases
- Reconciling security mandates with performance requirements in high-traffic APIs.
- Merging different frontend refactoring suggestions from UX and accessibility reviews.
- Clearing circular dependencies in large-scale system migrations.
Known limitations
This skill does not edit the original lens reports or code. It requires existing remediation reports to function and assumes Python 3 is available in the environment.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Requires existing design review reports as input. Python 3 must be available for candidate scanning and validation scripts. Does not perform code edits directly.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 12 days ago
- Software
Python