software-paradigms-karpathy

Explain Karpathy's three software paradigms and map tasks to Software 1.0, 2.0, and 3.0.

2|3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jona/ycombinator-skills --skill software-paradigms-karpathy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-paradigms-karpathy
Source: https://github.com/jona/ycombinator-skills/tree/main/skills/software-paradigms-karpathy
Command: npx skills add https://github.com/jona/ycombinator-skills --skill software-paradigms-karpathy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users understand how software is evolving by framing the evolution as three paradigms: Software 1.0 (traditional code), Software 2.0 (neural network weights), and Software 3.0 (LLM prompts). It clarifies when to apply each paradigm and why prompt-based programming represents a new form of software design.

Core Features & Use Cases

  • Clear explanation of the 1.0/2.0/3.0 distinctions with concrete examples.
  • Paradigm-aware task mapping: when to use traditional code, neural networks, or prompts.
  • Practical guidance for designing hybrid systems (e.g., orchestrating 1.0/2.0/3.0 components in a single app).

Quick Start

Ask: Explain a minimal AI assistant architecture using Software 1.0 for orchestration, Software 2.0 for perception, and Software 3.0 for prompts.

Frequently Asked Questions about software-paradigms-karpathy

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

FAQPage Schema
What are Karpathy's software 1.0, 2.0, and 3.0 paradigms?

Karpathy's software paradigms define programming evolution: Software 1.0 uses traditional code, Software 2.0 uses neural network weights, and Software 3.0 uses LLM prompts. This framework clarifies how prompt-based programming represents a new form of software design.

How do I map tasks to the right software paradigm?

Map tasks to software paradigms by evaluating requirements: use traditional code for deterministic logic, neural network weights for perception tasks, and LLM prompts for cognitive or generative tasks. This mental model guides precise architecture decisions and task routing.

When should I use LLM prompts versus traditional code?

Use LLM prompts when tasks require cognitive reasoning or language generation, and traditional code for deterministic orchestration. The software 3.0 paradigm treats prompts as programming, ideal for AI-enabled product design where explicit rules are difficult to define.

How do I design a hybrid AI assistant architecture?

Design hybrid AI architectures by orchestrating Software 1.0 for control flow, Software 2.0 for perception, and Software 3.0 for prompt-based reasoning. This combines deterministic logic, trained models, and LLM prompts to build robust AI-enabled products.

Why are LLM prompts considered a new software paradigm?

LLM prompts represent a new software paradigm because they function as programming instructions for AI models. In Software 3.0, prompts replace explicit code logic with natural language directives, shifting how developers design and execute application architecture.