vp docs

Documentation Community v0.2.1

Skill notes

Invocation Banner

Output this banner as the first thing on every invocation — before questions, work, or any other output: </greeting> <version_check>

Version Update Check (ENH-072)

After displaying the greeting banner, run: If exit code = 1 (update available — new version printed to stdout): Display notice banner before any other output: Replace {latest_version} with stdout from the command, {current} with the installed version, {adapter_id} with the active adapter (claude-code / cursor / antigravity / codex / copilot).

Persona Context Injection (ENH-073)

At skill start, run: Inject the output as ## User Persona context before any task execution. Silent if command unavailable or errors. </persona_context> <adapter id="claude-code">

B. User Prompting

Prompt user conversationally with options.

C. Tool Usage

Use Claude Code tools: Bash (shell), Read (file), Edit + Write (file write/patch), Grep (search), Glob (file patterns), LS, WebSearch, WebFetch, Agent (spawn subagent — multi-level nesting supported) Interactive: AskUserQuestion (deferred — preload via ToolSearch before first call) </adapter>

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
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@0-CODE · v0.2.1 · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Node.js · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

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

01
Step 0: Resolve Project Context (ALWAYS first)

Use `$GIT_HOST`, `$GIT_OWNER`, `$GIT_REPO` in all generated files. Use `$ACTUAL_SKILLS` and `$ACTUAL_WORKFLOWS` for counts. Never write `your-org`, `YOUR_USERNAME`, `YOUR_ORG` into generated files.

02
Step 0A: ViePilot active profile (FEAT-009)

After Step 0: resolve `.viepilot/META.md` → global profile file (same rules as `workflows/crystallize.md`). Keep working notes (org, website, audience, branding) for prose docs; do not fail if missing. Details: `workflows/documentation.md` §0A.

03
Step 1: Ask Documentation Scope

Step 1: Ask Documentation Scope

04
Step 2A: API Documentation

Step 2A: API Documentation

05
Step 2B: Developer Guide

Step 2B: Developer Guide

06
Step 2C: User Guide

Step 2C: User Guide

07
Step 2D: Changelog Update

Step 2D: Changelog Update

08
Step 3: Generate Files

Use templates and extracted content to generate markdown files.

09
Step 3B: Update skills-reference.md (incremental)

For each skill in `$MISSING`: append section to `docs/skills-reference.md`. Do NOT overwrite existing sections (preserve manual edits).

10
Step 4: Create Index

Update `docs/README.md` with: Documentation index Quick links Last updated date Also update root `README.md`:

11
Step 5: Commit

Step 5: Commit

12
Step 6: Confirm

</process> <success_criteria> [ ] Requested documentation generated [ ] Code examples included where relevant [ ] Cross-references added between docs

Discussion

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