3,018 件 ・ 関連度順
概要と使いどころ
Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says "programmatic SEO", "pages at scale", "dynamic pages", "template pages", "generated pages", "data-driven SEO", "pSEO", "template engine", "data-driven pages", "index bloat", or "thin content at scale".
日本語の概要は準備中です。原文の説明を表示しています。
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
日本語の概要は準備中です。原文の説明を表示しています。
Porta el cambio de la rama actual a las variantes hermanas de esta plantilla (es/en × con-IA/sin-IA) — traduce el contenido, adapta o elimina la capa de IA según el destino y deja cada variante con una rama lista para PR. Úsalo cuando un cambio del template deba replicarse en las otras variantes (p. ej. "porta este cambio al template en inglés", "replica esto en las variantes").
日本語の概要は準備中です。原文の説明を表示しています。
Trae a este proyecto las mejoras que la plantilla de origen recibió después de la instanciación — lee .template-origin, calcula el diff del tooling (skills, hooks, scripts, workflows) contra la plantilla actual y propone aplicarlo. Úsalo cuando la persona quiera actualizar/sincronizar el proyecto con la plantilla (p. ej. "actualiza la plantilla", "trae las mejoras nuevas del template").
日本語の概要は準備中です。原文の説明を表示しています。
Secure skill template with prompt injection defenses. Copy this template when creating new skills.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and fix common accessibility issues in Angular templates and Angular Material components. Use when the user mentions Lighthouse, axe, screen readers, keyboard navigation, ARIA, asks to fix a11y issues in Angular HTML templates, or after any feature, bug fix, or refactor that changed Angular templates.
日本語の概要は準備中です。原文の説明を表示しています。
Start a project on the Visual Stack — a multi-step setup form captures what's being built, recommends a stack, and either instantiates the vstack-template-base template, sets up a specs-and-design-only workspace, or records an existing codebase without touching it. Use when the user wants to start a new project, scaffold a repo, set up a codebase from the Cavalry template, pick a stack or add-ons, run Day-1 setup, or bring an existing app onto the visual stack.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when creating professional presentation materials, slide decks, or proposal documents following FUJISOFT America's corporate template standards. Triggers include requests like "create a presentation", "make slides", "prepare proposal materials", "FUJISOFT template", or when MARP-format Markdown presentations are needed with consistent corporate branding. The skill provides a complete MARP template with CSS styling, visual design components, and quality assurance workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Render a Template + data + Style into a final artifact in one of HTML, PDF, PNG, SVG or PPTX. Use whenever the user asks for a concrete deliverable like "make me a poster", "render a card", "give me a one-pager".
日本語の概要は準備中です。原文の説明を表示しています。
Builds a slide-by-slide presentation draft on the user's own slide template and checks every slide against written brand rules (colours with hex codes, fonts, logo placement, slide archetypes, tone, banned visuals), returning the approved outline, the DRAFT deck content and a compliance report as Markdown. Use when the user asks to "build this deck on our template", "make these slides on-brand", "check this presentation against our brand guidelines", "rebuild these slides to corporate identity (CI)" or asks for a CI-compliant or corporate-template presentation. Do not use for an accessibility review of slides, use document-accessibility-check instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a DRAFT proposal skeleton from a discovery summary (call notes, discovery brief, CRM record, emails) and the organisation's own proposal template: every template section in order, pre-filled only where the discovery material supports it with the source beside each line, and every section still needing a human input marked HUMAN INPUT with the owner role and the question to answer. Use when the user asks to "start the proposal for <prospect>", "build the proposal skeleton from the discovery notes", "pre-fill our proposal template", "what do we already have for the proposal" or "first cut of the proposal". Do not use for answering a formal RFP, RFQ or tender question set, use rfp-response-drafter instead; for turning a priced estimate into a statement of work use estimate-to-sow. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Manage the NV oOS Pro Toolkit Project Management system — projects, tasks, events, sprints, task plans, task templates, and PM workflow rules. Covers complete project lifecycle (planning → active → completed), task tracking with priorities and effort estimation, sprint planning, event scheduling with attendees, and template-driven task plan generation. Use when managing projects, creating or tracking tasks, planning sprints, scheduling events, generating task plans from templates, assigning work to team members, or troubleshooting project management data.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy Azure resources with ARM templates and Bicep. Create modular deployments and manage dependencies. Use when deploying Azure-native IaC.
日本語の概要は準備中です。原文の説明を表示しています。
Digital product builder — Ebooks, templates, presets, Notion templates, Gumroad setup
日本語の概要は準備中です。原文の説明を表示しています。
テンプレートへのフィードバック。開発中の問題や改善点をテンプレートリポにPRとして反映する。 「テンプレートに反映して」「テンプレートを改善して」「テンプレートにフィードバックして」 「親テンプレートにPR作成して」「テンプレートリポにPRして」 「これをテンプレートに反映したい」などのリクエストで使用する。 sync-templateは取り込み（pull）、本スキルは反映（push/PR）。
Use this skill when writing or editing Japanese documentation, teaching material, comments, or explanations for this template (Sabakyan style). Trigger words: ドキュメント執筆, 教材, 解説を書く, 日本語スタイル, README 作成, 説明文, サバキャン, わかりやすく書く.
This skill should be used when the user asks to "fill a template", "テンプレート入力", "書式入力", "裁判所書類の作成", "テンプレートに入力", "書式に記入", "この書式に入れて", "PDFからテンプレートに", "書類を作成して", "これも追加して", "このデータも入れて", or wants to auto-populate or incrementally add data to court documents.
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
日本語の概要は準備中です。原文の説明を表示しています。
Create agency proposal templates. TRIGGERS - Use when user needs help with agency-proposal-template related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Create strategic account planning templates. TRIGGERS - Use when user needs help with account-planning-template related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Estimate calcium-normalized Gapon selectivity coefficients from paired exchange and solution chemistry, or initialize depth-explicit EcoSIM Gapon inputs from the closest bundled ecosystem template when paired chemistry is unavailable. Use when deriving or checking EcoSIM GKC4, GKCH, GKCA, GKCM, GKCN, or GKCK values; matching a target ecosystem, climate, vegetation, and management regime to a starting profile; remapping template values to target soil layers; or documenting that template-based values require calibration or tuning.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
日本語の概要は準備中です。原文の説明を表示しています。