From amplify
Enforces mandatory Skill tool invocation before any response or clarifying questions at conversation start to discover and apply relevant skills.
npx claudepluginhub wezzard/skills --plugin amplifyThis skill uses the workspace's default tool permissions.
<EXTREMELY-IMPORTANT>
Enforces workflows for skill discovery and invocation before tasks: check all skills first, read relevant ones, brainstorm before coding, create todos for checklists.
Enforces skill check before any Claude Code response: invoke if 1% relevant, follow flowchart and red flags to avoid rationalizing skips. Use at conversation starts.
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.
Share bugs, ideas, or general feedback.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.
Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
These thoughts mean STOP—you're rationalizing:
| Thought | Reality |
|---|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't count as a task" | Action = task. Check for skills. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
When multiple skills could apply, use this order:
"Let's build X" → brainstorming first, then write-plan, then execute-plan, then review. "Fix this bug" → recover-from-errors if stuck, brainstorming if unclear.
| Skill | When to Use |
|---|---|
brainstorming | BEFORE any creative work: features, components, modifications |
write-plan | After brainstorming, to create structured implementation plan |
execute-plan | When you have a finalized plan file ready to implement |
review | After plan execution completes, to verify all changes were implemented |
recover-from-errors | After 2+ consecutive failures or when stuck |
Rigid (execute-plan, recover-from-errors): Follow exactly. Don't adapt away discipline.
Flexible (brainstorming): Adapt principles to context.
The skill itself tells you which.
Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.