docs-init

[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "docs-init" with this command: npx skills add duc01226/easyplatform/duc01226-easyplatform-docs-init

[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.

Quick Summary

Goal: Initialize project reference documentation by verifying the session-init-docs.cjs hook has created placeholder files, then running scan skills to populate them.

Workflow:

  • Verify -- Check that session-init-docs.cjs hook has created placeholder docs in docs/

  • List -- Show which reference docs exist and which are still placeholders

  • Populate -- Ask user which scan skills to run (or run all)

Key Rules:

  • Do NOT create docs manually -- the hook handles placeholder creation automatically

  • Each reference doc has a corresponding /scan-* skill that populates it

  • Scan skills do deep codebase scanning; expect 5-15 min per skill

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Step 1: Verify Reference Doc Stubs

Check that the session-init-docs.cjs hook has created the 10 reference doc files:

docs/project-reference/project-structure-reference.md -> /scan-project-structure docs/project-reference/backend-patterns-reference.md -> /scan-backend-patterns docs/project-reference/frontend-patterns-reference.md -> /scan-frontend-patterns docs/project-reference/integration-test-reference.md -> /scan-integration-tests docs/project-reference/feature-docs-reference.md -> /scan-feature-docs docs/project-reference/code-review-rules.md -> /scan-code-review-rules docs/project-reference/scss-styling-guide.md -> /scan-scss-styling docs/project-reference/design-system/README.md -> /scan-design-system docs/project-reference/e2e-test-reference.md -> /scan-e2e-tests docs/project-reference/lessons.md -> /learn (managed separately)

If any files are missing, the hook should create them on next prompt. Verify by checking docs/ directory.

Step 2: Detect Placeholder vs Populated

Read the first 512 bytes of each file. If it contains <!-- Fill in your project's details below. --> , it is still a placeholder and needs scanning.

Step 3: Offer Scan Options

Use AskUserQuestion to present:

  • "Run all scan skills" (Recommended for first-time init) -- Runs all 9 scan skills sequentially

  • "Select specific skills" -- Let user choose which ones to run

  • "Skip -- docs are already populated" -- Exit if all docs have content

For each selected scan skill, invoke it via the Skill tool (e.g., /scan-backend-patterns ).

Configuration

Reference doc definitions are in docs/project-config.json under referenceDocs . The hook reads this config to determine which files to create. See .claude/hooks/session-init-docs.cjs for the full implementation.

IMPORTANT Task Planning Notes (MUST FOLLOW)

  • Always plan and break work into many small todo tasks

  • Always add a final review todo task to verify work quality and identify fixes/enhancements

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

pdf-to-markdown

No summary provided by upstream source.

Repository SourceNeeds Review
General

markdown-to-docx

No summary provided by upstream source.

Repository SourceNeeds Review
General

docx-to-markdown

No summary provided by upstream source.

Repository SourceNeeds Review
docs-init | V50.AI