「title」の検索結果

SEO + GEO (AI-search) + brand-entity desk (Busabase App-in-Skill) — wired to Google Search Console for a dashboard over search analytics and an agent-prepared SEO opportunities review queue, plus an AI-visibility tracker (are we cited in ChatGPT / Perplexity / Gemini / Claude / Copilot answers), a GEO content-optimization queue gated by geo-qa, and an entity / knowledge-panel readiness checklist. Use when the user invokes $kelly-seo or /kelly-seo, mentions SEO, Google Search Console, GSC, search analytics, search performance, queries, keywords, rankings, positions, impressions, clicks, CTR, striking-distance queries, title/meta rewrites, content briefs, internal links, SEO opportunities review, GEO, generative engine optimization, AI search, AI visibility, being cited by AI answer engines, ChatGPT/Perplexity/Gemini/Claude/Copilot citations, brand entity, knowledge panel, Wikidata, schema.org, or entity readiness.

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

Listing factory (上架工作台, Busabase App-in-Skill) for a cross-border e-commerce seller. Use when the user invokes $kelly-listing or /kelly-listing, mentions 上架, listing, Amazon title bullets, A+ content, flat file, TikTok Shop listing, listing compliance, 禁用词, multi-locale listings, wants platform listings drafted from product source material or a kelly-picks brief, deterministic compliance checks against per-platform rule sets, a review queue for approving drafts, or approved listings exported as Markdown/CSV for upload.

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

Explore PostHog's Inbox — the surface where signal reports surface as actionable issues and trends. Use when the user asks "what's in my inbox?", "what should I look at?", "which reports are actionable?", "what's PostHog flagged recently?", asks about a specific report by ID or title, or wants to see which signal sources are configured. Covers listing, filtering, and drilling into reports, plus pointers to the deeper `signals` skill when raw signals or semantic search are needed.

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

Create a clean, review-ready pull request with a good title, structured description, linked issues, and appropriate reviewers.

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

Generate a print-ready PDF manuscript with title page, table of contents, and chapters at 6x9 inch trim size.

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

Generate a professional PDF report with title, executive summary, data table, and footer.

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

Generate an Amazon A+ Content banner image for book marketing with cover art, title, and branding.

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

Generate a front cover image with custom artwork, title text, and author attribution.

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

Generate a professional certificate image with recipient name, course title, and completion date for digital sharing, social media, or email delivery.

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

Build a PowerPoint slide deck with title slide, content slides, and call-to-action page.

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

Generate an Open Graph social sharing card with dynamic title, description, and branding.

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

Generate a YouTube thumbnail with bold title text, gradient background, and a static image cutout.

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

Extract role title, location, salary range, requirements, and application details from a public job posting.

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

Extract title, summary, steps, related links, and last updated date from a public help center article.

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

Extract clean article content — title, author, date, and body text — from PDFs, Word docs, and web pages.

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

Extract title, authors, abstract, and citation info from academic papers.

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

Extract clean title, summary, markdown sections, and source metadata from a public documentation page for RAG ingestion.

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

Gestion de l'état global dans Next.js — contextes d'auth Sanctuaire/Expert, entitlements, et hooks React personnalisés.

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

5-level verification pyramid: static→unit→Playwright E2E (homepage-first, 6bp)→AI visual→post-deploy. 8-check quality gate. Multi-agent testing (functional/security/a11y/performance). Playwright v1.59+ AI agents (Planner/Generator/Healer). WCAG 2.2 AA via axe-core v4.11. Percy+Chromatic visual regression. ADA Title II 2027/2028 deadlines.

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

Prepare a request to change the terms of a Japanese job offer before accepting it, sorting what the user wants changed (pay components, start date, work style, location, title, probation) by priority, tying each ask to a basis the user can show (the written offer, the job posting, what was said in interviews, their own records), working the timing back from the acceptance deadline, and drafting the message to the employer or recruiting agent. Use when a user has an offer and wants to ask for higher pay, a later start date, more remote days, or other changed terms, or wants to know how to raise it without losing the offer; do not use to predict whether the request will succeed, to set a target figure from market rates, to fabricate a competing offer, to decide whether to accept, or to send anything to the employer.

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

Assemble a Japanese shokumu-keirekisho (career history document) from an experience inventory, choosing between reverse-chronological, chronological, and skills-based layouts, mapping the target posting's requirements to the experiences that can support them, and drafting the summary, work history, skills, and self-PR so that each sentence stays within what its evidence supports and confidential details are abstracted. Use when a user wants to write or rebuild a whole shokumu-keirekisho for a specific posting or as a general version, or wants to decide which experiences to include and in what order; do not use to invent experience, numbers, titles, or qualifications, to predict whether it will pass screening, to fill in a rirekisho form, or to submit it anywhere.

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

Create an aggregated Epic PR from a `cc-epic-<Issue number>` branch to the default branch. Takes the Epic Issue number as argument, assumes sub-PRs have already been merged into the epic branch, and automatically generates the PR title and description from the commit log against the base branch (including sub-PR / sub-Issue references). The PR is posted via `gh pr create` with no label and `Closes #<Epic Issue>`.

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

Re-analyze an existing GitHub Issue using its current title and body, refresh the implementation plan against the latest code state, and update the Issue in place. Use when the user provides an Issue number (numeric, `#`-prefixed, or Issue URL) and wants to regenerate the code analysis via the explore-agent subagent. For reflecting comment-driven updates, use update-issue. For creating a brand-new Issue from a natural-language task description, use create-issue.

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

Generate a single-file industrial-archive product landing page (Nordic museum aesthetic, hash-routed detail pages). Takes a natural-language description of one or more "exhibit-style" products (objects, tools, hardware, watches, kitchenware, lighting, audio, instruments, anything with a designed/forged/restrained quality); outputs ONE working .html file. Visitors see a black-framed cover that flips between exhibits, sidebar index, side meta column (material/origin/year/dimension), and click any exhibit → full detail page (giant italic title, spec table, hero image, lead + 3 prose paragraphs, gallery, prev/next). Runs in BOTH Claude Code (writes to ~/Desktop) and GLM / online chat (outputs HTML inline). Trigger: "做个工业风产品落地页", "做克制之物风格的展品页", "industrial-archive-gen ...", or when user drags this skill folder into chat asking for a product page in the Nordic-industrial archive style.

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