CZ

corey924/zerospec

Developer tools

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기

65 stars 품질 58 트렌드 18MIT

ZeroSpec is a zero-dependency Markdown framework that helps AI agents understand your repository structure, rules, and source of truth before coding.

개요

If you've shipped features with Copilot, Cursor, Claude Code, or similar tools on a real codebase, these situations are familiar: - The agent edits the wrong module because navigation docs have drifted from the actual structure - The code lands in the right file but quietly breaks architecture rules scattered across several documents - The response references a deprecated API, an old version, or an interface that is no longer the source of truth - You're maintaining separate guidance for each tool, and they are slowly diverging In many teams, these are less pure model failures and more context gaps — the project knowledge agents need is not in places they can reliably find. ZeroSpec puts that context in a predictable set of files before the agent starts working. Plain Markdown, no new runtime, no platform lock-in. - In the Stack Overflow Developer Survey 2025, 66% said a major frustration is getting answers that are almost right, but not quite, and 45.

README

원문 README의 일부입니다. 원문 보기.

ZeroSpec

ZeroSpec is a zero-dependency Markdown baseline that gives AI coding agents the project context they need — architecture rules, module navigation, and source of truth — before they start editing files.

🌐 Traditional Chinese (zh-TW)

Version: v0.5.3 Status: Active


What Problem Does ZeroSpec Solve?

If you’ve shipped features with Copilot, Cursor, Claude Code, or similar tools on a real codebase, these situations are familiar:

  • The agent edits the wrong module because navigation docs have drifted from the actual structure
  • The code lands in the right file but quietly breaks architecture rules scattered across several documents
  • The response references a deprecated API, an old version, or an interface that is no longer the source of truth
  • You’re maintaining separate guidance for each tool, and they are slowly diverging

In many teams, these are less pure model failures and more context gaps — the project knowledge agents need is not in places they can reliably find.

ZeroSpec puts that context in a predictable set of files before the agent starts working. Plain Markdown, no new runtime, no platform lock-in.

Why This Matters

These are not edge cases.

  • In the Stack Overflow Developer Survey 2025, 66% said a major frustration is getting answers that are almost right, but not quite, and 45.2% said debugging AI-generated code is more time-consuming.
  • In METR’s 2025 randomized controlled trial of experienced open-source developers, participants completed tasks 19% slower when AI tools were allowed in that specific setting.
  • AGENTS.md has become a common open guidance-file convention across AI-assisted development workflows, which suggests the ecosystem is converging on predictable context files rather than tool-specific magic.

Those sources do not prove that every team needs ZeroSpec. They do support a simpler point: context quality is a practical part of AI-assisted development, not just a prompting preference.

As Simon Willison notes in Hallucinations in code are the least dangerous form of LLM mistakes, giving models better context is often more useful than treating every failure as a model-selection problem.

Anthropic’s engineering team frames this broadly as Context Engineering — the discipline of curating the smallest set of high-signal tokens that lets an agent work reliably. ZeroSpec is one practical implementation of that principle at the repo level.

What ZeroSpec Does

ZeroSpec standardizes the minimum repo context agents usually need before they start coding:

GitHub에서 전체 README 보기

추천 도구

다른 키워드를 입력하거나 필터를 제거해 보세요.

설치

npx skillfish add corey924/zerospec
MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →