「authority」の検索結果

Build and maintain a provenance-clean proof library — inventory every real proof asset (analytics, reviews, permitted testimonials, case studies, press, certifications), categorize it, rewrite each cleared item in 3 lengths, fuse top assets with narrative, and gate everything through FTC testimonial rules before it can ship. Use when "proof library", "gather our proof", "authority builder", "collect testimonials", "social proof assets", "proof points for the sales page", "what results can we claim", or any request to assemble evidence for marketing claims. NEVER invents proof — missing proof is reported as a gap.

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

LLM brand manipulation — build a consensus web so ChatGPT, Claude, Perplexity, and Google AI Overviews mention your brand when people ask about your category. Uses surround sound methodology, entity SEO, and LLM citation science. Use when "get mentioned in AI", "LLM brand presence", "surround sound", "AI search visibility", "Perplexity ranking", "ChatGPT mentions", "AI Overview inclusion", "entity authority", "brand mentions in AI", or any request to influence how AI systems perceive and recommend your brand.

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

Turn a KOL roster + subreddit brand-fit analysis into a deployable creator network. Splits creators into KOL (authority) and KOC (grassroots) layers, matches each to a main + secondary subreddits by real gear/shooting-type ∩ community fit, and emits an account×subreddit deployment_matrix (with a ≤3-per-sub ceiling + no-cross-interaction rule) plus per-creator persona_cards. Route A disclosed-compliance baked into every card (FTC disclosure required on any material connection). Consumes reddit-kol-finder's kol_roster.json natively. READ-ONLY, deterministic, no LLM key needed.

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

Coordinate SEO, LLM-readable site architecture, UX, content, monitoring, security, and external authority work as a task-plan-driven sequence. Use this skill when the user asks to plan, execute, validate, or route multi-skill website growth work; asks what to do next across semantic core, URL structure, internal linking, schema, llms.txt, UX journeys, analytics, citation monitoring, or white-hat link placement; or wants a central architect that preserves evidence, alarms, handoffs, and tests.

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

Use when the user wants to get found in Google or AI engines (ChatGPT, Perplexity, AI Overviews) — keyword and content strategy, technical or content SEO audits, schema markup, link building, topical clustering, E-E-A-T, AI citation (AEO), or deciding whether SEO is even the right channel for their startup. Calibrated for early-stage, low-authority sites. Not for paid acquisition or channel-mix/CAC analysis (use channel-expert), or writing the page copy itself (use copywriter-skill).

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

Run the local pre-commit gate for the memex repo before staging a commit: format check, clippy with warnings denied, and the workspace unit-test suite, mirroring memex's own CI. Use right before `commit-changes` on a memex working tree, after editing any Rust crate under `crates/`, or when reproducing a red CI run locally. Optionally runs the Postgres-gated integration suite when the `memex-pg` container is up and `.env` is sourced. This is a verification gate, NOT a replacement for memex CI — CI remains the authority; this catches failures earlier.

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

Achieve distributed agreement without central authority using bee democracy, threshold voting, and quorum sensing. Covers proposal generation, advocacy dynamics, commitment thresholds, deadlock resolution, and consensus quality assessment. Use when a group must decide between options without a designated leader, when centralized decision-making is a bottleneck, when stakeholders have different perspectives to integrate, or when designing automated systems that must reach consensus such as distributed databases or multi-agent AI.

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

Establish Proto UI repository state, live contributor authority, Agent comprehension scope, task risk, and authorization before work begins. Use at the start of a development session, before autonomous task selection, after a material repository update, or when permission or assessment state may have changed.

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

Create or revise a governed Proto UI spec entity after identity, ownership, lifecycle intent, semantic scope, relations, and evidence plan are fixed by current authority. Use for Contract, Prototype, Module, Adapter profile, Decision, Host Capability, Test, Version, or Knowledge entity work. Do not use to decide an unresolved admission or lifecycle promotion.

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

Independently review a Proto UI change against current authority, bounded scope, executable evidence, projections, provenance, and integration conditions. Use for pull-request review, acceptance review, pre-merge audit, or fresh-context verification. Do not use to approve one's own work.

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

