Repository navigation
chore(docs): update README.md for consistent format and to avoid duplication - #23939
Conversation
…mp causing duplicate info
…h these are exceptions to the general format
| 5. `## Usage`: only one fenced, basic getting-started code example (TypeScript or a framework component with TypeScript). | ||
| 6. A suitable docs link using `See the [<package title> documentation](<url>) for more information.` If none clearly fits, use 1–2 related docs links with custom phrasing. | ||
|
|
||
| You must not include anything else in the readme. Any additional documentation belongs in `content/`. |
There was a problem hiding this comment.
This rule contradicts the READMEs this PR produces. 45 of them keep a ## Skill for Coding Agents section between Setup and Usage (e.g. packages/anthropic/README.md:13, packages/openai/README.md:14, packages/gateway/README.md:11), and the PR description says keeping it is intentional. An agent following this skill literally will delete that section on the next edit, and new provider READMEs will leave it out.
Can we add it to the ordered list as an optional item between Setup and Usage, with the exact block, and say which packages get it (provider packages)?
Related: skills/add-provider-package/SKILL.md:164 still says to write the README with "installation, authentication, configuration, supported models, and basic usage", which this format now forbids. Pointing it at edit-package-readme would keep the two skills from pulling in opposite directions.
Background
Package
README.mdfiles should be minimal starting points. Detailed documentation already lives incontent/; duplicating it in READMEs risks drift.Summary
edit-package-readmeskill to capture the conventions.ai(also the repository README)codemod(internal tooling)provider, andprovider-utils(internal foundations)Checklist
pnpm changesetin the project root)Future Work
Update the
angularREADME once a suitable documentation page exists. It remains untouched for now, but is not a format exception.