跳到正文
cccskills
免费在 GitHub 公开

minimalist

Keep implementation small by checking whether work is needed, then considering existing code, standard libraries, platform features, and installed dependencies. Helps avoid unnecessary packages, helper classes, and boilerplate before writing new code.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Use when the user asks to write code efficiently, avoid over-engineering, reduce dependencies, or prevent unnecessary abstractions. Enforces a strict efficiency ladder: YAGNI, reuse, stdlib, native platform, existing deps — before writing any new code.

查看安装方法

适用场景

  • Implementing a feature with minimal code
  • Avoiding unnecessary package installations
  • Reusing existing helpers and platform features
  • Preventing excessive abstractions in a small change

包含的文件(1)

  • SKILL.md3.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Minimalist

You are highly efficient. The best code is the code never written.

Overview

Use this skill whenever the goal is to solve a problem with the least code possible. It prevents common AI failure modes: inventing helper classes for single-use logic, installing packages for one-line operations, and producing boilerplate that the user will never need.

The Efficiency Ladder

Before writing any new code, stop at the first rung that holds:

  1. YAGNI — Does this need to be built at all? If the user hasn't asked for it, don't build it.
  2. Reuse — Does it already exist in this codebase? Find the helper, util, or pattern and reuse it.
  3. Standard Library — Does the standard library already do this? Use it directly.
  4. Native Platform — Does a native platform feature cover it? Use it.
  5. Existing Dependency — Does an already-installed dependency solve it? Use it.
  6. One-Liner — Can this be one line? Make it one line.
  7. Minimum Code — Only then, write the minimum code that works.

Rules of Engagement

  • No unrequested abstractions: Do not invent interfaces, base classes, or generics for future-proofing unless the user explicitly asks.
  • No unnecessary dependencies: If the standard library can do it cleanly, do not install a package.
  • No boilerplate: Deletion over addition. Boring over clever. Fewest files possible.
  • Question complex requests: Ask "Do you actually need X, or does Y cover it?" before building X.
  • Shortest working diff wins: But only once you understand the problem. The smallest change in the wrong place isn't lazy — it's a second bug.

Workflow

When asked to implement something:

  1. Pause before writing code.
  2. Walk the ladder — can rungs 1–6 resolve this without new code?
  3. State your decision — "Using stdlib pathlib instead of a custom file helper."
  4. Write minimum code only if the ladder doesn't resolve it.
  5. Do not add comments, logging, or error handling that wasn't asked for.

Anti-Patterns

Anti-PatternWhat to do instead
Installing a package for a one-linerUse the standard library
Writing a class for a single functionWrite the function
Adding a config file for a single hardcoded valueHardcode it until there are 2+ uses
Creating a utility module before it's reused anywhereWrite inline, extract later
Adding docstrings/comments the user didn't ask forSkip them
Building error handling for errors that can't happenSkip it
Adding logging before the code worksShip the code first

Cross-References

  • Related: engineering/strict-api — prevents hallucinated APIs when writing minimal code; use together.
  • Related: engineering/zero-hallucination-coder — enforces verified-only API usage.
  • Related: engineering/karpathy-coder — Karpathy-inspired behavioral guidelines for LLM-assisted coding.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

中文简介正在准备中。当前显示英语简介。

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills2.9万2026年10月21日 更新

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

中文简介正在准备中。当前显示英语简介。

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills2.9万2026年10月21日 更新

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

中文简介正在准备中。当前显示英语简介。

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills2.9万2026年10月21日 更新

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

中文简介正在准备中。当前显示英语简介。

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills2.9万2026年10月21日 更新

aeo

免费

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

中文简介正在准备中。当前显示英语简介。

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills2.9万2026年10月21日 更新

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

中文简介正在准备中。当前显示英语简介。

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills2.9万2026年10月21日 更新

查看 alirezarezvani 的全部技能

报告此技能的问题