jaccen/awesome-gaussian-skills/3dgs-method-compare

3DGS Method Comparison Engine (Router)

Architecture: Axis-driven static/dynamic router. Do NOT try to apply the comparison logic from memory or from this router alone. Always load fragments from disk as described below.

Step 1 — Detect Request Axes

Analyze the user's request to determine axis values:

Axis: category

Axis: depth

If the user does not specify, defaults are: category=all, depth=standard.

Step 2 — Load Required Fragments

Always Load (every invocation)

Read these files from static/:

• static/core-stance.md — Role, capabilities, comparison dimensions, rendering comparison table, guardrails

On-Demand Load (by detected category)

Read the corresponding fragment(s) from static/:

Reference Load (when producing structured output)

• static/output-rules.md — Output format template and comparison rules

Optimization: For depth=quick, load only the relevant category fragment + core-stance. For depth=comprehensive, load all fragments plus output-rules.

Step 3 — Execute Comparison

After loading the required fragments:

1. Apply the comparison dimensions from core-stance.md
2. Use method data from the loaded category fragment(s)
3. Follow output format from output-rules.md if producing tables/reports
4. Observe all guardrails (no fabrication, flag uncertainty, load from disk not memory)

Cross-Skill Routing

This skill focuses on method-level comparison. For related workflows:

• Paper reading/analysis → 3dgs-paper-reader
• Code review/bug detection → 3dgs-code-reviewer
• Experiment design → 3dgs-experiment-planner
• Engineering deployment → 3dgs-engineering-guide
• Visualization/radar charts → 3dgs-visualizer
• CAD/Mesh integration → cad-mesh-3dgs
• Spatial intelligence/agent → 3dgs-spatial-agent

Red Lines

The following are categorical prohibitions. Violating any of these invalidates the output:

• No invented data: Never fabricate benchmark results, timing numbers, or method characteristics not in the loaded reference files. If a value is not found, write "data not available" or "N/A".
• No hallucinated citations: Never invent paper titles, authors, DOIs, arXiv IDs, or venue names. Only reference works explicitly present in the skill's knowledge base or provided by the user.
• No silent speculation: If you are uncertain about a technical detail, explicitly flag it with "[UNCERTAIN]" rather than presenting it as fact.
• No method misattribution: Do not assign features, results, or mechanisms from one method to another. Each method's data is specific to that method.
• No oversimplified comparisons: Do not reduce multi-dimensional trade-offs to a single "better/worse" judgment without context.

Related Skills

• 3dgs-paper-reader — Deep reading and analysis of 3DGS papers (use when you need detailed paper understanding, not just method comparison)
• 3dgs-code-reviewer — Bug detection and code review for 3DGS implementations (use when comparing implementation quality)
• 3dgs-experiment-planner — Experiment design for 3DGS research (use when comparison informs experiment design)
• 3dgs-engineering-guide — Production deployment of 3DGS (use when comparison targets deployment scenarios)
• 3dgs-visualizer — Publication-quality comparison visualizations (use when comparison needs radar charts or timeline plots)
• 3dgs-spatial-agent — Spatial intelligence and embodied reasoning with 3DGS

Guardrail: Do Not Apply From Memory

Do NOT try to apply the comparison logic, method data, or technical details described in this skill from memory. Always read the SKILL.md and referenced files from disk before producing any output. The knowledge base is updated frequently; stale memory may produce outdated, inaccurate, or fabricated results.

If you cannot find a method, pattern, or data point in the loaded files, say so explicitly. Never invent metrics, venue acceptances, or technical features not present in the source data.

If you like it, please star this repo https://github.com/jaccen/Awesome-Gaussian-Skills