Trace and verify fixes for complex Questerix platform bugs using IDD Protocol.
npx skills add https://github.com/rmg007/Questerix --skill ironclad-architect
Please help me install this Agent Skill. Skill: ironclad-architect Source: https://github.com/rmg007/Questerix/tree/main/.agent/skills/ironclad-architect Command: npx skills add https://github.com/rmg007/Questerix --skill ironclad-architect
This Skill provides a rigorous, systematic approach to diagnosing and resolving complex, hard-to-fix, or silent bugs within the Questerix platform, ensuring root causes are identified and fixes are robust.
Use the ironclad-architect skill to analyze a silent data corruption bug in the student app.
High-intent search queries and answers about installing and using this skill.
Root cause analysis for silent data corruption uses a structured 5-phase IDD protocol and RARV cycle to trace bugs from symptom to origin. This forensic approach checks against 17 production bug patterns to identify race conditions or state corruption.
Debugging cascading bugs across platform layers requires platform-aware analysis that adapts to the detected environment, such as Admin Panel, Student App, Edge Functions, or Database. It traces data flow across all layers to verify fixes and prevent new problems.
Yes, forensic debugging fixes race conditions in a Student App by tracing data flow after sync operations. It identifies state corruption and proposes verified fixes complete with regression tests to ensure no new problems are introduced.
The forbidden-pattern checklist prevents new problems during bug fixing by validating proposed fixes against known anti-patterns. Combined with 17 production bug pattern checks, it ensures fixes are robust and do not introduce regressions.
You need a forensic root cause analysis engine for platform architecture when facing hard-to-fix or silent bugs within the Questerix platform. It provides staff-level systematic diagnosis to resolve complex issues and verify fixes.
Root cause analysis works across Edge Functions and Database layers by adapting its debugging approach based on the detected platform. It systematically traces bugs across all layers to identify origins and propose robust fixes.
kollaboraiDiagnose MCP server connection failures, tool registration issues, and execution errors.
Cor-IncorporatedIdentify, fix, and regression-test bugs across a codebase.
duanbiao2000Create Grafana dashboards with panels for request rate, error rate, and latency.
duy-tungDebug software issues through systematic root cause analysis and verification.
