By hpsgd
User documentation writer — user guides, tutorials, knowledge base articles, onboarding content. Writes in product language for non-technical audiences.
Bootstrap the user documentation conventions for a project. Appends user guide, onboarding, and KB article conventions to docs/content/CLAUDE.md. Idempotent — merges missing sections into existing files without overwriting.
Define a documentation content strategy using the Diataxis framework — map existing content, identify gaps across tutorials/how-to/reference/explanation quadrants, and plan content creation. Use when establishing or auditing a documentation practice.
Write a knowledge base article from a resolved support issue, common question, or how-to topic.
Write onboarding content — welcome flow, getting-started guide, or first-run experience. Optimised for time-to-first-value. Use when creating new user onboarding or improving activation rates.
Write a task-oriented user guide for a feature or workflow. Written in product language for non-technical readers. Produces step-by-step instructions with expected results and troubleshooting.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A plugin marketplace for Claude Code. Agents, skills, rules, and conventions that work together as a virtual team.
/plugin marketplace add hpsgd/turtlestack
Start with the core plugins (rules, thinking skills, and code review), then add agents for your stack:
/plugin install coding-standards@hpsgd
/plugin install writing-style@hpsgd
/plugin install security-compliance@hpsgd
/plugin install thinking@hpsgd
/plugin install tooling@hpsgd
/plugin install code-reviewer@hpsgd
/plugin install ai-engineer@hpsgd
Add a technology stack if relevant:
/plugin install dotnet-stack@hpsgd
/plugin install nextjs-stack@hpsgd
/plugin install python-stack@hpsgd
Then reload:
/reload-plugins
Browse the full plugin list below to see what else is available.
Per-project overrides. Create your own .claude/rules/ files. Project-level rules take precedence over marketplace rules.
Disabling a plugin. Set it to false in .claude/settings.json:
{
"enabledPlugins": {
"writing-style@hpsgd": false
}
}
Local overrides (not committed). Use .claude/settings.local.json for personal preferences that shouldn't affect the team.
{
"enabledPlugins": {
"coding-standards@hpsgd": true,
"writing-style@hpsgd": true,
"security-compliance@hpsgd": true,
"thinking@hpsgd": true,
"tooling@hpsgd": true,
"code-reviewer@hpsgd": true,
"dotnet-stack@hpsgd": true,
"nextjs-stack@hpsgd": true,
"python-stack@hpsgd": true,
"plugin-curator@hpsgd": true,
"coordinator@hpsgd": true,
"cpo@hpsgd": true,
"product-owner@hpsgd": true,
"ui-designer@hpsgd": true,
"ux-researcher@hpsgd": true,
"user-docs-writer@hpsgd": true,
"developer-docs-writer@hpsgd": true,
"internal-docs-writer@hpsgd": true,
"gtm@hpsgd": true,
"support@hpsgd": true,
"customer-success@hpsgd": true,
"grc-lead@hpsgd": true,
"cto@hpsgd": true,
"architect@hpsgd": true,
"react-developer@hpsgd": true,
"dotnet-developer@hpsgd": true,
"python-developer@hpsgd": true,
"ai-engineer@hpsgd": true,
"qa-lead@hpsgd": true,
"qa-engineer@hpsgd": true,
"release-manager@hpsgd": true,
"performance-engineer@hpsgd": true,
"devops@hpsgd": true,
"security-engineer@hpsgd": true,
"data-engineer@hpsgd": true,
"analyst@hpsgd": true,
"investigator@hpsgd": true,
"workflow-tools@hpsgd": true
}
}
After installing plugins, scaffold your project with domain-specific docs:
/coordinator:bootstrap-project my-project
npx claudepluginhub hpsgd/turtlestack --plugin user-docs-writerInternal documentation writer — architecture docs, runbooks, changelogs, onboarding guides, ADR documentation. Writes for engineers who know the domain but may be new to the codebase.
Go-to-market specialist — positioning, launch strategy, content marketing, competitive analysis
Customer support — ticket triage, feedback synthesis, knowledge base, bug escalation
Security baseline rules and audit skills for maintaining secure code
Developer documentation writer — API references, SDK guides, integration tutorials, code examples. Writes for developers who are competent but unfamiliar with your codebase.
📚 Technical Writer — Technical Documentation Specialist + Knowledge Curator
Documentation agents — technical writer, documentation architect
Documentation review, cleanup, and generation with AI slop detection, style learning, and human-quality writing enforcement
Technical documentation specialist for README files, API docs, user guides, specifications, and release notes with Obsidian vault management
Write technical blog posts, tutorials, and documentation with Flatiron School's engaging teaching style. Turn complex topics into clear narratives.
Claude + Obsidian knowledge companion. Sets up a persistent, compounding wiki vault (Karpathy's LLM Wiki pattern). v1.7 "Compound Vault" + v1.8 methodology modes close 5 of 5 priority gaps from the May 2026 compass artifact. Ships: substrate alignment with kepano/obsidian-skills, default Obsidian CLI transport, hybrid retrieval (contextual prefix + BM25 + cosine rerank per Anthropic's Sept 2024 research), per-file advisory locking for multi-writer safety, pre-commit verifier agent, AND methodology modes (LYT / PARA / Zettelkasten / Generic) for first-class organizational support no other Claude+Obsidian competitor offers. v1.7.x audit closure: every BLOCKER + HIGH + MEDIUM + LOW finding from the v1.7.0 audit is CLOSED or DEFERRED-with-rationale. Optional DragonScale Memory extension (log folds, deterministic addresses, semantic tiling lint, boundary-first autoresearch).