From forge-core
Collaborative ideation before implementation — explore context, clarify intent, propose approaches. USE WHEN starting creative work, new features, design decisions, or modifying behavior.
npx claudepluginhub n4m3z/forge-coreThis skill uses the workspace's default tool permissions.
Turn ideas into designs through structured dialogue. Explore context, ask questions, propose approaches with trade-offs, get approval before implementation.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
Turn ideas into designs through structured dialogue. Explore context, ask questions, propose approaches with trade-offs, get approval before implementation.
No implementation until design is approved — not code, not scaffolding, not "just a quick prototype."
Every project goes through this process. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short, but it must exist and be approved.
Ask one question at a time. Wait for the answer before asking the next. Bundling questions overwhelms and produces shallow answers.
Good questions uncover constraints the user hasn't stated:
Present 2-3 distinct approaches, not variations of the same idea. Each approach gets:
Lead with your recommendation and explain why.
| Thought | Reality |
|---|---|
| "This is too simple to need a design" | Simple projects are where bad assumptions waste the most time. |
| "I already know what they want" | You know what you assumed. Ask. |
| "Let me just start coding and we'll iterate" | Iteration without direction is thrashing. |
| "The user seems impatient, skip to building" | Rushing produces rework. A short design is still a design. |
| "I'll figure it out as I go" | That's exploration, not implementation. Explore, then design. |
| "There's only one way to do this" | There are always trade-offs. Name them. |