From solution-engine
Generate per-component implementation specs from formalization and stack selection
npx claudepluginhub jobrien127/plugin-marketplace --plugin solution-engineThis skill is limited to using the following tools:
Produce one spec file per system component, following SPEC_TEMPLATE.
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.
Produce one spec file per system component, following SPEC_TEMPLATE.
select complete$PROBLEMS_ROOT/$ARGUMENTS/specs/*.mdspecify → complete$MATH_ROOT/ formalization.$PROBLEMS_ROOT/$ARGUMENTS/stack/evaluation.md — selected algorithms and stack.${CLAUDE_PLUGIN_ROOT}/templates/SPEC_TEMPLATE.md — spec structure.experience/ and market/ for non-optimization components.$PROBLEMS_ROOT/$ARGUMENTS/specs/.pipeline-state.json.