Implement or extend one governed Proto UI Module semantic slice. Use when Module ownership, facade and port boundary, dependencies, resource lifetime, Host Capability plan, Runtime registration, Adapter evidence, and validation scope are fixed by current authority. Do not use to admit a new Module or decide ownership.

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

Implement one governed Proto UI Adapter-profile realization slice. Use when target and runtime range, supported or omitted Module role, Host Capability fidelity, lifecycle translation, failure behavior, compatibility boundary, and evidence scope are fixed by current authority. Use pui-adapter-assess for research or readiness assessment and pui-regression first for a governed failing behavior.

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

Implement or revise one governed Proto UI Host Capability connecting a semantic Module to a bounded host responsibility. Use when capability identity, portable need, public shape, availability, failure, replacement, cleanup, fidelity, Adapter realization, and evidence are fixed by current authority.

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

Update Proto UI human documentation, localized pages, contributor guidance, demos, or package prose as a projection of governed repository facts. Use when the reader problem and source authority are known. Do not use documentation to invent semantics, hide drift, or widen a lifecycle guarantee.

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

Repair one independently verified Proto UI maintenance finding when governing authority or an explicit product decision fixes the expected result. Use for the bounded remediation and its evidence packet before independent review.

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

Prepare a reviewed Proto UI global release candidate as repository state after current project authority has chosen the exact version and stage. Use for draft Version identity, exact package metadata, notes, bill of materials, rehearsal, and publish dry-run. Publication remains a distinct privileged operation.

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

Independently attempt to falsify one Proto UI autonomous-maintenance finding in a fresh non-mutating context. Use after pui-observe produced a candidate finding and route the result directly to remediation or closure when authority is clear.

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

Map who is winning an SEO market with measured data — recurring SERP domains, organic footprints, winning content themes, backlink authority, and the gaps worth attacking. Use this skill for market-level questions ("who ranks for X", "how competitive is this space", "where are the SEO openings") before committing to keyword targets or content themes. For one named competitor, use openseo-competitor-analysis instead. Triggers: "competitive landscape seo", "who ranks for", "seo market map", "how competitive is", "serp competitors".

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

Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program.

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

"Apply Moore's business ecosystem framework to analyze how firms co-evolve through four stages (birth, expansion, authority, renewal) and occupy different ecosystem roles. Use this skill when the user needs to map ecosystem dynamics in a platform or industry, evaluate keystone vs dominator strategies, assess ecosystem health, or when they ask 'what stage is this ecosystem in', 'how should we position in this ecosystem', or 'why is this ecosystem declining despite having a dominant player'.".

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

Class Variance Authority - type-safe component variant styling with cva(), compound variants, and VariantProps

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

Generates networking boilerplate adapted to the project's chosen networking package (NGO, Mirror, Photon). Use when setting up multiplayer systems, syncing state, writing RPCs, building lobbies, or designing an authority matrix. Triggers on requests like "add multiplayer", "sync player health", "create an RPC", "set up lobbies", "make this networked", "add co-op", "replicate this across clients", "spawn networked objects", "handle player disconnect", "create a matchmaking system", or any task involving network state synchronization, remote procedure calls, or client-server architecture. Always reads ProjectConfig.yaml -> networking before generating code. If networking is "none", do NOT generate networking code.

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

Use when a task needs the judgment of an executive administrative assistant — triaging a stacked calendar against competing priorities, deciding what reaches an executive versus what gets redirected, reconciling a multi-city travel itinerary or expense report, drafting on an executive's behalf within a delegated-authority boundary, or handling a scheduling conflict across time zones.

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

Use when a task needs the judgment of a Clinical Nurse Specialist — diagnosing why a unit-level outcome metric (CLABSI, falls, pressure injury) is off benchmark, designing and scaling a practice-change pilot, appraising whether a new clinical guideline actually fits the local population, writing a quarterly outcomes report to nursing leadership, or coaching staff nurses through a new protocol without formal authority over them. US hospital/health-system default; state nurse practice acts vary. A reasoning aid, not clinical or legal advice.

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