「section」の検索結果

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing.

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

Retrieves patent claims data from Nexscope (Nexscope). Trigger when the user mentions patent claims, claim text, independent claims, dependent claims, claim count, claims tree, claims analysis, claim scope, claim language, viewing the claims section of a specific patent, patent claims, independent claims, dependent claims, claims text, Nexscope. Also trigger when the user requests patent claims information by patent ID or publication number, even without explicitly mentioning Nexscope or Nexscope.

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

SEO-friendly article writing, audit, and humanization workflow for Markdown content. Use when creating, outlining, editing, auditing, rewriting, or quality-checking blog posts, tutorials, comparisons, listicles, explainers, FAQ sections, excerpts, SEO titles, meta descriptions, tags, or Google-friendly content briefs that need clear topics, natural keyword use, on-page SEO review, reader-friendly prose, and iterative optimization.

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

Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document

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

Build, revise, audit, or rebut a research manuscript from Harness Research evidence. Use for paper intake, related-work research, claim and citation control, section architecture, LaTeX patching, figure planning, reviewer response, or final manuscript hardening when the workspace contains Harness research artifacts.

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

Use when evaluating grant ideas, diagnosing proposal logic, framing fundable projects, strengthening reviewer-aware arguments, or preparing to write any section of a research proposal.

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

Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers (=========), class organization, naming conventions (services, queue jobs, records, events, enums), defineRules() and validation, beforePrepare() and addSelect(), MemoizableArray, DateTimeHelper vs Carbon, strict_types/declare(strict_types=1), short nullable notation (?string), typed properties, void returns, control flow (early returns, match over switch), CP Twig template conventions, form macros, translations (Craft::t), ECS/PHPStan config, scaffolding commands, and the verification checklist.

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

Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: "resolve the open questions", "close the gaps in this spec", "research the open items", "finalize my spec", "make this spec implementation-ready", "answer the TBDs". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec.

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

Health insurance planning for Indian families — Section 80D optimization, family floater vs individual, super top-up strategy, parents' coverage, critical illness, corporate cover limitations, and IRDAI portability. Triggers on 'health insurance', '80D', 'mediclaim', 'family floater', 'super top-up', 'health cover', 'parents health insurance', 'medical insurance', or 'health insurance for family'.

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

Analyzes insurance scenarios by referencing specific sections of the Life Insurance Act, Insurance Contracts Act, and Corporations Act, providing direct quotes and explanations.

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

Produce board financial package — monthly or quarterly financial update with P&L, cash position, key metrics, and variance vs plan. Use when asked to "prepare board materials", "write the financial section of the board deck", or "what metrics does the board care about".

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

Show where the user is and what their actions affect — breadcrumbs, regions, scope labels. Use when designing deep navigation or multi-section layouts.

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

Product visuals must show the real product with real data. Use when building landing pages, hero sections, screenshots or demo panels.

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

Creates, supersedes and validates decision records (ADRs) against the convention a collection already follows, instead of imposing a published one. Use when the user wants to record a decision, write an ADR, supersede an existing decision, audit or lint a decisions folder, check that an ADR index is in sync, or asks "why did we decide X". Deduces the filename scheme, section set and status vocabulary from the records already there; ships a validator with an exit code, so the audit is a check and not an opinion.

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

Spatial reasoning, coordinate geometry, transformations, and trigonometry for geometric problem solving. Covers Euclidean geometry (points, lines, angles, congruence, similarity), triangle geometry (Pythagorean theorem, laws of sines and cosines), circle geometry (tangent lines, inscribed angles, power of a point), coordinate geometry (distance, midpoint, slope, conic sections), transformations as functions (rotation, reflection, translation, dilation), trigonometry (unit circle, identities, inverse functions), and geometric proof techniques. Use when reasoning about shapes, angles, spatial relationships, coordinate problems, or trigonometric computations.

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

Musical form and structural analysis covering binary, ternary, rondo, sonata, theme-and-variations, and popular song forms. Covers formal archetypes (AB, ABA, ABACA, sonata-allegro), 12-bar blues, arch form, minimalist process forms, strophic and through-composed designs, and formal analysis methodology for both score study and listening. Use when determining the structural plan of a piece, analyzing sectional relationships, or understanding how form shapes musical narrative.

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

Generate intelligence briefings for the planning dashboard. Use this skill whenever a request file appears in `.planning/console/inbox/pending/` whose `type` field starts with `intelligence.` (refresh_briefing, triage_finding, snapshot_diff, investigate_section, dismiss_finding). The skill reads the per-project KB at `.gsd/intelligence/intelligence.db`, synthesizes a briefing with a causal hypothesis + acknowledged uncertainty + confidence label and ranked moves, then writes the result back to the KB. Always trigger this skill for these request types — do not generate briefings manually.

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

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

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

Configures pyproject.toml and Python packaging using PEP 517/518/621/660/723 standards. Use when creating or updating pyproject.toml, selecting a build backend (hatchling/setuptools/flit), configuring ruff, ty, mypy, pytest, or coverage tool sections, setting up dependency constraints or optional extras, defining CLI entry points, configuring pre-commit hooks, establishing src-layout directory structure, or preparing a package for PyPI publishing.

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

Synthesis step in the multi-angle technical research pipeline. Receives structured outputs from all four research angles (api-state, ecosystem-research, impact-measurement, codebase-auditor), applies cross-angle signal weighting and conflict resolution, and produces a single synthesized Research section. Invoked by the technical-researcher orchestrator after all angle skills complete. Returns content to the orchestrator — does not write to the backlog.

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

Use when executing a task the orchestrator dispatched — reads the task and its orchestrator response from the work ledger, loads task-level skills, implements against acceptance criteria, records divergences and the completion report as task sections, and closes the attempt. Triggers on task execution within the implement-feature loop or when an agent picks up a specific task from a plan.

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

Use when the PLAN artifact from SAM Stage 2 needs contextualization against actual codebase state — grounds the design plan in reality by performing scope analysis (NEW/MODIFY/COMPLETE classification), conflict detection between plan assumptions and codebase patterns, and resource mapping to concrete file paths and integration points. Produces an updated ARTIFACT:PLAN registered via MCP with a Contextualization section appended.

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

Transforms validated /linear-walkthrough artifacts into one presentation-ready deck outline per major codebase component. Use when the user asks to create a presentation, prepare a walkthrough deck, build an onboarding deck, produce an architecture review deck, or summarize a codebase for a technical audience. Requires walkthrough directory output -- reads unified walkthrough, per-section files, validation reports, coverage maps, entry points, and open questions -- then orchestrates four parallel agent phases to produce slide outlines with speaker notes, evidence references, and suggested visuals.

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

Enforce anti-AI UI design rules based on the Uncodixfy methodology. Use when generating HTML, CSS, React, Vue, Svelte, or any frontend UI code. Prevents generic AI aesthetic — soft gradients, glassmorphism, hero sections in dashboards, oversized rounded corners, and decorative copy. Applies constraints from Linear/Raycast/Stripe/GitHub design philosophy for functional, honest, human-designed interfaces. Triggers on UI generation, dashboard building, component creation, CSS styling, landing page design, or any task producing visual interface code.

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