Skip to content

Add Claude Code agent team for Spryker docs#3767

Open
alex-galych wants to merge 1 commit into
masterfrom
feature/claude-docs-agents
Open

Add Claude Code agent team for Spryker docs#3767
alex-galych wants to merge 1 commit into
masterfrom
feature/claude-docs-agents

Conversation

@alex-galych

Copy link
Copy Markdown
Contributor

Summary

Adds a file-based Claude Code subagent team under .claude/agents/ for autonomous, standards-compliant documentation work on this repository. Every agent treats the repo CLAUDE.md as the authoritative source for documentation standards and the validation workflow.

Agents

Agent Role Edits files?
docs-orchestrator Plans and coordinates an end-to-end docs change; delegates and gates on validation No (delegates)
docs-writer Authors/edits Markdown/Jekyll content to Spryker standards Yes
docs-reviewer Read-only standards/style/grammar review → numbered amendments No
docs-validator Runs Vale, markdownlint, and the sidebar checker; fixes ERRORS only Yes
sidebar-manager Keeps _data/sidebars/*.yml in sync on add/remove/rename/move Yes
docs-architect Information architecture & restructuring plans (advisory) No (plans)
docs-ux-designer Page-level UI/UX and accessibility improvements Yes
docs-speller English spelling correctness; curates the Vale vocabulary Yes

README.md documents the team, the typical flow, and how to extend it.

Notes

  • Docs-only change: adds agent definitions under .claude/; no documentation content or sidebars are modified.

🤖 Generated with Claude Code

Introduce a file-based subagent team under .claude/agents/ for autonomous
documentation work, all gated on the repository CLAUDE.md standards:

- docs-orchestrator: plans and coordinates end-to-end docs changes
- docs-writer: authors/edits Markdown to Spryker standards
- docs-reviewer: read-only standards/style/grammar amendments
- docs-validator: runs Vale, markdownlint, and the sidebar checker
- sidebar-manager: keeps _data/sidebars/*.yml in sync
- docs-architect: information architecture / restructuring plans
- docs-ux-designer: page-level UI/UX and accessibility
- docs-speller: English spelling correctness and Vale vocabulary

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@netlify

netlify Bot commented Jun 21, 2026

Copy link
Copy Markdown

Deploy Preview for spryker-docs ready!

Name Link
🔨 Latest commit 56c9460
🔍 Latest deploy log https://app.netlify.com/projects/spryker-docs/deploys/6a38035a82888c00085aad87
😎 Deploy Preview https://deploy-preview-3767--spryker-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@profuel profuel left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would also like to add the following statement somewhere:
When you are done with writing, check it for consistency and sanity, use of the same vocabulary and ambiguity

should be staged vs. done together.

You do not modify files. Hand the plan to `docs-orchestrator` for execution and
flag anything that needs a human decision (audience, ownership, scope).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest to be more specific about audience here.
i.e. mention roles that can act: architect, product owner, solution engineer, etc.

Comment on lines +25 to +27
standards (internal link format, tone of voice, Markdown/Liquid rules,
`last_updated`, sidebar rules, Twig `{% raw %}` wrapping, `info_block` blank-line
rule, validation workflow). Read it before planning if you have not already, and

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do you list rules here - let's only add reference.

Comment on lines +32 to +38
- Internal links are `/docs/.../file.html` (leading `/`, `.html` not `.md`).
- `last_updated` frontmatter is set to today's date on every edited file.
- Adding, removing, renaming, or moving a file requires a matching sidebar update
in `_data/sidebars/`.
- American spelling, second person, active voice, present tense, no contractions.
- Twig is wrapped in `{% raw %}{% endraw %}`; `info_block` content is surrounded
by blank lines.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see the same in the architect. let's put it into rules and reference

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants