techguide

Generate self-contained HTML tech guides with 1500-4000+ lines and sticky navigation.

32|6|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/GGPrompts/ggprompts --skill techguide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: techguide
Source: https://github.com/GGPrompts/ggprompts/tree/main/.claude/skills/techguide
Command: npx skills add https://github.com/GGPrompts/ggprompts --skill techguide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams and individuals generate end-to-end, style-consistent technical guides for any developer tool or language, eliminating the manual, repetitive writing process.

Core Features & Use Cases

  • Generate a self-contained tech guide with 1500-4000+ lines, 8-12 sections, a sticky jump nav, inline CSS, and Google Fonts.
  • Aligns with conventions in techguides/CLAUDE.md and the Style Guide Catalog to select an appropriate design system.
  • Use cases include creating guides for new tools, documenting APIs, or compiling best practices for internal teams.

Quick Start

Create a complete tech guide for the provided topic using the selected style, ensuring 8-12 sections, sticky navigation, inline CSS, and 1500-4000+ lines.

Frequently Asked Questions about techguide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a complete technical guide for a developer tool?

To generate a technical guide for a developer tool, define the topic and select a style guide to produce a self-contained HTML document with 1500-4000+ lines, inline CSS, Google Fonts, and a sticky jump navigation.

What is the best way to create web development documentation with sticky navigation?

Creating web development documentation with sticky navigation involves building a self-contained HTML file that includes inline CSS, 8-12 structured sections, and Google Fonts to ensure style consistency without external dependencies.

Can I use this approach to document APIs and best practices for internal teams?

Yes, you can document APIs and compile best practices for internal teams by generating a comprehensive tech guide that aligns with specific style guide conventions and contains 1500-4000+ lines of structured content.

Do I need external CSS files to build a style-consistent tech documentation guide?

No, you do not need external CSS files to build style-consistent tech documentation because the generated guide is a self-contained HTML file that embeds all styling directly using inline CSS and Google Fonts.

What limitations exist when generating a 1500-4000+ line developer guide?

Limitations of generating a 1500-4000+ line developer guide include strict adherence to predefined conventions, restricted font selection to only Google Fonts, and a structural requirement to organize content into exactly 8-12 sections.