bootstrap

Initialize the .docent directory structure and configuration for new projects.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/tnez/docent --skill bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootstrap
Source: https://github.com/tnez/docent/tree/main/skills/docent/bootstrap
Command: npx skills add https://github.com/tnez/docent --skill bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up a new project's documentation structure and configuration from scratch can be a manual and error-prone process. This Skill automates the initialization of the .docent/ directory, creating a standardized knowledge base, configuration file, and essential documentation scaffolding, ensuring consistency and immediate readiness for AI-powered documentation.

Core Features & Use Cases

  • Directory Scaffolding: Creates the full .docent/ structure including templates/, runbooks/, journals/, sessions/, and more.
  • Default Configuration: Generates a config.yaml with sensible defaults and project-specific settings.
  • Welcome Documentation: Provides an initial README.md to guide users on how to interact with Docent.
  • Use Case: You've just started a new project and want to integrate Docent. Simply tell your agent "Set up docent in this project" and it will instantly create the entire documentation infrastructure, ready for knowledge capture and retrieval.

Quick Start

Set up docent in this project.

Frequently Asked Questions about bootstrap

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

FAQPage Schema
How do I set up a documentation structure for a new project?

Project documentation setup creates a standardized .docent/ directory with configuration, templates, and subdirectories for runbooks, journals, sessions, and notes. This Skill automates the entire scaffolding process, generating config.yaml, .gitignore, and README.md instantly, so your project is ready for knowledge capture immediately.

What does the .docent directory contain after initialization?

The .docent directory structure includes templates/, runbooks/, journals/, sessions/, notes/, projects/, decisions/, and proposals/ subdirectories, plus a config.yaml file with sensible defaults and a .gitignore to exclude documentation artifacts from version control.

Can I use this initialization with existing Git repositories?

Yes, initialization works with or without Git. The Skill requires only a pre-existing project directory with write permissions and optionally integrates with Git by generating appropriate .gitignore entries to manage the .docent/ structure.

What languages and tools does project initialization support?

Project initialization applies across common languages and tools, creating a language-agnostic documentation framework. The standardized .docent/ structure and config.yaml work independently of your project's tech stack.

Do I need to manually create configuration files after setup?

No, initialization generates a complete config.yaml with sensible defaults and project-specific settings automatically. You get an instant, ready-to-use knowledge base without manual configuration steps.

What happens if the project directory lacks write permissions?

Initialization requires write permissions to the project directory to create the .docent/ structure and configuration files. Ensure your user account has write access before running setup.