Designing Before Coding

Design in pseudocode first, iterate approaches, then translate to code

43 stars 26 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add obra/clank --skill Designing Before Coding
Manual install
git clone --depth 1 https://github.com/obra/clank.git /tmp/clank
mkdir -p ~/.claude/skills
cp -r /tmp/clank/skills/coding/designing-before-coding ~/.claude/skills/Designing-Before-Coding

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Designing Before Coding

## Overview

Write the design in pseudocode BEFORE writing implementation code. Iterate through multiple approaches in pseudocode, pick the best, THEN translate to code.

**Core principle:** Once you start coding, you get emotionally involved with your code and it becomes harder to throw away a bad design. Design is cheap to change; code is expensive.

**Violating the letter of the rules is violating the spirit of the rules.**

## When to Use

Use for ANY programming task beyond trivial one-liners:
- New features or functionality
- Non-trivial bug fixes
- Refactoring
- Any routine longer than ~5 lines
- When you're unsure how to proceed
- When solution feels complex

**Red flags that you need this:**
- Jumping straight to implementation code
- "Just one more compile" syndrome
- Coding yourself into a corner
- Losing train of thought mid-implementation
- Forgetting to write parts of a routine
- Staring at screen not knowing where to start
- Code feels hack-y or patched together

**Don't skip when:**
- Under time pressure (designing first is FASTER than debug cycles)
- Problem seems simple (simple problems benefit from design too)
- You're confident you know the solution (overconfidence causes mistakes)

## The Process

### Step 1: Check Prerequisites

Before any design work:
- [ ] Is the job well-defined?
- [ ] Does it fit cleanly into overall design?
- [ ] Is it actually required by the project?
- [ ] What information will this routine hide?
Read the full skill on GitHub

Details

Skill name
Designing Before Coding
Repository
obra/clank
Path
skills/coding/designing-before-coding/SKILL.md
Repo updated
9 October 2025

FAQ

What does the Designing Before Coding skill do?

Design in pseudocode first, iterate approaches, then translate to code

How do I install the Designing Before Coding skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add obra/clank --skill Designing Before Coding. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Designing Before Coding popular?

It lives in obra/clank, which has 43 GitHub stars and 26 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.