「page」の検索結果

Publish a project's docs as a static HTML manual on GitHub Pages: check that Pages is enabled, bring the wiki up to date, list the doc gaps, build the site, preview it locally and push it after GO. Use for "publish the docs", "docs site", "put the manual on GitHub Pages".

日本語の概要は準備中です。原文の説明を表示しています。

Generates high-converting Next.js/React landing pages with Tailwind CSS. Uses PAS, AIDA, and BAB frameworks for optimized copy/components (Heroes, Features, Pricing). Focuses on Core Web Vitals/SEO.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

日本語の概要は準備中です。原文の説明を表示しています。

CLI tool for AI-powered web scraping, data extraction, search, and crawling via ScrapeGraph AI. Use when the user needs to scrape websites, extract structured data from URLs, convert pages to markdown, crawl multi-page sites, search the web for information, automate browser interactions (login, click, fill forms), get raw HTML, discover sitemaps, or generate JSON schemas. Triggers on tasks involving: (1) extracting data from websites, (2) web scraping or crawling, (3) converting webpages to markdown, (4) AI-powered web search with extraction, (5) browser automation, (6) generating output schemas for scraping. The CLI is just-scrape (npm package just-scrape).

日本語の概要は準備中です。原文の説明を表示しています。

Produces and audits externally published marketing copy where factual claims must survive scrutiny — landing pages, product pages, launch emails, one-pagers, search/social metadata. Every statistic, competitor comparison, capability description, and proof point is traced to a fetched source or the project's own documents, labeled, and adversarially verified before it ships. Use when writing or rewriting high-stakes marketing copy; when copy must pass legal, compliance, brand, or claims review; when the audience is skeptical technical or executive buyers; when the company has little or no customer proof yet (pre-launch, zero customers); or when auditing existing copy for unsupported claims, invented capabilities, unverified statistics, or AI-slop language.

日本語の概要は準備中です。原文の説明を表示しています。

Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click / rageclick / scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements. TRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap/click data, or to 'analyze/assess/review the heatmap' for a URL. DO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).

日本語の概要は準備中です。原文の説明を表示しています。

Generate landing pages with AI. TRIGGERS - Use when user needs help with ai-landing-page-gen related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Refactor a whole documentation page in this repository without losing source-verified behavior facts. Use for page rewrites, splits, reorganizations, or substantial shortening of README sections, docs pages, or instruction files. Do not use for ordinary documentation authoring, targeted corrections, or documentation review; use technical-documentation instead.

日本語の概要は準備中です。原文の説明を表示しています。

Web Performance Engineering — analyzes Core Web Vitals using the PageSpeed Insights API (PSI v5) and applies the 80/20 principle: identify the 20% of changes that produce 80% of the performance gain. Produces a prioritized markdown report with quantified estimates and framework-specific code. Trigger: When auditing page speed, analyzing Core Web Vitals, or optimizing web performance for any URL.

日本語の概要は準備中です。原文の説明を表示しています。

Run the PageSpeed performance audit — 80/20 analysis of Core Web Vitals using the PageSpeed Insights API.

日本語の概要は準備中です。原文の説明を表示しています。

Sync the current machine's configuration into the dotfiles repo and update the React showcase page. Use this skill whenever the user says "sync dotfiles", "update dotfiles", "sync config", "actualizar dotfiles", "sincronizar config", "update the repo with my current setup", or anything about pulling their current machine state into the dotfiles repo. Also trigger when the user mentions updating the toolkit page, adding new tools to the page, syncing Claude Code or Codex config (AGENTS.md, codex agents/skills/hooks), or keeping the dotfiles repo in sync with what's actually installed.

日本語の概要は準備中です。原文の説明を表示しています。

Escreve ou reescreve copy de páginas de marketing — home, landing page, página de preço, de produto, de funcionalidade, institucional. Use quando o usuário disser "escrever copy", "criar landing page", "reescrever essa página", "preciso de headline", "melhorar o CTA", "copy do site", "texto da home". Para e-mail use copy-email; para anúncio use copy-ads; para revisar texto pronto use copy-review.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.

日本語の概要は準備中です。原文の説明を表示しています。

Turn any markdown file into a publication-quality PDF. Proper 1in margins, intelligent page breaks, page numbers, cover pages, running headers, curly quotes and em dashes, clickable TOC, diagonal DRAFT watermark. Not a draft artifact — a finished artifact. Use when asked to "make a PDF", "export to PDF", "turn this markdown into a PDF", or "generate a document". (gstack) Voice triggers (speech-to-text aliases): "make this a pdf", "make it a pdf", "export to pdf", "turn this into a pdf", "turn this markdown into a pdf", "generate a pdf", "make a pdf from", "pdf this markdown".

日本語の概要は準備中です。原文の説明を表示しています。

Apply DESIGN, canon, and modules to every page in the inventory, producing a deployable static HTML site. Three render branches (approved page, template-applied sibling, unique render). Per-page, incremental, idempotent, content-preserving by default.

日本語の概要は準備中です。原文の説明を表示しています。

Render a proposed redesign of a page on the current website as a self-contained static HTML file, then iterate via the impeccable craft loop. Per-page, idempotent, stale-aware. Use when the user asks for a redesign prototype, a before/after comparison, a design preview, a page mockup, a visual diff of the redesign, or invokes /stardust:prototype.

日本語の概要は準備中です。原文の説明を表示しています。

Import a single webpage from any URL into canonical EDS block format — structured HTML that authors edit in DA. Scrapes the page, analyzes structure, maps to existing blocks, and generates HTML for immediate local preview. Also triggered by terms like "migrate", "migration", or "migrating". Use this when the goal is canonical EDS authoring; use the snowflake skill instead when the user wants to preserve the original DOM byte-for-byte (static-to-EDS overlay).

日本語の概要は準備中です。原文の説明を表示しています。

Implement several variations of a design directly inside the running app, on the real page/route, with a live switcher to toggle between them in the browser, then recommend one and fold the winner into the real code. Variants are real implementations judged against real data, layout, and density (not an isolated mockup). Use this skill whenever the user wants to try design options live in the app, prototype changes directly on a real page, add a variant switcher, compare layouts in-context, asks to "build a few versions of this page", "try variants on the real screen", "switch between designs in the app", "implement this with a toggle", or says "real-prototype this". For a safe standalone .html copy that never touches the app, use the prototype skill instead.

日本語の概要は準備中です。原文の説明を表示しています。

Filesystem auto-discovery of App Router pages into navigable index pages. Use when creating an index/listing page, adding route directories, converting hard-coded route configs to auto-discovery, or adding a route-listing display variant.

日本語の概要は準備中です。原文の説明を表示しています。

(core) route header and body-height conformance via PageHeader. Use when fixing a (core) page's header, title bar, breadcrumbs, sub-route nav, body height (h-page, calc(100dvh…)), mobile header, or buttons hidden behind the avatar, or on a header-conformance assignment. NOT for /administration/* routes.

日本語の概要は準備中です。原文の説明を表示しています。

Fetch any URL and convert to markdown using Chrome CDP. Supports two modes - auto-capture on page load, or wait for user signal (for pages requiring login). Use when user wants to save a webpage as markdown.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.

日本語の概要は準備中です。原文の説明を表示しています。

Inject a floating toolbar into a running dev page so the user can point at elements and comment on them, and have that arrive as a live notification. Use when iterating on a UI together in the browser, when the user says "page bridge", or asks to show you which element they mean.

日本語の概要は準備中です。原文の説明を表示しています。