「rules」の検索結果

Roadmap concision rules, step decomposition efficiency, AC abstraction guidelines, and step-to-scenario mapping. Load when creating implementation roadmaps.

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

Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.

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

Definition of Ready checklist criteria, antipattern detection patterns, UAT quality rules, and domain language enforcement for product owner review

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

Strategic and tactical DDD patterns, bounded context discovery, context mapping, aggregate design rules, and decision frameworks for when to apply DDD

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

Tactical DDD — aggregate design rules, entities, value objects, domain events, repositories, domain services, and anti-pattern detection

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

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

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

BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation

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

Documentation collapse anti-patterns - detection rules, bad examples, and remediation strategies for type-mixing violations

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

Domain-specific authoritative source databases, search strategies by topic category, and source freshness rules

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

Use when briefing or managing an EXTERNAL agency, freelancer, or production vendor — scope of work, deliverable specs, revision rounds, approval process, USD payment milestones, IP assignment and confidentiality terms, communication rules, and a post-project vendor scorecard. Trigger on 'brief an agency', 'hire a freelancer', 'scope of work', 'the agency is not delivering', 'onboard a new vendor', 'we keep paying for work we have to redo'. Also use when the user is about to sign a supplier with nothing written down. Not for — briefing an internal team member, see `64-team-brief-global`; the campaign brief itself, see `02-campaign-brief-global`; the asset list the vendor produces, see `41-campaign-asset-list-global`.

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

Use when a NEW landing page, sales page, or single-product page has to be built — seven-section structure, one page one goal one CTA, copy per block, mobile-first rules, technical and speed requirements, tracking plan, A/B test plan, and a dropshipping single-product mode. Trigger on 'landing page brief', 'build a sales page', 'I need a landing page', 'brief for the dev', 'Shopify product page', 'what should go on the page'. Also use when ad traffic is ready and there is nowhere to send it. Not for — the ad copy pointing at the page, see `05-ad-copy-global`; the offer and its value stack, see `31-offer-design-global`; scoring a finished design, see `47-design-review-global`; coded email, see `49-html-email-template-global`.

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

Use when the user wants a marketing image GENERATED or an image prompt written — personal brand portraits, logos and monograms, campaign key visuals, day-to-day social graphics, editorial art, infographics, web hero mockups, and quote graphics. Reads brand identity from project context, composes an on-brand prompt, generates via gpt-image-2 when an API key exists, otherwise outputs paste-ready prompts for DALL-E 3, MidJourney, Leonardo, or Ideogram. Trigger on 'design an image', 'make me a logo', 'MidJourney prompt', 'key visual for the campaign', 'generate a graphic for this post', 'I need a visual and have no designer'. Not for — briefing a human designer on a static, see `42-image-brief-global`; a slide sequence, see `43-carousel-brief-global`; the brand rules themselves, see `46-brand-guideline-global`; scoring a finished design, see `47-design-review-global`.

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

Use when the user needs to define, document, or enforce how the brand SOUNDS in writing — three personality traits, a five-dimension tone table, vocabulary to use, avoid, and ban, sentence rules, before and after rewrites, platform adaptation, and a copy approval checklist. Every content skill reads it before writing. Trigger on 'brand voice', 'tone of voice', 'voice guidelines', 'banned words list', 'this copy does not sound like us', 'every writer sounds different'. Also use when the user cannot say why a draft feels wrong. Not for — the visual side of brand, see `46-brand-guideline-global`; positioning and the message, see `58-positioning-global`; approving one specific piece, see `62-marketing-review-global`.

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

Use when a designer needs hands-on production direction inside a tool — Canva, Figma, or Adobe Express: which template to start from, the operating order, element-by-element mapping, grid and spacing, brand kit colors and fonts, export checklist, and the dos and do-nots. Trigger on 'Canva brief', 'Figma brief', 'production direction', 'how do I build this in Canva', 'layout direction for the designer', 'the junior designer needs step by step'. Not for — the creative concept for a static, see `42-image-brief-global`; the concept for a slide sequence, see `43-carousel-brief-global`; the brand rules being applied, see `46-brand-guideline-global`; adapting one master into every size, see `50-asset-resize-global`.

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

