The systematic process of collecting, organizing, analyzing, connecting, retrieving, and applying references to improve the quality of decisions made during production.
Reference Engineering is a discipline focused on references as its primary object.
Not knowledge. Not research. Not documentation. Not inspiration.
References — the specific collected materials that practitioners use to inform decisions before and during production. Reference Engineering is the discipline of working with those materials systematically.
Most practitioners collect references. Very few engineer them.
The difference is not effort — it is methodology. A reference collector asks: "What should I save?" A reference engineer asks: "What decisions does this project require, and what reference will inform each one?"
This repository is the canonical free library for Reference Engineering across every discipline that has a production phase. It defines the methodology, proves it with examples, and provides the tools to practice it.
Reference Engineering was developed by Atharva Patil (Northbyte Studios, Navi Mumbai, India) in 2026. See MANIFESTO.md for the origin and CITATION.md to cite this work.
- References are assets
- Context is more valuable than quantity
- Organization precedes automation
- Retrieval is as important as collection
- Relationships matter more than storage
- Knowledge compounds
- Systems outperform memory
- Reference Engineering is optional
- The discipline is tool-agnostic
- The discipline is domain-agnostic
Seven layers. Build bottom-up. The upper layers are only useful once the lower layers are established.
▲
/|\
/ | \
/ 7 \ PRECISION DETAIL
/-------\ Close-range, fine-grain, craft-level
/ 6 \ BEHAVIOR & CONSTRUCTION
/ \ How it is made, how it acts under conditions
/-------------\
/ 5 \ CONTEXTUAL CONDITIONS
/ \ How it reads in its actual environment
/-----------------\
/ 4 \ GOVERNING RULES
/ \ Extracted parameters — written, not vibes
/-----------------------\
/ 3 \ STAGE-APPROPRIATE REFERENCE
/ \ Right reference for the current phase
/-----------------------------\
/ 2 \ SCALE & PROPORTION
/ \ Real dimensions, relational anchors
/-----------------------------------\
/ 1 \ FUNCTION & CONTEXT
/ \ What it does, where it lives
/-------------------------------------------\
Most reference collections have too much at the top and nothing at the foundation. The gaps at the bottom hurt more than the abundance at the top helps.
Full model: core/REFERENCE_PYRAMID.md
The canonical theoretical foundation. Cite theory/REFERENCE_ENGINEERING_THEORY.md when referencing this discipline.
| Document | Contents |
|---|---|
theory/REFERENCE_ENGINEERING_THEORY.md |
Complete unified theory — definition, principles, all models |
theory/REFERENCE_HIERARCHY.md |
Credibility model — Primary, Secondary, Tertiary tiers |
theory/REFERENCE_LIFECYCLE.md |
How reference briefs age, version, and compound |
theory/REFERENCE_RELATIONSHIPS.md |
How references relate to each other — the relationship model |
theory/REFERENCE_DECISION_MAKING.md |
How reference quality maps to decision quality |
theory/REFERENCE_MEMORY.md |
Compounding, personal libraries, institutional memory |
Operational documents — use these during production.
| Document | Contents |
|---|---|
core/WHAT_IS_REFERENCE_ENGINEERING.md |
Definition, boundary, six operations, navigation |
core/REFERENCE_PYRAMID.md |
Seven-layer structural model with domain cross-reference |
core/REFERENCE_SYSTEM.md |
How the framework connects across disciplines |
core/REFERENCE_MISTAKES.md |
Ten named failure modes with fixes and production costs |
core/REFERENCE_CHECKLIST.md |
Universal printable pre-production checklist |
core/SOURCES.md |
Reference sources organized by Pyramid layer |
core/GLOSSARY.md |
All framework terms defined precisely |
Worked demonstrations of the complete Reference Engineering workflow across five disciplines.
| Example | Discipline | Key Skill Demonstrated |
|---|---|---|
examples/ui-redesign/ |
UI/UX | Extracting written rules from competitor analysis |
examples/game-environment/ |
Game Art / 3D | Full seven-layer coverage, primary reference sourcing |
examples/brand-identity/ |
Brand Design | Converting subjective briefs into measurable parameters |
examples/character-design/ |
Character Art | Full lifecycle — brief v1 → v2, all seven layers |
examples/architecture/ |
Architecture | Multi-domain reference management |
Read examples/character-design/ for the most complete lifecycle demonstration.
Retroactive analysis of real projects through the Reference Engineering lens.
| Case Study | Project | Key Finding |
|---|---|---|
case-studies/kanvaz-ui-v2/ |
Kanvaz desktop app | Technical failures are often reference failures in disguise |
Format for new case studies: case-studies/FORMAT.md
Field-specific adaptations of the framework.
| Discipline | Status |
|---|---|
disciplines/3d-art/ |
✅ v1.0.0 |
disciplines/web-dev/ |
✅ v1.0.0 |
disciplines/app-dev/ |
✅ v1.0.0 |
disciplines/vfx/ |
✅ v1.1.0 |
disciplines/game-dev/ |
✅ v1.1.0 |
disciplines/ui-ux/ |
✅ v1.1.0 |
New to Reference Engineering:
core/WHAT_IS_REFERENCE_ENGINEERING.md— what it is, what it is not, and why the boundary mattersMANIFESTO.md— the philosophy and origincore/REFERENCE_PYRAMID.md— the seven layers- One example from
examples/closest to your discipline core/REFERENCE_CHECKLIST.md— run this before your next project
For the complete theory: theory/REFERENCE_ENGINEERING_THEORY.md
Reference Engineering is distinct from adjacent disciplines:
| Discipline | Manages | Goal |
|---|---|---|
| Reference Engineering | References | Better decisions through better reference practice |
| Knowledge Management | Knowledge assets | Organizational learning |
| Research Methodology | Investigation processes | Discovery of new information |
| Documentation | Recorded information | Reliable future access |
| Moodboarding | Aesthetic communication | Shared creative direction |
Reference Engineering intersects with all of these. It is not replaced by any of them.
The first AI skill pack implementing Reference Engineering is available today:
3d-ref-skills v3.1.0 — 9 skills covering the full 3D pre-production reference workflow
→ github.com/p4inz-code/3d-ref-skills
Compatible with Claude Code, Cursor, Codex, Gemini.
I am an animation student and indie developer in Navi Mumbai, India. In 2026, while building systematic reference workflows for 3D production and game development, I found that the methodology underneath what I was doing had no name, no documentation, and no canonical resource. Every discipline had the same reference problem. None of them had a shared language for it.
This repository is the attempt to provide that language.
— Atharva Patil, Northbyte Studios
Cite this work: CITATION.md
Prior art record: TRADEMARK_NOTE.md
See CONTRIBUTING.md and DISCIPLINE_TEMPLATE.md.
Community: discord.gg/XFF5nV53ZJ
MIT — see LICENSE
Reference Engineering — coined by Atharva Patil, Northbyte Studios, 2026
I make these tools on my own and keep them free. If one helped you, you can chip in by UPI. Any amount.
9321614988@jio
On your phone? Open the donation page.
Outside India, or prefer a card?
