journeydoc-init

Initialize capture-driven documentation scaffolds with Playwright specs and Docusaurus configs.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ConductionNL/shillinq --skill journeydoc-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journeydoc-init
Source: https://github.com/ConductionNL/shillinq/tree/main/.claude/skills/journeydoc-init
Command: npx skills add https://github.com/ConductionNL/shillinq --skill journeydoc-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of setting up user documentation by automating the creation of a standardized, capture-driven documentation scaffold that integrates seamlessly with Conduction apps.

Core Features & Use Cases

  • Automated Scaffolding: Instantly generates the required directory structure, Playwright capture specs, and Docusaurus configuration.
  • Brown-field Migration: Automatically detects and fixes common documentation anti-patterns like broken image paths, stale locales, and incorrect domains.
  • Use Case: When launching a new feature or app, use this skill to generate a complete documentation site skeleton that is ready for content and automated screenshot generation.

Quick Start

Use the journeydoc-init skill to bootstrap documentation for the opencatalogi app.

Frequently Asked Questions about journeydoc-init

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

FAQPage Schema
How do I automate Docusaurus documentation scaffolding for a new application?

Automated Docusaurus scaffolding generates the required directory structure, Playwright capture specs, and configuration files. This eliminates manual setup overhead by creating a complete, capture-driven documentation skeleton ready for content integration.

What is capture-driven user documentation and how does it work with Playwright?

Capture-driven user documentation uses Playwright test specs to automate screenshot generation for your docs. This mechanism ensures visual content stays synchronized with application updates by generating screenshots directly from automated browser interactions.

Can I use this to migrate existing documentation with broken image paths and stale locales?

Yes, you can migrate existing documentation by detecting and fixing common anti-patterns like broken image paths, stale locales, and incorrect domains. This brown-field migration automatically repairs existing documentation structural issues during the scaffolding process.

Do I need the GitHub CLI installed to bootstrap documentation scaffolds?

Yes, you need the GitHub CLI installed and local filesystem access to bootstrap documentation scaffolds. These tools are required to manage repository branches and pull requests during the automated initialization process.

What's the best way to set up automated screenshot generation for a Docusaurus site?

The best way to set up automated screenshot generation is creating a standardized scaffold integrating Docusaurus configurations with Playwright test specs. This approach ensures your documentation site is immediately ready for automated visual content capture.