From pratyabhijna-creative-engine
Use when the user asks for a poem, haiku, sonnet, ghazal, or any short literary form, or when they want a constraint-anchored creative composition. Routes through the Pratyabhijna cascade so the result reflects vimarsa aspect-shifts and BMR-driven candidate selection rather than raw LM sampling.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pratyabhijna-creative-engine:cascade-poetryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Poetry, song lyrics, haiku, micro-fiction, or any short literary form where the user supplies a topic + form constraint. Also use when the user asks "compose with the cascade" or "use PCE for this poem".
Poetry, song lyrics, haiku, micro-fiction, or any short literary form where the user supplies a topic + form constraint. Also use when the user asks "compose with the cascade" or "use PCE for this poem".
prompt string (the brief / image / event).constraint_text that names the form and tone (e.g. "a 5-7-5 haiku about autumn rain, restrained voice").must_avoid from concrete clichés the user wants to dodge.aspects (2-4 short phrases naming axes of meaning the user wants present).pratyabhijna_mcp__cascade with K=6..8, max_tokens=64..96, render_mode="verbatim".surface, vimarsa_event, selected_idx, audit.delta_F, audit.ananda_scores.vimarsa_event = false and the user asked for an aspect-shift poem, retry with a slightly higher cit_temperature (1.1 → 1.3) and a larger K.Return the surface text. If vimarsa_event = true, add a one-line italicised note saying which aspects were detected. Never return raw JSON to the user.
cascade.aspects the user did not imply.npx claudepluginhub sharathsphd/pratyabhijna --plugin pratyabhijna-creative-engineCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.