cite-algorithm

Locates canonical papers and license-compatible reference implementations before implementing non-trivial rendering algorithms.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/HendrikGC02/Astroray --skill cite-algorithm-hendrikgc02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cite-algorithm
Source: https://github.com/HendrikGC02/Astroray/tree/main/.claude/skills/cite-algorithm
Command: npx skills add https://github.com/HendrikGC02/Astroray --skill cite-algorithm-hendrikgc02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing physics, sampling, or numerical algorithms from scratch risks reinventing worse solutions and losing provenance for citations. This Skill enforces a research-first gate so every non-trivial algorithm in Astroray is grounded in a canonical paper and a license-compatible reference implementation before any code is written. ## Core Features & Use Cases - Provenance gate: Defines what counts as non-trivial (MIS, ReSTIR, BSDFs, spectral upsampling, GR integrators, synchrotron emission) versus trivial textbook math, so the rule applies per algorithm. - Structured research workflow: Searches for the original paper, verifies license compatibility (Apache-2.0, BSD, MIT, MPL-2.0, GPL with caution), and writes a templated research note to .astroray_plan/docs/. - In-code citation blocks: Generates standardized header comments with DOI/arXiv, reference repo commit, mirrored file paths, and SPDX license identifiers. - Use Case: Before porting Cycles' principled hair BSDF, run the skill to produce a research note capturing the paper, the Cycles commit and file paths mirrored, and the citation block to paste into the new translation unit. ## Quick Start Ask the AI to run the cite-algorithm skill before implementing a named technique such as ReSTIR DI or Kerr-Schild coordinates.

Frequently Asked Questions about cite-algorithm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I cite a paper and reference implementation before writing rendering code?▼

State the algorithm in one sentence, search for the original paper capturing title, authors, year, and DOI or arXiv ID, then find a license-compatible implementation and record its repo, commit, and mirrored file paths. Write a research note to .astroray_plan/docs/ and add a citation header block to the code.

Which algorithms require research notes before implementation?▼

Non-trivial algorithms require the gate: sampling distributions like MIS and ReSTIR, BSDFs beyond Lambertian plus Schlick, spectral upsampling, GR integrators and Kerr transforms, synchrotron emission, denoising, and advanced tone mapping. Textbook math like Halton sequences or Schlick Fresnel is exempt.

What open source licenses are compatible for reference implementations?▼

Apache-2.0, BSD-2/3-Clause, MIT, MPL-2.0, and public domain or CC0 are accepted directly. GPLv2 and GPLv3 require checking against Astroray's LICENSE first, while proprietary, research-only, non-commercial, or unstated licenses are rejected.

Can I implement an algorithm first and add citations later?▼

No, implementing first is an explicit anti-pattern because provenance becomes guesswork and citation blocks end up wrong. The research note and citation must exist before the implementation, and the rule applies per algorithm regardless of change size.

What goes into the research note template?▼

The note captures the paper metadata, the reference repo with commit and license rationale, the equations and data structures reproduced, intentional differences from the reference, what is deliberately not taken, the Astroray integration plan with files and tests, and open questions.