Learning By Making logo

Learning By Making

Community
Dragoon0x
learning-by-making

Build taste through volume of output, deliberate failure, and speed. Taste cannot be developed by watching. It's sharpened by making, failing, and making again. Use when designing practice routines, breaking through creative blocks, or helping someone move from analysis to execution.

Overview

PublisherDragoon0x
Repositorytaste-skills
Skill namelearning-by-making
Stars
6
Forks
3
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Dragoon0x on GitHub. Read the source before you install it.

Installation

Install the Learning By Making AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Dragoon0x/taste-skills/tree/main/skills/evaluation/learning-by-making
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Dragoon0x/taste-skills.git /tmp/taste-skills
mkdir -p .claude/skills
cp -r /tmp/taste-skills/skills/evaluation/learning-by-making .claude/skills/learning-by-making
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Learning By Making in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Learning By Making on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Learning By Making is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Learning by Making

Taste is sharpened by making, failing, and making again. Not by watching.

How to use

  • /learning-by-making Apply making-as-practice constraints to creative development in this conversation.

Constraints

The Volume Principle

  • MUST prioritize quantity of finished work over quality of any single piece
  • A designer who ships 50 projects in a year learns more than one who perfects 3
  • MUST finish things. Unfinished work teaches you how to start. Finished work teaches you how to decide.
  • NEVER let "it's not ready" become permanent. Set a deadline. Ship it. Learn from the gap between what you shipped and what you wished you'd shipped.

Deliberate Practice Formats

  • Speed rounds (15-30 min): Redesign a real product screen. No research. No moodboard. Just instinct. What comes out reveals your current taste baseline.
  • Style copies (60 min): Recreate someone else's design decision-for-decision. Not pixel-copying. Understanding why every choice was made by making it yourself.
  • Constraint challenges (45 min): One typeface, one color. 320px width only. Zero images. 10 words max per screen. Constraints strip away crutches and expose your actual judgment.
  • Fake briefs (2-4 hours): Invent a product. Design it end-to-end. Landing page, onboarding, core screen, settings. The act of making complete decisions across a whole product builds holistic taste.
  • Remix exercises (30 min): Take something you made last month. Redesign it from scratch without looking at the original. Compare the two. The delta is your growth.

Rules of Making

  • MUST make things even when they're bad. Especially when they're bad. Bad work with reflection teaches more than good work by accident.
  • MUST reflect after making. "What worked? What didn't? What would I change with 2 more hours?" Without reflection, volume is just busywork.
  • MUST vary the format. If you only design landing pages, your taste is landing-page-shaped. Design dashboards, mobile apps, emails, posters, packaging, signage.
  • SHOULD share work publicly. The vulnerability of showing imperfect work accelerates growth because it forces you to articulate your decisions.

The Failure Requirement

  • MUST reframe failure as data. A design that doesn't work tells you exactly what you don't understand yet.
  • SHOULD keep a failure archive. Save your worst work. Revisit it quarterly. When you can articulate why it's bad in precise language, you've grown.
  • NEVER delete bad work. It's your most honest record of where you were.

Anti-Patterns

  • Analyzing 10 products for every 1 you make (consumption-to-creation ratio is inverted)
  • Only making things in your comfort zone (safe projects don't stretch taste)
  • Abandoning projects when they get hard (the hard part is where the learning is)
  • Waiting for the perfect brief to start making (the brief doesn't matter, the reps do)
  • Treating practice work as throwaway (practice work should be finished and reflected on)

Frequently asked questions

What does the Learning By Making AI skill do?

Build taste through volume of output, deliberate failure, and speed. Taste cannot be developed by watching. It's sharpened by making, failing, and making again. Use when designing practice routines, breaking through creative blocks, or helping someone move from analysis to execution.

Why use Learning By Making on TypingMind?

Because you install it once and use it with any model. Learning By Making is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Learning By Making in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Dragoon0x/taste-skills/tree/main/skills/evaluation/learning-by-making. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Learning By Making?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Learning By Making?

As many as you like. As long as a model supports skills, you can use Learning By Making with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Learning By Making AI skill free?

Yes. It is published on GitHub by Dragoon0x under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