docs

Documentation Community

Skill notes

When to use this skill

Use when the user request matches this skill's domain and capabilities. Use when this workflow or toolchain is explicitly requested.

When not to use this skill

Do not use when another skill is a better direct match for the task. Do not use when the request is outside this skill's scope. Generate stunning, professional software documentation that elevates your projects above the competition. This skill implements a rigorous 4-phase process powered by AI models for maximum impact.

Philosophy

This skill represents documentation excellence through: Rigorous Discovery - Comprehensive project analysis leaving no detail unexplored Kimi K2.5 Thinking - Advanced reasoning for optimal documentation architecture Gemini 3 Flash Design - Modern, cutting-edge visual design generation Unique Positioning - Documentation that differentiates your project

Rigorous Research Routine

Before generating any documentation, the skill performs exhaustive investigation:

Project Analysis

Complete file tree traversal and categorization Language detection and version identification Dependency mapping and ecosystem analysis Architecture pattern recognition Code complexity and structure assessment

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@0-CYBERDYNE-SYSTEMS-0 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview docs.preview
# Thinking Process Outputs

1. Documentation skeleton with prioritized sections
2. Key messages and value propositions
3. Recommended example scenarios
4. Audience-appropriate technical depth
5. SEO keywords and meta descriptions

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.