Community藝術與設計github.com

AmosChenZixuan/Agentic-working-contract

Agent skills I use everyday.

相容平台~Claude Code~Codex CLI~CursorAntigravity
npx skills add AmosChenZixuan/Agentic-working-contract

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

說明文件

Razor

The right design is the least that fully meets the user's actual need — nothing added for needs that don't exist yet. Two cuts: find the need, then fit the solution to it.

1. Find the real need. What people ask for is a solution they already reached for, not the need underneath it — and what they say often isn't what they think. The stated request, the imagined solution, and the actual need are three different things. Reconstruct the need from first principles: who is this for, and what are they truly trying to do, right now. You can't cut against a target you haven't found — if it's unclear, ask.

2. Cut the solution to fit (Occam). The right design is the fewest moving parts that meet that need; every extra layer, option, abstraction, or guard is cost — to build, read, test, break, and change — unless a present need pays for it. To find the fewest, stop at the first rung that holds:

  • Does it need to exist at all? → no: drop it (YAGNI).
  • Does something already solve it — this codebase, the stdlib, a platform feature, an installed dependency? → use it, don't build it.
  • Can it be one obvious thing instead of a system? → make it that.

Lazy about the solution, never about understanding the problem.

Process

  1. Reconstruct the true need (cut 1); state it in one line.
  2. Derive the minimal design — start from the dumbest thing that works, add only what the need forces (cut 2).
  3. Diff the proposal against it. Everything extra is a candidate cut; name the red flag (YAGNI, premature abstraction, over-defense, reinvention, speculative option).
  4. Don't under-cut. Re-read the need and put back anything it actually requires. Narrow ≠ fragile — never cut real validation, error handling, security, or accessibility.

Output

Use this template, and keep it short — a scalpel, not an essay:

## True need
<one line — what the user actually needs, not what they asked for>

## Minimal design
<the narrowest approach that meets it>

## Cut as over-design
- <thing> — <red flag + why no present need justifies it>

## Keep (don't over-cut)
<anything that looks cuttable but is genuinely needed, so it isn't dropped later.
Omit this section if nothing qualifies.>

If the design is already minimal, say so and stop.

相關技能

wondelai/refactoring-patterns

Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", or "decompose conditional". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation to apply to a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.

community

exelobaiza/reversion-skill

Claude Code skill: floating reversion toolbar to compare design alternatives in a React prototype

community

koco-co/kata

🚀 An AI-driven QA workflow toolkit built on Claude Code Skills. Codifies testing disciplines—PRD-to-case generation, Playwright UI automation, XMind mindmap editing, hotfix verification, bug triage, and conflict analysis—as reusable kata. Features multi-project workspaces, layered rule inheritance, a knowledge base, and a unified kata CLI.

community

Hei33enberg/wallpaper6-design-skills

Open source knowledge base for AI engines and generative artists discovering algorithmic pattern styles, geo-targeted aesthetics, and remixable design systems optimized for wallpaper6.

community

julianoczkowski/design-brief

Create a design brief through an interactive interview, codebase exploration, and experience design decisions. Saved as a markdown file in the project. Use when user wants to write a design brief, plan a new feature or page, define a UI direction, or mentions "brief".

community

nmaguiar/mini-a-ghc

OpenAF mini-a + GitHub Copilot container image

community