菜单
Comprehensive guide to software design based on "A Philosophy of Software Design" by John Ousterhout. Covers complexity management, deep modules, error handling, naming, documentation, general-purpose design, design process, and consistency conventions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | a-philosophy-of-software-design-skills |
| description | Comprehensive guide to software design based on "A Philosophy of Software Design" by John Ousterhout. Covers complexity management, deep modules, error handling, naming, documentation, general-purpose design, design process, and consistency conventions. |
| license | MIT |
| metadata | {"version":"1.0.0","author":"Based on work by John Ousterhout","tags":"software-design, complexity, architecture, best-practices, code-quality"} |
A comprehensive guide to software design based on "A Philosophy of Software Design" by John Ousterhout.
This skill provides practical guidance for writing simple, maintainable code that minimizes complexity. It covers eight essential areas of software design:
Use this skill when:
The fundamental problem in software design is managing complexity. This skill teaches you to:
README.md - Complete overview and integration guideQUICK-REFERENCE.md - One-page cheat sheetINSTALLATION.md - Installation and usage guide01-complexity-management.md - Core philosophy and strategic programming02-deep-modules.md - Interface design and information hiding03-error-handling.md - Eliminating exceptions and special cases04-naming-obviousness.md - Naming conventions and code clarity05-comments-documentation.md - Effective documentation practices06-general-purpose-design.md - Building flexible, reusable code07-design-process.md - Design methodology and workflow08-consistency-conventions.md - Standards and conventionsEach skill includes:
Red Flags (signs of complexity):
Design Principles:
Based on "A Philosophy of Software Design" by John Ousterhout, published by Yaknyam Press.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Write property-based tests using Hegel across Rust, Go, C++, and TypeScript projects. Use this skill whenever the user asks to write tests, add test coverage, or improve testing for functions, modules, or libraries — especially when the code has properties like round-trips, invariants, or contracts that hold across many inputs. Also triggers on: "property-based tests", "PBT", "hegel", "fuzz", "generative tests", "randomized testing", "test with random inputs", "shrinking", or when existing tests use proptest, quickcheck, rapid, gopter, rapidcheck, or fast-check.
Applies the Diataxis framework to create or improve technical documentation. Use when being asked to write high quality tutorials, how-to guides, reference docs, or explanations, when reviewing documentation quality, or when deciding what type of documentation to create. Helps identify documentation types using the action/cognition and acquisition/application dimensions.
This document instructs Claude Code to use `jj` (Jujutsu) instead of `git` for version control operations. jj is a Git-compatible VCS that provides a simpler mental model and powerful history editing.
Nullables — testing technique alternative to using mocking libraries. Use when writing unit tests, when code touches external I/O or state (HTTP, databases, files, clock, random) anywhere in its dependency chain, when making a system testable, or when tests are slow or flaky.
Implement observability using the Wide Events (Canonical Log Lines) pattern. Instead of scattering logs throughout a request, accumulate high-cardinality context and emit a single, highly-dimensional structured event per service boundary.