「pillars」の検索結果

Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance. Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building. USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design, UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI. DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic without UI, or non-frontend code.

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

Use when the user asks to "build a story bank", "collect our origin and customer stories", or "assemble reusable proof stories for the message"; assembles reusable narrative units — origin, founder, customer, transformation, and proof stories — each tagged to a claims-ledger ID and a message-house pillar, with every proof labeled Measured / User-provided / [needs source]. Not for authoring the message house or pillars — use message-system-architect; not for brand voice or naming rules — use brand-language-codifier; not for finished long-form prose — use content-writer; not for adjudicating whether a proof is true — use offer-claims-registry. 品牌故事库/起源客户转化/证据故事单元

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

Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for AI-citation SEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation".

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

Extract factual claims from PR copy, verify each claim independently, attach concrete citations, and warn when certainty is low. Runs each claim through proven newsroom verification methods (lateral reading, source-tier climbing, provenance pillars, triangulation, calibrated rating) and puts the burden of proof on the speaker. Use before a pitch, press release, reactive comment, DM, or other journalist-facing draft is trusted or sent.

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

Analyze a creator, influencer, founder, competitor, or brand social account to explain its positioning, content pillars, winning posts, hooks, formats, series, calls to action, and audience response. Use when the user wants to understand why an account works and what patterns to test without copying it.

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

Brand building and positioning on TikTok Shop. Brand identity development, content pillars, community engagement, brand storytelling, and authenticity strategies. Use when the user asks about TikTok branding, brand building, brand identity, or brand positioning on TikTok.

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

DORA (EU 2022/2554) digital operational resilience compliance for financial entities, covering all 5 pillars. Use for DORA readiness assessments, ICT risk management, incident classification, and third-party ICT oversight.

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

Create social media content across LinkedIn, Twitter/X, Instagram, TikTok, and Facebook with platform formats, hook formulas, and content pillars. Use when creating social posts, planning calendars, or writing LinkedIn posts and threads.

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

Plan content strategy: content pillars, audience research, topic clustering, funnel mapping, and content audits. Use when deciding what content to create, building a content calendar, planning topic clusters, or finding content gaps.

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

Strategic social media management for B2B SaaS: platform selection, content pillars, editorial calendars, community engagement, and crisis response. Use when building social strategy, planning content calendars, or conducting social audits.

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

Build a social media strategy per platform: pillars, cadence, KPIs. "build our social media strategy"

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

Build a 12-month SEO plan that scores four pillars and phases the roadmap. "build an SEO strategy"

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

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

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

Audits a legal document against legal design principles. Scores the document on six pillars: language patterns (bureaucratese, archaisms, passive voice, nominalization), readability (Flesch Reading Ease and language-specific equivalents), structure and navigation, hidden conditions (material obligations buried away from their headings), statutory duplication (restating the law instead of citing it), and visual hierarchy where layout is available. Assessment-only; does not rewrite the document. Works on English, French, and German documents, inferring the applicable jurisdiction from the document's language and textual signals: governing-law clause, statute citations, party addresses. Use when a user shares a legal document (contract, NDA, T&C, privacy policy, internal policy) asking how good the drafting is from a legal design perspective, whether it is readable, whether it contains buried clauses or restates the law, or how it scores on Flesch / LIX / Amstad / Kandel-Moles readability metrics.

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

Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier acceptance, example-based sad paths)

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

Use when a PERSONAL brand — founder, coach, or creator — needs a 12-month strategy: niche selection with Ikigai and a 3x3 matrix, positioning statement, a three-chapter story arc, four content pillars with 28 topics, a five-stage authority ladder, and a Q1 to Q4 growth plan. Trigger on 'personal brand strategy', 'founder brand plan', 'coach positioning', 'creator strategy', 'what niche should I own', 'I post constantly and nothing compounds'. Also use when the user has followers and no direction. Not for — a company brand, see `58-positioning-global` and `00-marketing-plan-global`; the context file this reads first, see `22-personal-brand-context-global`; turning it into revenue, see `27-personal-brand-monetize-global`.

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

Use when the user needs a monthly or weekly content calendar — posting schedule per channel, funnel ratio, content pillars, repurposing matrix, and an owner per slot. Trigger on 'content calendar', 'posting schedule', 'what should we post this month', 'editorial calendar', 'social media plan', 'we post randomly with no plan'. Also use when the user only says the team keeps running out of things to post. Not for — the brief for one specific post, see `36-content-brief-global`; the caption text itself, see `37-social-caption-global`; deciding next period content from last period data, see `40-next-content-plan-global`; a paid campaign timeline, see `02-campaign-brief-global`.

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

Use when the user asks for a visual or UI quality review of frontend code that already shipped, or passes a phase number. Produces {phase_num}-UI-REVIEW.md with a graded 1-4 assessment across six pillars.

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

Build a LinkedIn content system for thought leadership. Use when someone needs to establish authority, attract inbound leads, or build a consistent content presence. Covers positioning, content pillars, formats, and posting rhythm.

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

Generate a weekly Instagram content plan from a theme, audience, and content pillars. Produces a per-day mix of Reels, carousels, single images, and stories, each with a hook formula, angle, posting time, and primary goal, plus a weekly saves-and-shares goal (the 2026 lever), a story cadence, and a balance check across saves, shares, comments, and follows. Use to plan a week instead of ad-hoc posting. Not for drafting one caption (use ig-caption-writer) or one carousel (use ig-carousel-planner).

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

Provides structured AWS cost optimization guidance using five pillars (right-sizing, elasticity, pricing models, storage optimization, monitoring) and twelve actionable best practices with executable AWS CLI examples. Use when optimizing AWS costs, reviewing AWS spending, finding unused AWS resources, implementing FinOps practices, reducing EC2/EBS/S3 bills, configuring AWS Budgets, or performing AWS Well-Architected cost reviews.

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

When the user needs to plan, prioritize, or structure a content program -- including identifying content pillars, mapping content to the buyer journey, choosing content types, or building an editorial calendar.

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

Create, update, or validate a game's Game Design Document. Use when the user wants help producing, editing, or validating a GDD — the primary design artifact covering pillars, mechanics, progression, levels, art, audio, and development epics.

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

The research-domain clarification skill — find underspecified items in a thesis spec.md (prose wrong_if, universe rows without rationale, missing budget/expiry/pins, ambiguous pillars), ask the human structured questions WITH options (max 5 per round), encode the answers back into spec.md's Clarifications section, and re-evaluate checklists/thesis-quality.md after every write (Q32 bidirectional maintenance).

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