From folio
Initialize a Folio workspace with directory structure, intent capture, and material import. Use when starting a new manuscript project.
npx claudepluginhub athan-dial/skills --plugin folioThis skill uses the workspace's default tool permissions.
Set up a new Folio workspace with canonical directory structure, intent capture, and material import.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Set up a new Folio workspace with canonical directory structure, intent capture, and material import.
None — this is the first stage in the pipeline.
idea — Core contribution or topic (prompt if not provided).materials_path — Folder of notes, data, figures, PDFs, etc. (prompt if not provided; accept none for blank slate).venue (optional) — Target outlet and formatting constraints.Collect missing inputs. Prompt for idea, materials_path, and optionally venue.
Capture intent fields. Prompt the user for each field that populates intent.json:
audience — Who must understand the output.doc_type — Short label (e.g., white paper, research article, memo).thesis — One or two sentences: central claim or promise.constraints — Length, tone, confidentiality, deadlines, tooling.forbidden_topics — Topics or claims to avoid.preferred_mode — white_paper, research_paper, hybrid, or null for auto-routing.Align field names and types with ../../templates/manifests/intent.schema.json.
Run initialization script:
python ../../scripts/init_workspace.py "<workspace_path>"
Copy user materials into inputs/raw_materials/ under the workspace root. Preserve relative structure when copying trees.
Write intent.json at the workspace root from user responses. If ip_policy.json exists, ensure forbidden terms and code-name lists reflect organizational policy (see ../../templates/manifests/ip_policy.schema.json).
Append a session line to logs/run_log.md.
inputs/, planning/, citations/, figures/, drafts/, reviews/, final/, exports/, logs/).intent.json populated and valid for routing.Proceed to folio:prep.