Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From jeremylongshore-claude-code-plugins-plus-skills
Guides creating architecture documentation with step-by-step instructions, best practices, and production-ready configurations. Activates when users mention architecture doc creator or architecture documentation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jeremylongshore-claude-code-plugins-plus-skills:architecture-doc-creatorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides automated assistance for architecture doc creator tasks within the Technical Documentation domain.
This skill provides automated assistance for architecture doc creator tasks within the Technical Documentation domain.
This skill activates automatically when you:
Example: Basic Usage Request: "Help me with architecture doc creator" Result: Provides step-by-step guidance and generates appropriate configurations
| Error | Cause | Solution |
|---|---|---|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |
Part of the Technical Documentation skill category. Tags: documentation, markdown, api-docs, readme, technical-writing
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skillsCreates long-form technical documentation from existing codebases by analyzing architecture, patterns, and implementation details.
Clear technical documentation, API docs, architecture decision records, and runbooks.
Documents system architecture with component diagrams, data flows, ADRs, deployment views, and templates. Analyzes patterns and maintains living docs for team communication.