From critic
Read and summarize each chapter, writing summaries to the summary/ directory. Use when the user wants chapter summaries generated or updated.
npx claudepluginhub jdpedrie/critic --plugin criticThis skill uses the workspace's default tool permissions.
Read each chapter and write a summary to `summary/<chapter-name>.md`.
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.
Read each chapter and write a summary to summary/<chapter-name>.md.
The vault path for all tool calls is: ${user_config.vault_path}
Run non-interactively through all chapters.
Call list-chapters with the vault path to get all chapter names.
For each chapter, sequentially:
Call summarize-chapter with the vault path and chapter name. This returns the chapter text.
Write a summary of the chapter. The summary should include:
Keep each summary to roughly 200-400 words. Be factual, not evaluative — this is a reference document, not a review.
Call write-summary with the vault path, chapter name, and the summary content.
Report progress: "Saved summary for [chapter name]"
After all chapters are done, report the total number of chapters summarized.