standards/research-api-exploration.md | Map a third-party API's capabilities, constraints, auth, rate limits, and integration cost before building against it |
standards/research-architecture-pattern.md | Identify proven architecture patterns, explain trade-offs with evidence, and recommend the best fit for the project's scale and constraints |
standards/research-cve-scan.md | Determine whether specific CVEs affect the project, assess exploitability in context, and produce a remediation plan |
standards/research-dependency-audit.md | Produce a dependency health report covering security vulnerabilities, abandoned packages, license risks, duplicates, and unused dependencies |
standards/research-library-comparison.md | Compare libraries with an evidence-backed recommendation — functionality, performance, DX, maintenance, license, and migration cost |
standards/research-markdown-format.md | Canonical report template and writing style rules to enforce a consistent, scannable, decision-ready format across all research reports |
standards/research-performance-benchmark.md | Find or produce credible benchmark data and interpret it against the project's actual load profile and SLA |
standards/research-security-advisory.md | Surface known vulnerabilities, security anti-patterns, and best practices with actionable findings |
standards/research-tech-landscape.md | Map a technology's ecosystem readiness, adoption signals, community health, maturity, and trajectory before committing |
standards/research-toolchain-eval.md | Choose the right toolchain for build, test, lint, CI/CD, and IaC based on speed, DX, CI integration, and migration cost |