Move the Google style skill to the Agent Skills standard path.

Move the Google style skill to the Agent Skills standard path.

The skill now lives in `.agents/skills/google-developer-style/SKILL.md` with
Agent Skills front matter and works across agents, not just Devin. The
`AGENTS.md` Communication style section points to that file.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

renamed .agents/skills/google-developer-style/SKILL.md
modified AGENTS.md

Diff

2 files changed, +11 -6

---
name: google-developer-style
description: Apply the Google Developer Documentation Style Guide to user-facing docs, READMEs, AGENTS.md, and commit messages. Use when writing or reviewing prose in this repo.
---

# Google Developer Documentation Style

Use this skill when writing or reviewing user-facing documentation, READMEs, `AGENTS.md`, and commit messages for OpenAgents.
Use this skill when you write or review user-facing documentation, READMEs, `AGENTS.md`, and commit messages for OpenAgents.

## How to invoke
## How to use this skill

Apply these rules to the text you are about to produce or edit. When a rule would make something less clear, break the rule and stay consistent.
Apply these rules to the text you produce or edit. When a rule would make something less clear, break the rule and stay consistent.

## Voice and tone


## Language and grammar

- Use active voice. Make clear who performs the action.
- Use second person (`you`) for the reader.
- Use second person ("you") for the reader.
- Use present tense.
- Use standard American spelling and punctuation.
- Put conditions before instructions, not after.


## Communication style

All text in this repo — docs, README, `AGENTS.md`, commit messages, and agent responses — follows the [Google Developer Documentation Style Guide](https://developers.google.com/style). When writing or reviewing text, invoke the `google-developer-style` skill.
All text in this repo — docs, README, `AGENTS.md`, commit messages, and agent responses — follows the [Google Developer Documentation Style Guide](https://developers.google.com/style). When writing or reviewing text, read the `google-developer-style` skill at `.agents/skills/google-developer-style/SKILL.md`.

- Write in active voice and address the reader as `you`.
- Use sentence case for all headings and titles.

  - You must import the vendor deps into app.js and app.css to use them
  - **Never write inline <script>custom js</script> tags within templates**

### UI/UX & design guidelines
### UI and UX design guidelines

- **Produce world-class UI designs** with a focus on usability, aesthetics, and modern design principles
- Implement **subtle micro-interactions** (e.g., button hover effects, and smooth transitions)

	1	+	`---`
	2	+	`name: google-developer-style`
	3	+	`description: Apply the Google Developer Documentation Style Guide to user-facing docs, READMEs, AGENTS.md, and commit messages. Use when writing or reviewing prose in this repo.`
	4	+	`---`
	5	+
1	6		`# Google Developer Documentation Style`
2	7
3		-	Use this skill when writing or reviewing user-facing documentation, READMEs, `AGENTS.md`, and commit messages for OpenAgents.
	8	+	Use this skill when you write or review user-facing documentation, READMEs, `AGENTS.md`, and commit messages for OpenAgents.
4	9
5		-	`## How to invoke`
	10	+	`## How to use this skill`
6	11
7		-	`Apply these rules to the text you are about to produce or edit. When a rule would make something less clear, break the rule and stay consistent.`
	12	+	`Apply these rules to the text you produce or edit. When a rule would make something less clear, break the rule and stay consistent.`
8	13
9	14		`## Voice and tone`
10	15

18	23		`## Language and grammar`
19	24
20	25		`- Use active voice. Make clear who performs the action.`
21		-	- Use second person (`you`) for the reader.
	26	+	`- Use second person ("you") for the reader.`
22	27		`- Use present tense.`
23	28		`- Use standard American spelling and punctuation.`
24	29		`- Put conditions before instructions, not after.`

48	48		`- You must import the vendor deps into app.js and app.css to use them`
49	49		`- Never write inline <script>custom js</script> tags within templates`
50	50
51		-	`### UI/UX & design guidelines`
	51	+	`### UI and UX design guidelines`
52	52
53	53		`- Produce world-class UI designs with a focus on usability, aesthetics, and modern design principles`
54	54		`- Implement subtle micro-interactions (e.g., button hover effects, and smooth transitions)`

2	2
3	3		`## Communication style`
4	4
5		-	All text in this repo — docs, README, `AGENTS.md`, commit messages, and agent responses — follows the [Google Developer Documentation Style Guide](https://developers.google.com/style). When writing or reviewing text, invoke the `google-developer-style` skill.
	5	+	All text in this repo — docs, README, `AGENTS.md`, commit messages, and agent responses — follows the [Google Developer Documentation Style Guide](https://developers.google.com/style). When writing or reviewing text, read the `google-developer-style` skill at `.agents/skills/google-developer-style/SKILL.md`.
6	6
7	7		- Write in active voice and address the reader as `you`.
8	8		`- Use sentence case for all headings and titles.`