Guides rendering strategy selection and optimization for search engine and AI crawler visibility. Golden rule: Page data and metadata must be available on page load without JavaScript execution for optimal SEO.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrendering-strategiesExecute the skills CLI command in your project's root directory to begin installation:
Fetches rendering-strategies from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate rendering-strategies. Access via /rendering-strategies in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
Guides rendering strategy selection and optimization for search engine and AI crawler visibility. Golden rule: Page data and metadata must be available on page load without JavaScript execution for optimal SEO.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
| Method | When HTML generated | SEO | Best for |
|---|---|---|---|
| SSG (Static Site Generation) | Build time | ✅ Best | Blog, docs, marketing pages; content rarely changes |
| SSR (Server-Side Rendering) | Request time | ✅ Good | News, product pages; dynamic, personalized content |
| ISR (Incremental Static Regeneration) | Build + revalidate | ✅ Good | Large sites; static with periodic updates |
| CSR (Client-Side Rendering) | Browser (after JS) | ❌ Poor | Dashboards, account pages; no SEO needed |
| Dynamic rendering | On-demand for bots | ✅ Fallback | SPAs; prerender for crawlers, SPA for users |
HTML generated at build time; same HTML for every request. Best for SEO: crawlers receive full HTML immediately; optimal performance.
getStaticProps, Astro, GatsbyHTML generated on each request. Good for SEO: crawlers receive complete HTML; supports dynamic, personalized content.
getServerSideProps, RemixStatic at build; pages can revalidate after a period. Good for SEO: combines static performance with freshness.
revalidate in getStaticPropsServer sends minimal HTML shell; content renders in browser after JS loads. Not for SEO: crawlers may see empty content; indexing delays or failures.
Serve prerendered HTML to crawlers; serve SPA to users. Fallback when full SSR/SSG is not feasible (e.g. legacy SPA migration).
| Crawler | JavaScript | Content in initial HTML |
|---|---|---|
| Googlebot | Renders JS (Chrome); may have multi-day queue | Full weight; SSR/SSG preferred |
| AI crawlers (GPTBot, ClaudeBot, PerplexityBot) | Do not execute JS | Required—CSR content invisible |
| Bingbot | Renders JS | Same as Googlebot |
AI crawlers: ~28% of Googlebot's crawl volume. Critical content (articles, meta, nav) must be in initial HTML. See site-crawlability for AI crawler optimization; generative-engine-optimization for GEO.
Google does not simulate user clicks (tabs, carousels, "Load more"). Content loaded via AJAX or on interaction is not discoverable.
| Component | Requirement | Implementation |
|---|---|---|
| Tabs / Accordion | All tab content in DOM at load | Server-render; use <details>/<summary> or CSS show/hide |
| Carousel | All slides in initial HTML | Server-render; CSS/JS for show/hide only |
| Hero | Headline, CTA, LCP image in HTML | No JS-only rendering |
| Navigation | All nav links in first paint | No JS-injected menus for critical links |
Recommendation: Server-render (SSR/SSG) all critical content; use JS only for interaction (show/hide, animation). Content loaded on click = not indexed.
| Content type | Rendering | Reason |
|---|---|---|
| Blog, docs, marketing | SSG or ISR | Best SEO; fast; static |
| Product, news, dynamic | SSR | Fresh content; crawler-ready |
| Dashboard, account | CSR | No SEO; auth required |
| Legacy SPA | Dynamic rendering | Bridge until SSR/SSG migration |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
rendering-strategies fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added rendering-strategies from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
rendering-strategies is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: rendering-strategies is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: rendering-strategies is the kind of skill you can hand to a new teammate without a long onboarding doc.
rendering-strategies is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for rendering-strategies matched our evaluation — installs cleanly and behaves as described in the markdown.
rendering-strategies reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: rendering-strategies is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend rendering-strategies for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 38