S
SVN11X/standards
How SVN11X repositories are organized, documented and reviewed, by people and by any AI tool
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Install command from the repository
pip install pyyaml
Parsed from the README we fetched on 2026-11-10; we have not executed it.
This is the install method the repository states, not an MCP client config, so no JSON is generated.
Key names differ by client: Clients & CLI
- Star count
- 0 ★ · SVN11X/standards · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-11 · last seen 2026-11-14 · seen 4× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
- Install
pip install pyyaml
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
pip install pyyaml. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
SVN11X/standards;first catalogued 2026-11-11;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# standards
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
How SVN11X repositories are organized, documented and reviewed. One source of truth for people and for any AI tool (Claude, Codex, Copilot, Cursor, Gemini).
## Read first
SETUP.md sets up the standard with any AI tool. docs/how-it-works.md explains how this repository works inside. The docs/ folder explains the standard in order: 000-philosophy.md, 001-profiles.md, 002-intent.md, 003-autopilot-and-hooks.md, 004-radar.md, 005-verification-and-orchestration.md and 006-model-analyzer.md.
## How a repository uses it
Each repository carries three things:
.standard.yml declares the profile, the answers to the setup questions and the pinned version of this standard.
AGENTS.md is generated from this repo and from the repository's own docs/goals.md. AI tools read it at the start of every session. People can read it too.
.github/workflows/standard.yml calls the shared check in this repo on every push and pull request.
Each repository also keeps its intent in docs/: goals, glossary, assumptions, decisions and specs. The owner writes the goals. AI tools may ask, transcribe and format, never invent.
## Profiles
A profile describes what a repository produces.
web: sites and apps used in a browser.
software: programs and libraries.
data-ai: data pipelines, analysis and machine learning.
hardware: electronics, firmware and mechanical parts.
docs: documents and research.
infra: infrastructure defined as code.
A mixed repository picks a main profile and declares parts. A part is a subfolder that follows another profile and has its own nested AGENTS.md.
Every profile has three kinds of practice. Fixed rules always apply. Some techniques are allowed only with a reason written in docs/decisions/. Everything else is a setup question, answered once and stored in .standard.yml.
## Start a new repository
From a template: open template- on GitHub and click "Use this template". Then answer the setup questions, with the repo-setup skill in Claude or with prompts/intake.md in any other AI.
From the command line:
bash
pip install pyyaml
python scripts/standard.py init ../my-site --profile web --name my-site --interactive
## Skills
The repo-setup and code-review skills are published at SVN11X/skills, which is also a plugin marketplace: install it once in claude.ai or Claude Code and turn on automatic sync. The skills read the rules from this repository at the version each repository pins, so most changes here reach them without republishing. prompts/global-instructions.md has the text that tells each tool to use them.
## Adopt the standard in an existing repository
The check fails while files sit outside the layout: loose files at the root, undeclared folders and undeclared hidden folders are errors. To fix a messy repository:
1. python scripts/standard.py migrate --profile writes docs/migration-plan.yml with every proposed move, the decisions left to the owner, and the lines that mention each moved file. Nothing moves yet.
2. Review and edit the plan, for example to translate names to English.
3. python scripts/standard.py migrate --apply moves the files with git mv and adds the missing standard files.
4. Fix the listed references, resolve the decisions, then run agents and check.
## Read first
SETUP.md sets up the standard with any AI tool. docs/how-it-works.md explains how this repository works inside. The docs/ folder explains the standard in order: 000-philosophy.md, 001-profiles.md, 002-intent.md, 003-autopilot-and-hooks.md, 004-radar.md, 005-verification-and-orchestration.md and 006-model-analyzer.md.
## How a repository uses it
Each repository carries three things:
.standard.yml declares the profile, the answers to the setup questions and the pinned version of this standard.
AGENTS.md is generated from this repo and from the repository's own docs/goals.md. AI tools read it at the start of every session. People can read it too.
.github/workflows/standard.yml calls the shared check in this repo on every push and pull request.
Each repository also keeps its intent in docs/: goals, glossary, assumptions, decisions and specs. The owner writes the goals. AI tools may ask, transcribe and format, never invent.
## Profiles
A profile describes what a repository produces.
web: sites and apps used in a browser.
software: programs and libraries.
data-ai: data pipelines, analysis and machine learning.
hardware: electronics, firmware and mechanical parts.
docs: documents and research.
infra: infrastructure defined as code.
A mixed repository picks a main profile and declares parts. A part is a subfolder that follows another profile and has its own nested AGENTS.md.
Every profile has three kinds of practice. Fixed rules always apply. Some techniques are allowed only with a reason written in docs/decisions/. Everything else is a setup question, answered once and stored in .standard.yml.
## Start a new repository
From a template: open template- on GitHub and click "Use this template". Then answer the setup questions, with the repo-setup skill in Claude or with prompts/intake.md in any other AI.
From the command line:
bash
pip install pyyaml
python scripts/standard.py init ../my-site --profile web --name my-site --interactive
## Skills
The repo-setup and code-review skills are published at SVN11X/skills, which is also a plugin marketplace: install it once in claude.ai or Claude Code and turn on automatic sync. The skills read the rules from this repository at the version each repository pins, so most changes here reach them without republishing. prompts/global-instructions.md has the text that tells each tool to use them.
## Adopt the standard in an existing repository
The check fails while files sit outside the layout: loose files at the root, undeclared folders and undeclared hidden folders are errors. To fix a messy repository:
1. python scripts/standard.py migrate --profile writes docs/migration-plan.yml with every proposed move, the decisions left to the owner, and the lines that mention each moved file. Nothing moves yet.
2. Review and edit the plan, for example to translate names to English.
3. python scripts/standard.py migrate --apply moves the files with git mv and adds the missing standard files.
4. Fix the listed references, resolve the decisions, then run agents and check.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/svn11x-standards/)
- Source
- github · https://github.com/SVN11X/standards
- Browse by field
- Open source
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.