Use when one master design has to become every size a campaign needs — feed, story, reel, cover, and ad placements: the standard size matrix, three strategies of scale-and-crop, re-compose, or rebuild, safe-zone rules, platform crop behavior, and file naming. Trigger on 'resize this design', 'all the sizes', 'adapt to other placements', 'safe zone', 'standard size chart', 'the text gets cut off in stories'. Also use when one visual exists and six placements are waiting on it. Not for — the original concept brief, see `42-image-brief-global`; production steps in Canva or Figma, see `45-design-tool-brief-global`; the full campaign asset list, see `41-campaign-asset-list-global`; an urgent new creative, see `48-quick-visual-brief-global`.

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

Use when warm audiences need a plan — retargeting tiers by intent and recency, a different message per tier, frequency caps, attribution windows, lookalike seeds, exclusion rules, and a first-party data base that survives iOS ATT and cookie deprecation. Trigger on 'retargeting', 'remarketing', 'warm audience', 'custom audience setup', 'retarget cart abandoners', 'my retargeting pool is too small'. Also use when the user says people visit once and never come back. Not for — cold prospecting audiences, see `51-audience-research-global`; the pixel and events that feed these audiences, see `53-tracking-setup-global`; email win-back flows, see `14-email-marketing-global`; raising budgets, see `55-scaling-ads-global`.

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

Use when a team wants to design, audit, or operate an AI Marketing OS — a Brand Hub source of truth, role-based AI projects for leader, content, design, performance, and knowledge, skill chains, ChatGPT plus Claude plus NotebookLM workflows, MCP connectors, a Notion or Drive second brain, ads data loops, SOPs, weekly reviews, and handoffs. Trigger on 'AI marketing OS', 'set up our marketing AI system', 'Brand Hub', 'AI workflow for the team', 'MCP for ads data', 'how do I make AI actually useful for marketing'. Not for — one campaign brief, see `02-campaign-brief-global`; the weekly report, see `07-marketing-report-global`; the brand visual rules, see `46-brand-guideline-global`; the product context file, see `product-marketing-context-global`.

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

Use when a finished DESIGN needs scoring and feedback — brand consistency, hierarchy plus readability plus accessibility, conversion elements, and platform fit, 10 points each, with per-issue feedback in issue, why, and how-to-fix form and a verdict of approve, minor fix, or redo. Trigger on 'design review', 'review this design', 'score this creative', 'is this design good', 'brand check on this banner', 'can we ship this or not'. Also use when the user just sends an image and asks for thoughts. Not for — reviewing copy and briefs, see `62-marketing-review-global`; writing the brief before production, see `42-image-brief-global`; the brand rules being checked against, see `46-brand-guideline-global`.

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

Use when the user wants to show up in OTHER communities without astroturfing — Reddit, Facebook Groups, Discord, Slack, LinkedIn groups, Quora, and niche forums: a prioritized community list with the rules of each space, a named participant roster, post types written in full, reply scripts, a participation calendar, and red lines. Trigger on 'community marketing', 'Reddit marketing', 'seeding plan', 'post in Facebook groups', 'answer questions on Quora', 'we got banned from a group'. Not for — building your OWN paid or private community, see `28-community-building-global`; monitoring mentions across the web, see `15-social-listening-global`; briefing paid creators, see `06-ugc-egc-brief-global`.

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

Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.

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

Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.

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

Run bounded tabletop scenes with explicit rules assumptions, character state and player choices. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.

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

Rules for Operately schema migrations (app/priv/repo/migrations/) and data migrations (app/lib/operately/data/change_*.ex). Use when adding, renaming, reviewing, or generating database migrations, ecto.gen.migration, Operately.Data.Change* modules, backfills, schema_migrations version collisions, mix ecto.migrate, or make gen.migration.

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

Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language. Use this whenever the user asks to write clean code, follow clean-code principles, refactor for clarity, improve naming, reduce complexity or duplication, separate concerns, tighten error handling, work test-first or do TDD, or otherwise raise code quality, readability, and maintainability. Also use when writing or reviewing Operately APIs or Ecto queries. Apply these rules by default when producing or changing code for a quality-conscious user.

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