Execute FireCrawl primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "firecrawl main workflow", "primary task with firecrawl".
Executes the primary FireCrawl workflow for core integration and feature development tasks.
/plugin marketplace add jeremylongshore/claude-code-plugins-plus-skills/plugin install firecrawl-pack@claude-code-plugins-plusThis skill is limited to using the following tools:
Primary money-path workflow for FireCrawl. This is the most common use case.
firecrawl-install-auth setup// Step 1 implementation
// Step 2 implementation
// Step 3 implementation
| Error | Cause | Solution |
|---|---|---|
| Error 1 | Cause | Solution |
| Error 2 | Cause | Solution |
// Complete workflow example
For secondary workflow, see firecrawl-core-workflow-b.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.