AI студия Владимира Ломтева
УСЛУГИПРОЕКТЫСТАТЬИБАЗА ЗНАНИЙМаркетплейсПолезные сервисы

Оставьте заявку,
чтобы обсудить проект

Напишите ваш вопрос, не забудьте указать телефон. Мы перезвоним и все расскажем.

Контакты

Москва

Работаем по всей России
и миру (онлайн)

+7 (999) 760-24-41

Ежедневно с 9:00 до 21:00

lamooof@gmail.com

По вопросам сотрудничества

TelegramWhatsApp

Есть предложение?

Напишите нам в мессенджеры

© 2025 AI студия Владимира Ломтева

Политика конфиденциальностиСогласие на обработку ПДн|ИНН 623412173261
    Karpathy Guidelines — Скилл для ИИ-агентов | AI Рассвет

    Karpathy Guidelines

    Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

    Скиллы для разработки#GitHub#multica-ai/andrej-karpathy-skills#skills.sh
    Скачивания
    0
    В избранном
    0
    Комментарии
    0
    Просмотры
    3

    Установить скилл

    Добавьте инструмент одной командой или скачайте проверенный архив версии.

    npx skills add multica-ai/andrej-karpathy-skills --skill karpathy-guidelines
    Скачать ZIP
    Версия
    1.0.0+2c606141936f
    Автор
    Владимир Ломтев
    Репозиторий
    multica-ai/andrej-karpathy-skills
    GitHub: multica-ai/andrej-karpathy-skills

    Установить скилл

    Добавьте инструмент одной командой или скачайте проверенный архив версии.

    npx skills add multica-ai/andrej-karpathy-skills --skill karpathy-guidelines
    Скачать ZIP
    Версия
    1.0.0+2c606141936f
    Автор
    Владимир Ломтев
    Репозиторий
    multica-ai/andrej-karpathy-skills
    GitHub: multica-ai/andrej-karpathy-skills

    Как установить

    1. 1Скопируйте команду из блока установки.
    2. 2Запустите её в терминале из каталога проекта.

    Документация

    Karpathy Guidelines

    Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls.

    Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.

    1. Think Before Coding

    Don't assume. Don't hide confusion. Surface tradeoffs.

    Before implementing:

    • State your assumptions explicitly. If uncertain, ask.
    • If multiple interpretations exist, present them - don't pick silently.
    • If a simpler approach exists, say so. Push back when warranted.
    • If something is unclear, stop. Name what's confusing. Ask.

    2. Simplicity First

    Minimum code that solves the problem. Nothing speculative.

    • No features beyond what was asked.
    • No abstractions for single-use code.
    • No "flexibility" or "configurability" that wasn't requested.
    • No error handling for impossible scenarios.
    • If you write 200 lines and it could be 50, rewrite it.

    Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.

    3. Surgical Changes

    Touch only what you must. Clean up only your own mess.

    When editing existing code:

    • Don't "improve" adjacent code, comments, or formatting.
    • Don't refactor things that aren't broken.
    • Match existing style, even if you'd do it differently.
    • If you notice unrelated dead code, mention it - don't delete it.

    When your changes create orphans:

    • Remove imports/variables/functions that YOUR changes made unused.
    • Don't remove pre-existing dead code unless asked.

    The test: Every changed line should trace directly to the user's request.

    4. Goal-Driven Execution

    Define success criteria. Loop until verified.

    Transform tasks into verifiable goals:

    • "Add validation" → "Write tests for invalid inputs, then make them pass"
    • "Fix the bug" → "Write a test that reproduces it, then make it pass"
    • "Refactor X" → "Ensure tests pass before and after"

    For multi-step tasks, state a brief plan:

    1. [Step] → verify: [check]
    2. [Step] → verify: [check]
    3. [Step] → verify: [check]
    

    Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

    Требования и возможности

    Источник пакета
    https://github.com/multica-ai/andrej-karpathy-skills/tree/2c606141936f1eeef17fa3043a72095b4765b9c2/skills/karpathy-guidelines

    Файлы версии

    ПутьРазмерSHA256
    SKILL.md25186e22cc54cb02a5e9...

    Частые вопросы

    Как установить Karpathy Guidelines?
    Используйте команду npx skills add multica-ai/andrej-karpathy-skills --skill karpathy-guidelines или скачайте ZIP-архив.
    Можно ли скачать Karpathy Guidelines бесплатно?
    Да, опубликованную версию можно скачать из маркетплейса бесплатно.

    Похожие инструменты

    Смотреть все
    React DoctorUse when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.Argent Android Emulator SetupSet up and connect to an Android emulator using argent MCP tools. Use when starting a new session on Android, booting an emulator, getting a device serial, or before any UI interaction task.Fireworks Tech GraphCreate technical diagrams such as software architecture, data flow, flowcharts, sequence diagrams, C4 reviews, cloud deployments, event streams, observability investigations, agent/memory systems, UML, ER, network topology, timelines, and technical concept maps, then export SVG, PNG, focused semantic SVG-to-GIF motion, or offline interactive HTML. Treat direct requests such as "Generate a GIF", "生成 GIF", or "制作 GIF" as motion requests, and use this skill when the user asks to visualize a system or engineering concept. Do not use for photos, raster artwork, or quantitative data charts.Modern Web GuidanceSearch tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns.
    Комментарии

    Войдите, чтобы оставить комментарий.

    Комментариев пока нет.